DaVinci Junior cartridge reset (Page 15 of 58)

Well seeing how I am an incredibly lazy hack, My first intention was to default all commands to the bit bucket and then add in ones to respond to as needed. I suppose I am using the term Emulator rather loosely. I think as I get a better look at the data stream that may help form how much I want to do this. I am presuming that a large portion of the communication is static and repeatable and can be handled as "if you see this, respond with this", with little to no logic control.  I just have to figure out where my arduinos and raspberry pie have gone to set up a bit of Man in the middle hacking.

If there is FL+ABS or something marked on the filament there is an indicator on the spool that indicates that is PLA. I am going off of memory because I am not home so the letters might be different. You can try raising the temperature by using cura or slic3r to slice the model and setting the temp in those programs then using the program ThreeDubber posted earlier in this forum to convert the gcode to 3w then either sending it to the printer through XYZWare or loading it onto an sd card and printing it off there.

I finally got my Arduino shield!  Managed to reset the spool length in the chip that came with the spool/printer I previously ran to 0m. 

Now, I'm seeing something interesting....  I rewrote the chip using the password I'd grabbed earlier and crcasey's scripts.  This set Page 10/11 to 200m length.  Since then, I've been dumping the NFC chip after each (well, almost each, I get excited to start the next print sometimes!) print.  For each dump since the first reset, only pages 20->23 are updated.  Pages 10 and 11 (where the original length information was found) stay exactly the same.

When I check the spool stats on the LCD, it shows the value decrementing as expected.  After looking at the dumps, it appears Page 20 is formatted like Page 10/11.  But, it contains the remaining length.  Here are my values :

192m remaining : Page 20 = E4 F0 02 => 2F0E4 = 192740
175m remaining : Page 20 = 1E AF 02 => 2AF1E = 175902
168m remaining : Page 20 = C2 92 02 => 292C2 = 168642
0m remaining : Page 20 = 00 00 00 => 000000 = 0 

The 0m dump I did before the length reset.  Page 10/11 indicated 100m rather than 200m.  I'm thinking Page 10/11 might not be so important?

EDIT : Just went back and re-read the previous posts.  The Page 20 stuff was already figured out.  On to deciphering 21-23...

While working through the rest of the information on the NFC card might be interesting, I'm guessing what most people would like is a single system (i.e. don't need logic analyzers *and* arduinos *and* special shields) that can reset the length parameters.  We have most of the pieces of the puzzle already.  Just the specifics of the implementation are left to work through.

As I mentioned in an earlier post, I'm a fan of having a separate microcontroller sitting on the I2C bus that can both grab the password information *and* communicate with the PN512 to reset the chip.  This would eliminate the need for logic analyzers and NFC card readers.  Just "push a button" on the microcontroller to reset the length.

One additional part of the NFC decode that might be interesting is figuring out where it stores extruder temperature information.  I've had good luck using 3rd party PLA filament with a lower temperature range spec.  I'm very new to this so I'm not sure if the success is from the temperature range or from just having a better PLA material to work with.  It might be nice to be able to change the temperatures in the card rather than having to use the Advanced mode/G-code editor.

I'm using it perfectly fine with Cura. All I do is export the GCode, run it through ThreeDubber, load it up on an SD Card and pop it into my printer, then start the print. This is very useful because I don't have to have my printer plugged into my computer to slice a model, I don't understand why XYZWare does that. Anyway it works perfectly fine for me! What slicer are you using? It could be the settings of your slicer. Try adjusting the Z offset or the calibration screws.

I am using Cura version 15.04.4 (the latest version). I actually have changed the default Start/End code because I was originally using a script called convert2DaVinci before ThreeDubber came out, and I forgot about it. Anyway here it is if you want to try it out.

start.gcode:

; --- MOVE THIS SECTION TO THE TOP AND DELETE THIS LINE ---
; filename = composition.3w
; machine = daVinciJR10
; material = pla
; layer_height = {layer_height}
; total_layers = 173
; total_filament = 0.00
; extruder = 1
; --- END SECTION ---
;Sliced at: {day} {date} {time}
;Basic settings: Layer height: {layer_height} Walls: {wall_thickness} Fill: {fill_density}
;Print time: {print_time}
;Filament used: {filament_amount}m {filament_weight}g
;Filament cost: {filament_cost}
;TEMPERATURES
G21        ;metric values
M107       ;start with the fan off
G90        ;absolute positioning
G92 E0     ;zero the extruded length
M82        ;set extruder to absolute mode
G1 Z0.00000 ;offset Z by 8? mm to bring bed up to nozzle
G92 Z0     ;zero Z axis
G1 F{travel_speed} E-1.00000
G92 E0     ;zero the extruded length again

end.gcode:

;End GCode
;M104 S0                     ;extruder heater off
;M140 S0                     ;heated bed heater off (if you have it)
;G1 E-1 F300                 ;retract the filament a bit before lifting the nozzle, to release some of the pressure
;G1 Z+0.5 E-5 X-20 Y-20 F{travel_speed} ;move Z up a bit and retract filament even more
G92 E0
M107                        ;fan off
M84                         ;steppers off

I had the same problem with cura gcode, you have to convert the G0 commands to G1 as XYZ firmware doesn't handle them (according to another post on soliforum) doing this fixes the problem, but you have to make sure you don't kill the power during a print. Instead you should cancel the job via the menu. I made this mistake on a failed print and messed up one of my NFC cards. It now reads unidentified spool as I'm sure theres some mismatch on the card. It was already low anyway but I wish I had the NFC tools so I wouldn't have to deal with it. Are we documenting card passwords anywhere? I'd like to see if we can get the passwords without sniffing I2C traffic.

Right, pardon me for being unclear. I meant to say that maybe we can determine the relationship between the password and the information on the card and I was wondering if this was being documented anywhere.

Yes its possible, first need get password, after that you can turn off password protection

Not sure if it has been said before or looked into.  I had let the card get down to around 80m then went to rewrite and found that it would read unrecognized using the exact code and byte values I had used before. After some head scratching, comparing values and testing for about an hour I decided to copy all my original 200 or 200m pages back to the card but decremented the last byte on page 14 by 1 (was 38 and is now 37). Some reason it worked and I have a full card.

Hi! I am new to this topic. I just signed up here to ask a few questions about this. I have a Da Vinci Jr and would like to print with filaments such as wood that aren't given as an option from XYZ. From my understanding, you have to purchase a logic analyzer to capture the password coming from the I2C bus. I've looked into that and the cost of these analyzers such as the Salae Logic 4 is just way too high for my budget. Could you use an Arduino or Raspberry Pi as a logic analyzer? I've looked into them and there are some programs written to transform the raspberry pi/arduino into a logic analyzer but I don't know if any of them have to capabilities to read I2C and other important features as well as be fast enough to capture the password (I saw that you couldn't get the bus pirate to capture the password successfully). If there is no possible way to use an arduino or raspberry pi then are there any cheap analyzers that would be practical for this? ~$25

Edit: Was just looking around and found this. Would this be good? http://www.seeedstudio.com/depot/Logic- … -1750.html