Dimension elite support

[morriswinkler]

does one of the machine_number provide support for a elite, if not how can i help to get the

hex string ? i got one, also have some dumps of the software ( diskimage )

Cheers

[bvanheu]

Did you try with the "prodigy" machine number?

[morriswinkler]

I tried, it says MATERIAL ERROR INVALID SPOOL

could it be something with the Material i uses 0x00 ABS,

i have no original dimension elite spool to test with, the ones i use are from an other dimension ( don't remember the name right now)

[morriswinkler]

i also pulled the last commits from the repro and when i do

# python stratasys-cli.py eeprom -r -t prodigy -e d600000061424123  -i 1415101185.99.bin_prodigy

i get

Cartridge - '1415101185.99.bin_prodigy'
-------------------------------------------------------------------------------
Serial number       73.0
Material        ABS_S (15 - 0xf)
Manufacturing lot   EMPTY
Manufacturing date  2007-10-03 16:44:09
Last use date       2007-10-03 16:44:09
Initial quantity    56.3
Current quantity    56.3
Key fragment        55aa55df313978be
Version         1
Signature       STRATASYS

Machine type:       prodigy 5394D7657CED641D
EEPROM uid:     d600000061424123

To recreate this cartridge:
Traceback (most recent call last):
  File "stratasys-cli.py", line 228, in <module>
    app.run()
  File "stratasys-cli.py", line 47, in run
    args.func(args)
  File "stratasys-cli.py", line 125, in command_eeprom
    self._eeprom_info(args)
  File "stratasys-cli.py", line 200, in _eeprom_info
    + " --signature " + str(cartridge.signature))
AttributeError: Cartridge instance has no attribute 'material'

[bvanheu]

I tried, it says MATERIAL ERROR INVALID SPOOL could it be something with the Material i uses 0x00 ABS,

hmm i don't own a stratasys printer, but i think that they are validating the material on the cartridge.

Could you try with other material to see if the printer accept them?

Regarding the AttributeError (AttributeError: Cartridge instance has no attribute 'material') this is indeed a bug ;) i'll fix it soon.

Thanks.

[morriswinkler]

So ok i hooled up a Terminal to my Stratasy, added sshd and watched the log messages, than i saw that the validation failed at the material, thanks to the stratasys programmers the debug output is really great,

than i checked the log file for all cartdridges that where ever loaded successfull, turns out it is 63 0x3f and 40 0x28, really interesting , i let you know if i figure that whole material thing

cheers,

[dschiedsch]

Hi I got a new cartridge working on a dimension Elite machine with --material-name P430_BLK Full command was: ./stratasys-cli.py eeprom --machine-type prodigy --eeprom-uid "your-uid" --serial-number 127452107.0 --material-name P430_BLK --manufacturing-lot 6112 --manufacturing-date "2013-10-11 03:27:23" --use-date "2013-10-11 03:27:23" --initial-material 56.3 --current-material 56.2 --key-fragment 55aa55d7f09c62be --version 1 --signature STRATASYS -o new_abs3.bin

Seems 40 (0x28) ABS_SS is the code for the support material. So this will only work in the slot for support material

[milesguidon]

Hi dschiedsch,

I am working with an elite as well, and here is what I am trying to do, with an eeprom uid of 300000017BC4A223. Using your command as guidance I run this (I just changed the UID, andkey-fragment):

./stratasys-cli.py eeprom --machine-type prodigy --eeprom-uid "300000017BC4A223" --serial-number 127452107.0 --material-name P430_BLK --manufacturing-lot 6112 --manufacturing-date "2013-10-11 03:27:23" --use-date "2013-10-11 03:27:23" --initial-material 56.3 --current-material 56.2 --key-fragment 55aa557b78d255be --version 1 --signature STRATASYS -o new_abs3.bin

This resulting bin doesn't seem to work when converted to HEX and then written back to the chip. Your fragment "55aa55..." does that come from the chip when it is depleted, or did you grab that when it was full? Any ideas? thank you!

[dschiedsch]

Hi i used the UID without quotes (") maybe that makes a difference did you use a new eeprom chip. Becuase the machine remembers old EEPROM UIDs and gives an error if the material amount increases from the last known state (stored on the internal hard drive)

My key fragment comes from an old cartridge with two digits changed. I think the fragments are random at least from my experience with the machine.

Also I'm using a bus pirate to read and write the EEPROMs so I don't know if your conversion to hex has anything to do with that I just use the bp_write.py in the software package

If you pm me I can send you the cartridge data sets that I've read from a few original cartridges

[milesguidon]

Thanks dschiedsch! Turns out I just needed to run my resulting binaries through a bin2hex program that converts the binaries to Intel HEX format. Then, I manually deleted some info native to the Intel HEX format, leaving just the raw data to go on to the EEPROM. I'm using a 1-Wire to USB converter, where I can read and manually write data to a cartridge PCB -- this data is in Hex format so that's why I need to do the conversion.

The P430_BLK (model material) and ABS_SS (support material) codes are working well in my Elite, 1200ES SST, and Fortus 200MC. Success, for now! Thanks for your posting your results.

[B4bazil]

We have a uprint plus. Does anyone know the machine number or how to find it? is it stored on the hard drive somewhere? We have new EEPROM's and can read them.

[dschiedsch]

Hi same for me I just read the eeprom succesfully and also heed the correct machine number I would guess that it is somewhere on the machine but haven't tried taking the machine apart yet It would be very nice to know how the other numbers got acquired

On Tue, Apr 14, 2015 at 10:23 AM, B4bazil notifications@github.com wrote:

We have a uprint plus. Does anyone know the machine number or how to find it? is it stored on the hard drive somewhere? We have new EEPROM's and can read them.

— Reply to this email directly or view it on GitHub https://github.com/bvanheu/stratasys/issues/7#issuecomment-92691610.

[milesguidon]

It looks like there is added support for the uprint and uprintse, but not uprintse PLUS. I have tried to do the chips in my uprintse PLUS using the uprintse machine code, but it's not working. Where are the machine codes coming from?

[bvanheu]

Hi guys,

The machine codes are in a binary somewhere in the printer firmware. You have to reverse engineer the binary to see what code the firmware is using.

[milesguidon]

I wonder if the machine codes are located in the *.upg firmware upgrade files. I have these files for all of my machines...I have been looking but cannot find.

[krrk]

I am also looking for the machine id of the uprint SE Plus. I have an image of the hard drive and have been looking around, but I don't have any idea where to look. How were the existing machine id's obtained?

[milesguidon]

I've come to the conclusion that uPrint SE and uPrint SE Plus have the same machine ID, because on Stratasys' website shop, the spools of material you buy work on both machines. I still haven't gotten it to work. I have to take one of my EEPROMs and dump its data and backtrack to see what all of the original parameters are

On 6/2/2015 3:55 PM, Kieran Ramos wrote:

I am also looking for the machine id of the uprint SE Plus. I have an image of the hard drive and have been looking around, but I don't have any idea where to look. How were the existing machine id's obtained?

— Reply to this email directly or view it on GitHub https://github.com/bvanheu/stratasys/issues/7#issuecomment-108122763.

Best,

Miles Guidon

Hardware Design Engineer MOCAP Design, LLC www.MOCAPdesign.com http://www.mocapdesign.com (818) 730-4212