Closed bmalcheski closed 10 years ago
Hey!
Yes "stratasys-cli.py" expect a binary file as input. I just fixed a typo in a serial number when using the "fox" machine type, maybe it was the issue?
I've also merged stratasys-ng into master, so you may want to pull the repository and delete the "stratasys-ng" branch.
Thanks for the info. My machine is a prodigy.
I've added two scripts to read/write to an cartridge using a buspirate, you might want to try them.
Those scripts are awesome. Thank you so much! I'm having a problem with printing the eeprom data though. I enter this into the command line: python stratasys-cli.py eeprom -t prodigy -e 0e00000160aa0e23 -i ETeeprom.bin
and I get "TypeError: unpack-from() argument 1 must be string or read-only buffer, not byte array."
I assume I am doing something wrong but can't figure out what.
Thanks for the help.
Ben
On Fri, May 16, 2014 at 10:55 PM, Benjamin Vanheuverzwijn < notifications@github.com> wrote:
I've added two scripts to read/write to an cartridge using a buspirate, you might want to try them.
— Reply to this email directly or view it on GitHubhttps://github.com/bvanheu/stratasys/issues/4#issuecomment-43396836 .
I tried another eeprom and although I got a current quantity checksum error it seems to be working for that eeprom. I had been experimenting with the old refill method on some of these eeproms and likely messed the data up while doing so.
However, when trying a brand new support material eeprom (from a 3rd party material supplier) I still get the TypeError.
On Sun, May 18, 2014 at 11:14 PM, Ben Malcheski bmalcheski08@gmail.comwrote:
Those scripts are awesome. Thank you so much! I'm having a problem with printing the eeprom data though. I enter this into the command line: python stratasys-cli.py eeprom -t prodigy -e 0e00000160aa0e23 -i ETeeprom.bin
and I get "TypeError: unpack-from() argument 1 must be string or read-only buffer, not byte array."
I assume I am doing something wrong but can't figure out what.
Thanks for the help.
Ben
On Fri, May 16, 2014 at 10:55 PM, Benjamin Vanheuverzwijn < notifications@github.com> wrote:
I've added two scripts to read/write to an cartridge using a buspirate, you might want to try them.
— Reply to this email directly or view it on GitHubhttps://github.com/bvanheu/stratasys/issues/4#issuecomment-43396836 .
Ok, I just remembered the issues with Python 2.7.3. I just have to get my Ubuntu to install a newer Python. I tried 2.7.6 but I ended up getting a unicode mismatch between python and pycrypto...
On Sun, May 18, 2014 at 11:31 PM, Ben Malcheski bmalcheski08@gmail.comwrote:
I tried another eeprom and although I got a current quantity checksum error it seems to be working for that eeprom. I had been experimenting with the old refill method on some of these eeproms and likely messed the data up while doing so.
However, when trying a brand new support material eeprom (from a 3rd party material supplier) I still get the TypeError.
On Sun, May 18, 2014 at 11:14 PM, Ben Malcheski bmalcheski08@gmail.comwrote:
Those scripts are awesome. Thank you so much! I'm having a problem with printing the eeprom data though. I enter this into the command line: python stratasys-cli.py eeprom -t prodigy -e 0e00000160aa0e23 -i ETeeprom.bin
and I get "TypeError: unpack-from() argument 1 must be string or read-only buffer, not byte array."
I assume I am doing something wrong but can't figure out what.
Thanks for the help.
Ben
On Fri, May 16, 2014 at 10:55 PM, Benjamin Vanheuverzwijn < notifications@github.com> wrote:
I've added two scripts to read/write to an cartridge using a buspirate, you might want to try them.
— Reply to this email directly or view it on GitHubhttps://github.com/bvanheu/stratasys/issues/4#issuecomment-43396836 .
I can FINALLY read the data on an eeprom. I've been trying to get cartridge refills working for longer than I care to admit. Thank you so much for these awesome tools!
The Bus Pirate read script works like a charm!
On Mon, May 19, 2014 at 10:06 AM, Ben Malcheski bmalcheski08@gmail.comwrote:
Ok, I just remembered the issues with Python 2.7.3. I just have to get my Ubuntu to install a newer Python. I tried 2.7.6 but I ended up getting a unicode mismatch between python and pycrypto...
On Sun, May 18, 2014 at 11:31 PM, Ben Malcheski bmalcheski08@gmail.comwrote:
I tried another eeprom and although I got a current quantity checksum error it seems to be working for that eeprom. I had been experimenting with the old refill method on some of these eeproms and likely messed the data up while doing so.
However, when trying a brand new support material eeprom (from a 3rd party material supplier) I still get the TypeError.
On Sun, May 18, 2014 at 11:14 PM, Ben Malcheski bmalcheski08@gmail.comwrote:
Those scripts are awesome. Thank you so much! I'm having a problem with printing the eeprom data though. I enter this into the command line: python stratasys-cli.py eeprom -t prodigy -e 0e00000160aa0e23 -i ETeeprom.bin
and I get "TypeError: unpack-from() argument 1 must be string or read-only buffer, not byte array."
I assume I am doing something wrong but can't figure out what.
Thanks for the help.
Ben
On Fri, May 16, 2014 at 10:55 PM, Benjamin Vanheuverzwijn < notifications@github.com> wrote:
I've added two scripts to read/write to an cartridge using a buspirate, you might want to try them.
— Reply to this email directly or view it on GitHubhttps://github.com/bvanheu/stratasys/issues/4#issuecomment-43396836 .
Got the machine to read my eeprom! Thanks again!
Hi Ben, I've been working hard on this as well. Could you drop me a line to chat about this? creativechemist at netscape dot net
I am trying to refill cartridges using the GPIO pins on a Raspberry Pi to read/write the eeprom. Does Stratasys-ng expect the data file to be in binary?
What I am doing is taking the dump from the GPIO directory, opening it using Vi in hex mode, copy the data to another text editor, remove all of the spaces etc. I save that as a text file which I copy into HxD on my windows machine where I then save it as a .bin. However, the data will not decrypt for me. Is there a better way of doing this so that I am less likely to be causing errors?
Another place I may be having an issue is with the chip serial number. When I look up the serial using my Bus Pirate it differs from what the GPIO directory on the Pi calls it. Which one should I believe?
Thanks in advance!