Five years ago, I published what is probably the single most popular post on this blog – namely, how to reset a Stratasys material cartridge EEPROM so that it can be refilled with much cheaper third party filament.  Dan at gnurds.com took things a step further and came up with some great step-by-step tutorials on how to accomplish this, and even had a post featured in hackaday.  I received a lot of questions and feedback on the hack (and even helped hack a few machines running in the field), but the fact that the process requires modifying contents on the printer’s hard drive put it out of reach for users who were barred from doing any sort of ‘invasive surgery’ on the machine (generally students stymied by school officials).  What was needed was a truly ‘touchless’ hack that didn’t require any modification of the base machine itself – we needed a way to actually generate our own EEPROM data from scratch rather than simply re-using the EEPROM data as it had come on the cartridge from the factory.  The problem is that the EEPROM data is encrypted.  Worse, my understanding of how DES crypto is done on a practical level is pretty much zero – I’ve done embedded programming before, but this sort of stuff is far outside my area of expertise.

Fortunately, in 2013 a wizard cracked the EEPROM crypto and posted the code to github!  Benjamin’s sorcery is just what’s needed to build your own EEPROM image, and he’s put a great deal of time and effort into it for zero financial gain.  As a result, it really bugs me when I see people using his code to sell programmers for hundreds of dollars, with zero attribution for his work.  This post, then, shows start-to-finish how you can refill your own P-class Stratasys cartridge using only a Raspberry Pi.  It’s admittedly long and detailed, but I think it’s important to understand the whole process before trying to use any shortcuts.

The reason that it’s taken me so long to document this hack is that I previously had no real access to a P-class machine.  Fortunately, my friends at Into3D LLC have one in their shop and were more than willing to let me attempt refilling one of their empty cartridges.  It’s a Dimension BST 768, which fortunately is still supported for 2 more years.  This is what the front panel looks like with a near empty (1% material remaining) model cartridge:

Here’s that very cartridge – the label on top lists some applicable patents (6776602, 7063285, 7341214, D436111, and 7754807):

The side has a recycling information label and identifying information for the cartridge itself – we’ll see how that matches up with the information on the EEPROM itself.

Use a 7/32″ hex wrench to remove the 4 screws on the underside of the cartridge (I used a fold-up set to break them free first, then a standard L-wrench to remove them).

Then, flip the cartridge over and give the shell a few raps with your knuckles to shift the internal desiccant packs into the bottom half.  Carefully lift off the top half of the cartridge, exposing the 1% of material remaining on the spool:

Despite my dislike of using cartridges for 3D printers (it’s a lot of excess material to house the consumable), these are actually quite well designed – there’s a pair of very simple drive wheels at the corner exit, and the other 3 corners get desiccant packs.  The orange-brown circumferential seal has a spot for the filament to exit through, and the screws actually thread into brass inserts, not into the raw plastic.  A single cartridge can be reused many times, potentially lasting a fair portion of the life of the actual machine.  Parked right next to the drive wheels in a slot is the object of our interest, the EEPROM board itself:

Here’s what the front and back of the EEPROM PCB looks like:

In case anyone is wondering, the text on the chip itself is:


As noted in the original blog post, the chip is a DS2433 (originally a Dallas Semiconductor product, hence the ‘DS’, now owned by Maxim).  Importantly, it is a 1-wire device, hence requiring only 2 contacts to the chip.  As an aside, this nomenclature has always annoyed me – power and signal may be carried over a single wire, but you still need a ground connection.

Now, to extract those pesky bits from the EEPROM, all 4096 of them!  Technically, there’s a few more bits that we’ll need as well – a 48-bit serial number, 8 bits for CRC, and an 8-bit family code (0×23).  I’ve used a Bus Pirate before, and you can use an Arduino as well, but for this post I’ll be showing how to use a Raspberry Pi, since we can do everything on a single, standardized platform.  In this case, I’m using a Raspberry Pi model B with an Adafruit breakout board, and I started with a clean NOOBS image (v1.7.0 to be specific) on a freshly formatted SD card.

I booted the RasPi and was greeted with the installer – since I had the RasPi connected to my network, it provided me with network installation options, but I selected only the first option to install the Raspbian OS:

While that was installing, I prepped the breakout board.

I connected the black alligator clip to a GND (0vdc) terminal and the red alligator clip to IO4 on the breakout board (which is pin 7 of the RasPi header).  Note that pinouts on the RasPi can be very confusing – IO4 on the breakout board is not GPIO.4 on the RasPi as I had first thought, but pin 4 of the Broadcom BCM2835 processor at the heart of of the RasPi (also known as GPIO.7 on the RasPi).  You can read more about this confusion at wiringpi.com.  I connected a 2.2k resistor to a 5vdc terminal and the IO4 terminal – this acts as a pullup.

By this time, Raspbian had finished installing and I was looking at a fresh new desktop.  I find it easier to just SSH into the RasPi, so once I determined its IP address (just hover your mouse over the network icon in the upper right of the desktop), I could fire up PuTTY and connect right to a shell (you can certainly do everything via a terminal window on the desktop, though).

On a default install of Raspbian, the login is pi and the password is raspberry.  While Raspbian includes just about all the software we’ll need by default, the Python crypto library will be required later on, so run sudo apt-get install python-crypto right away to install that package (the RasPi will need to be network connected with internet access for this to work).  I then attached the breakout board to the RasPi and proceeded to do some testing with gpio to make sure that my wiring was correct.

I hooked up an oscilloscope to the red and black leads (you can use a multimeter, but a scope will let us see when EEPROM reads are occurring, which is handy when debugging), and saw that I had nearly 5vdc, which is just what I was expecting due to the 2.2k pullup resistor.

Now, let’s have a look at actually controlling the pin that the red alligator clip is connected to.  The gpio readall command gives us a snapshot of what the status is of all the header pins (again, see wiringpi.com for details).  By default, all the I/O pins are set to be inputs (note pin 7 is set as ‘IN’):

We can change the mode from input to output on that pin with gpio mode 7 out

And as soon as that command is issued, the voltage drops to zero:

Issuing gpio write 7 1 will bring that pin high:

Resulting in 3.3v output (RasPi digital I/O is 3.3v, not 5v):

That’s all for verifying that the wiring is correct.  There’s one final change to make before we can actually try reading in an EEPROM, and that’s disabling Device Tree (I understand it’s possible to get things working with DT enabled by means of some other configuration changes, but disabling it altogether is the route I went with).  Run sudo raspi-config to bring up the configuration menu, and select Advanced Options:

Then, select Device Tree:

Select ‘No’:

And DT will then be set as disabled:

Back at the main menu, select Finish and you’ll be prompted to reboot (select ‘Yes’):

With the RasPi rebooted, we’re finally ready to read in an EEPROM.  Recite the magic incantations sudo modprobe w1-gpio gpiopin=4 and sudo modprobe w1-ds2433 (note that you’ll need to run those commands again if you reboot the RasPi, so it may be worthwhile to add them to a startup script):

Now, connect the clips to the EEPROM – black clip to the ground pad, red clip to the data pad (you can tell which is the ground pad because it has a trace on all 4 sides connecting it to the ground plane):

If you have a scope hooked up, you’ll see that the voltage drops to 3.3 volts and then there will be a data read every 10 seconds or so:

We can cd /sys/bus/w1/devices/w1_busmaster1 to have a look at the connected 1-wire devices seen by the RasPi, and therein is a specific directory created for that EEPROM (23-0000014d4762 in this case – your EEPROM will be different!):

You can also use the xxd command to hex dump the EEPROM’s full UID as shown (0×2362474d0100006b).  This particular UID consists of the family code (0×23, which should be the same on all Stratasys P-class EEPROMs, except for those used on uPrint cartridges), the device serial number (0×62474d010000 – note the endianness) and finally the checksum (0×6b).  The screenshot also shows a dump of the 512 bytes of EEPROM data itself.  In order to actually do anything with this EEPROM data, though, we’ll need Benjamin’s code.

We’ll cd back to our user directory and then grab a .zip archive of the code via wget https://github.com/bvanheu/stratasys/archive/master.zip, after which we can extract it into a directory via unzip master.zip.

We’ll cd into that directory and try running the main program by executing ./stratasys-cli.py -h

This is just what we want to see!  If instead you get a number of errors mentioning crypto, make sure that you have the python-crypto library installed.  At this point, we don’t need to do any further configuration on the RasPi, and we can actually dive into the EEPROM data itself.  If you’ve managed to get this far, you’re probably capable of basic command line Linux work, so I’m going to gloss over those details from this point onward and let screenshots do most of the talking.  First, we’ll copy the EEPROM data out to a file that we can actually work with.

A directory listing confirmed that the resulting file is exactly 512 bytes in length, and all the formatting looks just like all the other Stratasys EEPROM dumps I’ve seen.  Let’s take one more look at the EEPROM UID, as we’ll need to format it correctly to feed into the stratasys-cli program:

We need to reverse the byte order of the shown UID, so instead of 23 62 47 4d 01 00 00 6b we’ll use 6b 00 00 01 4d 47 62 23 (remember, the family code of 0×23 is at one end, and the checksum is at the other end).  Here we finally feed the EEPROM UID and the EEPROM data through the program, using ‘prodigy’ as the machine type (any Dimension series machine should be ‘prodigy’, but a different machine type (Titan, Maxum, etc.) will have a different family name):

If you don’t have the UID formatted properly, the program will fail with a checksum error:

If we take a quick look at the data, everything agrees with the label that was on the cartridge – the color, serial number, manufacturing lot, and manufacturing date all match perfectly (I’m guessing that the timestamp on the EEPROM data is actually GMT).  Note that while the last use date is a separate entry in the EEPROM data, I’ve never seen it differ from the manufacturing date (maybe Stratasys intended to write this data back to the cartridge, but couldn’t be certain that the printer itself would actually have the correct day/time set).  A service manual I saw indicated that this timestamp was intended to be the date/time that the cartridge was actually first inserted into a machine, so perhaps Stratasys intended to have cartridges ‘expire’ after a certain amount of time.

The EEPROM stores material quantity in terms of cubic inches.  A brand new cartridge contains 56.3 cubic inches worth of filament, and the current level as shown on the EEPROM is under 0.75 cubic inches, so the 1% filament remaining message on the printer’s front panel was right on (there was actually a little more than that remaining on the reel, but the overage allows for nozzle purges, waste due to swapping cartridges, etc.).  The original hack worked by simply setting the current material quantity back to 56.3, but the printer would remember the serial number of the cartridge (and refuse to work with that cartridge serial again), so files needed to be deleted on the printer itself.  Since we can now create our own EEPROM images from scratch, we can simply change the serial number in addition to the material quantity, and the printer will be none the wiser.

In addition to decrypting the EEPROM data and displaying it in a human readable format, Benjamin’s program can provide all the parameters needed to generate that very EEPROM data, which is extremely handy.  We’ll simply tack on the -r option to the command we just used:

We only need to change the highlighted options to create our desired EEPROM image:

Reading the generated neweeprom.bin file back through the program shows that the serial number is now different (I incremented the value by 1000 rather than 1 just in case there were consecutively serialized cartridges the machine had already seen), and the material quantity is back to ‘full’.  Now, we can finally write that file back to the EEPROM itself (remember to use sudo when writing to the EEPROM due to permissions):

A quick hexdump directly from the EEPROM verifies that we’ve modified the contents successfully.  Note that the new image we generated is only 113 bytes, while the original EEPROM data is a full 512 bytes.  This is because everything after the ‘STRATASYS’ at 0×69 is random garbage (early on, Stratasys simply padded out 0×71 onwards with zeros), so that portion of the EEPROM can be left unchanged.  That’s all that we need to do with the RasPi – the EEPROM can be disconnected and set aside.  All that remains is to reload the cartridge with fresh material.

My favorite current filament is the ‘High Performance ABS’ from Coex3D – I’m partial to them because they’re local, their product quality is excellent, and Chris gave an amazing presentation on polymer processing and filament extrusion to our 3D printing user group a few years ago.  He listened to my pleas for MG94 filament and thankfully started producing it.

While Coex3D reels fit right into my FDM series machines, they don’t fit into P-class cartridges (the bore is just a little too small, and there is a rubber piece attached to the top shell of the cartridge that would interfere anyhow).  So I needed to respool the new filament onto the old reel.

In fact, respooling the filament itself is probably the hardest part of the entire process!  I admittedly got a bit hackish with the use of electrical tape as a makeshift drive dog, but it worked.

Make sure that you have the desiccant packets in place, the EEPROM PCB in its slot, and the drive wheels in position, then very carefully feed the end of the filament through the hole in the disc portion of the gasket.  Hold the filament in its guide slot, and carefully place the top shell half back in place (this is pretty tricky without having the gasket jump out of place).  Flip it over, assemble the cartridge with the 4 screws, and our work is complete.  Now, for the moment of truth…

After loading the refilled cartridge into the printer, it showed a 100% full model spool!

Of course, the proof is in the prints, and the machine is now happily churning out parts far more inexpensively than before (and with better material properties than the OEM P400 filament had).


1) Benjamin’s code works for other Stratasys printer families as well, including the big T-class and Maxum/Quantum machines.  It will even decrypt and generate binary images for uPrint cartridge EEPROMs.  However, uPrint cartridges use a different EEPROM model that unfortunately utilizes an HMAC authentication scheme for writes.  So while you can read EEPROMs and generate new .bin files, actually writing them back to the EEPROM is impossible without knowledge of the secret key used for the HMAC authentication.  If you only have access to a uPrint, you’re kind of stuck. [12FEB2017 addendum]  It turns out that an HMAC protected EEPROM can be re-written by using the DIAG port on the printer.  ‘Odin’ discovered this workaround and authored these concise instructions for the hack.  This isn’t quite ‘touchless’, but until someone breaks or sidesteps the HMAC protection, it’s the best option.

2) 56.3 cubic inches isn’t actually the maximum material quantity you can set on the EEPROM.  It’s a floating point number, so the sky is the limit!  However, on a P-class machine, 60.0 cubic inches is the maximum that the printer will accept as valid, as anything larger will instead be considered zero. [22FEB2017 addendum] Reports indicate that larger volumes can be used, but the ‘initial material quantity’ field needs to be similarly large.  However, others (Odin, for one) find that this doesn’t work on their machine, so this could be a difference between firmware revisions.

3) I mentioned using an Arduino to read/write the EEPROM.  There’s actually a fork of Benjamin’s code available on github called CartridgeWriter that runs in Windows and interfaces with an Arduino for EEPROM reads/writes.  I haven’t tried it myself, but others have used it successfully.  I prefer running Benjamin’s code directly on a RasPi due to the amount of control it provides.  Specifically, it makes some automation possible, such as…

4) …this clever little EEPROM rewriter made by Sneaks Hacks.  He’s posted the wiring schematic and STL files for the housing, and is currently working on an updated version as well as documentation for people wanting to build their own.

5) The Stratasys EEPROM PCB has a surface mount 4.7k pulldown resistor right next to the DS2433.  While most wiring schematics for reading/writing a Stratasys EEPROM show to use a 4.7k pullup between 5v and the data pad, I used a 2.2k to help ensure that voltage to the DS2433 remains in an acceptable range.  You can certainly start with a 4.7k pullup and reduce the resistance if you’re having flaky results, but I don’t think I’d go below 2.2k.

6) Benjamin notes that use of the –output-file option when generating EEPROM images isn’t actually correct in a traditional Unix sense, and that I/O redirection is really the proper Unix way to get binary output from stratasys-cli.py (that is, using something like ./stratasys-cli.py –foo –bar > my_file.bin).  I think using –output-file is a little easier to see and understand what’s going on, but if you’re building an automated system like Sneaks Hacks did, using stdout can help streamline the processing chain.  For example, you could write directly to the EEPROM and save a backup of the image all in one go by using something like ./stratasys-cli.py –foo –bar | tee backup_image.bin /sys/bus/w1/devices/w1_bus_master1/23-0000014d4762/eeprom.

7) Everything in this post is simply the compilation and distillation of other people’s hard work – I simply wanted to bring it to a wider audience.  These are the folks who deserve all the credit:

  • Huge thanks goes to Mjolinor, who I believe was the first to pioneer using a RasPi as an all-in-one solution for rewriting Stratasys EEPROMs.
  • Thanks to the anonymous and unnamed people (you know who you are) who have assisted in developing and testing these techniques over the past few years and helped review this post before publishing.
  • Steve, Joe, and John at Into3D LLC for letting me use their Dimension BST 768 as the guinea pig for this project.
  • First, last, again, and finally, Benjamin Vanheuverzwijn.  This man is an absolute electronic wizard and none of this would have been possible without him.  Send him coffee.

55 comments so far

Add Your Comment
  1. What is the current state of refilling uPrintSE+. Cartridge eeproms are password protected from write events. Can we write to new eeproms and load those in? or is there othr problems aside from sourcing a compatible chip.

    • Just as you say, the MAC protection means this will not currently work with uPrint SE cartridges.

      • Your answer is bit above my understanding.

        There is one commercial solution where a new eeprom is written as a fresh cartridge.

        Question :
        Why can we not write our read of a fresh data cart to a non pass work protected eeprom.

        *sending email.

  2. Is this do-able with the CubePro cartrages? They also use the DS28E01 chip, so looking at your reply to Johnny I assume that’s a no.

    • 3DS uses their own data storage format on the EEPROM, so Benjamin’s code won’t work with them – I’m not sure if there are any similar projects to rewrite them.

  3. This was such a huge help! the new eeprom-holder stl files are so nice! I’m still tweaking my setup to match our workflow but man this is great.

    Keep up the work, your blogposts are golden!

    • Thanks, glad you found it useful!

  4. I’m pooping. How do you pronounce “Vanheuverzwijn”?

    • I’ve only communicated with Benjamin via email, so I have no idea!

      • I’m surprised you didn’t comment on the “I’m pooping” comment. I believe I actually was pooping at the moment I posted that.

        • Did you want me to post the Bristol stool chart in response?

  5. I am attempting to read off the eeprom data but I am not seeing any response on the scope with the above configuration. I am also not seeing the serial number in w1_bus_master1. I am applying 3.3v power and ground as per the above instructions. Any suggestions?

    • Did you make sure to disable Device Tree? That sounds like the behavior you’ll see if DT is still enabled.

  6. The version of raspbian does not include this option in raspi-config but there is a option to turn 1wire on and off.

    • If you can’t disable DT, try adding the dtoverlay option is described here: http://www.modmypi.com/blog/ds18b20-one-wire-digital-temperature-sensor-and-the-raspberry-pi

      If that doesn’t work, try using v1.7.0 of NOOBS (which will allow you to disable DT), as that should allow you to perfectly replicate everything shown.

      • It did not work and I am unable to find a NOOBS download for version 1.7.0 would you be able to point me in the right direction as to were that would be located?

          • Add this line (dtoverlay=w1-gpio) to /boot/config.txt? Is this the same as disabling DT?

            • No, that doesn’t disable DT – that’s the proper way to use 1-wire with DT. I opted to go the non-DT route so that my guide wouldn’t require directly editing any files (hopefully keeping things a little simpler for users).

              If Andre is correct regarding new builds not allowing for DT to be disabled, then you’ll definitely need to use dtoverlay.

  7. I started with RasPi3B, Noobs 1.9.2 today. Installed and also found out that DT is not available. Configured 1Wire as on and continued all the other steps. Worked fine and the reprogramming is functional.
    System: Stratasys diemension SST 1200es

  8. I tried to CD into the eeprom data and reading it using xxd as mentioned in your post. But it returned ” xxd: 2362474d0100006b: permission denied

    Any idea why?

    • What are the permissions on the file? Have you tried running xxd as root?

  9. Yes. I tried sudo xxd -p id 23-000001174f17. I got xxd: 23:0…7: permission denied

    This was the only bottleneck. I went ahead with the rest and got exactly similar results as yours. But when I plugged it to the 3d printer the cartridge still showed empty(just as before). Any chance I can contact u through mail? Hjjkrishnan@gmail.com

  10. Great info! Thanks for the tutorial. I managed to get this to work perfectly on our Dimension 1200es. However, I used Cartridge Writer GUI and an Arduino – The whole process from nothing to a working setup took me no more than 15 mins. That GUI simple to use but has a couple of bugs that can be worked around, or fixed if anyone feels like it, as the source is all available.

    While going through some of our spent cartridges I noticed some of the newer ones (e.g. Mfg Date: Jan 2016) had different looking PCBs. I took one apart and noticed it has a DS24B33 on it as well as another IC + some more passive components.

    I think it’s a 555 timer (http://www.intersil.com/content/dam/Intersil/documents/icm7/icm7555-56.pdf). Not sure what they are using it for thought. Thoughts?


    I was still able to read it with no issues and also write to it. Haven’t tried it in the printer as I’m concerned it could ‘brick’ it or something.

      • Well, that certainly is interesting! I’m not sure why they’d add a 555 timer to the circuit, but I’d guess that it’s something to do with using the DS24B33 versus the original DS2433. This application note covers differences between the two, and I’m assuming the 555 must be accommodating notes 1 and/or 2, the longer read low time and recovery time on the ‘B’ model of the chip.

        • I think you’re correct.

          Interesting that they opted to add more cost to the cartridges rather than push a firmware update to the printers to rectify. Maybe it may have not been possible or probably a better “user experiance” this way.

          Plus they afford to ship those cartridges with a little gold if they wanted to – those things are damn expensive.

  11. Does anyone know what the legalities of doing this hack are?

    Our printer is out of warranty and we don’t have a service agreement but we do get them to come out and service the machine every now and then when something goes wrong. Would they start to refuse to offer support?

    Can they legally brick the printer if they detect someone has tampered with the cartridges? (Maybe not now but in future if they update firmware etc).

    We’re commercial users of the printer and the price of the cartridges has gone out of control. We’re spending many thousands per month on material. It’s almost no longer viable to continue to use it hence me searching for alternatives.

    • As far as copyright law is concerned (if Stratasys could even somehow claim copyright protection on the EEPROM data), you are clear and free – Public Knowledge has a little bit of info (hat tip and high-five to Michael Weinberg, who is an all-around awesome dude).

      On a more practical level, Stratasys has no way to tell that you’ve used third party filament. After all, this hack is 100% touchless and does not need any modification of the printer itself. Any firmware updates that they make need to be absolutely solid, and I cannot imagine that they would ever intentionally brick a machine. My day job is working for an industrial machinery manufacturer – on the extremely rare occasion (only once as far as I know) that we’ve even coded the capability to brick a machine, it was done with the end customer’s full knowledge and consent (customer couldn’t afford full purchase price, so we negotiated a reduced price, but the machine would lock up after a set number of cycles. If the customer paid the remainder, we’d provide an unlock code to remove any limits).

      I’ve dug through some Stratasys code, and their people are very conscientious about making darned sure that the machine is operable after a firmware update. I don’t think you have anything to fear – the vast majority of Stratasys operators have no idea that third party materials are available, that this hack exists, etc., and Stratasys is happy to keep it that way.

  12. Hello!) Could you please help me
    I write
    ./stratasys-cli.py eeprom -t prodigy -e 6d0000015d66b823 -i original23-0000015d66b8.bin
    and received

    Exception: invalid content checksum: should have 0×6658 but have 0×7c0a

    I have Dimention elite BST or SST 768
    EEPROM id 23b8665d0100006d
    reverse 6d0000015d66b823

    I try write fox,fox2, prodigy and ather, but also reveive checsum error with other num

    • You may have a bad read on the EEPROM – can you try re-reading it?

      • thank you very much, it worked

  13. Does anyone have a new generation board I can buy off of them, I am looking to make some replacement boards for myself and the old eeprom is no longer available so I want to see if I can make a clone of one of the newer ones


  14. Thank you very much! Working with old cartridges (2010-2013) and everything works like a charm!
    Very much grateful!

  15. “12FEB2017 addendum] Reports indicate that larger volumes can be used, but the ‘initial material quantity’ field needs to be similarly large.”

    On my SST 1200es it is not possible to use larger volumes than 60 cuin in the “current quantity” field. I can set every quantity in the initial field but current is limited to 60cuin. Every higher volume causes an error in the SST 1200es.

    • Which firmware version do you have on your machine?

  16. Hello , we have couple of Fortus 250 MC Machines , can any one tell me this tutorial works on the same , if not what’s the alternative . Thanks

  17. Hey I’ve got a problem reading data from the DS2433…
    Every time I pull/test data, it’s different. I ran
    watch -d -n 1 xxd /sys/bus/w1/devices/23-000001418587/eeprom
    and see what happens:


    How is this possible? My wiring is exactly like yours. Drivers work fine. Ran the setup with a 2.2k resistor, a 1.5k resistor, no pull-up at all. Every time the same problem. (Though sometimes the no-pull-up-setup didnt give me any data, sometimes it did)

    • Can you try it with a different EEPROM? Everything after the ‘STRATASYS’ is garbage, so as long as you can get a clean read up to that point, it’s all you need.

      • Oh yes. Fantastic! Wrote you java app that handles reading.
        Lists all the connected chips, reads the chips multiple times, then gets the most probable byte combination. Usually has a reliability of 99.3%. Stores it into a file. Dumps the complete stratasys-cli call, so you only have to copy-paste it.

        Re-coded the chip and read it again, all perfectly fine.

        Now I’ll extend the app to handle all the steps.
        So just connect the chip, backup is made, id and quantity are refreshed and written back to the chip in one go.

        Thanx for all the help and the great description.
        I’ll drop a link to that project later.

  18. I have a fortus 400 MC, somebody knows if this method works with it?

  19. Hi,

    I am a noob in this, but we have a uPrint SE Plus, but the eeprom looks different:


    How do I program those?

  20. Here are the links again:


    • You’ll need to create the .bin file separately and program the EEPROM via the DIAG port on the printer itself, since that model printer uses cryptographically write-protected EEPROMS. You can find information in this thread.

  21. Very important to know is, that empty eeprom of the uPrint are read only. You need afaik at least 1% filling left to write the eeprom via diag port l.

  22. Fantastic, thank you for the reply! :)

  23. Has someone used this on a fortus 400 mc cartridges?
    it also has a ds 2433 chip, so should it work?

  24. AFAIK yes. You have to use “fox” as printer type for generating a new one.

    For example with bvanheu’s tool:
    stratasys-cli.py eeprom –machine-type fox–eeprom-uid ffdc00000034f8d223 –serial-number 489435455.0 –material-name NYL12 –manufacturing-lot 7567 –manufacturing-date “2017-01-01 01:01:01″ –use-date “2017-01-01 01:01:01″ –initial-material 92.0 –current-material 92.0 –key-fragment 55aa55c395bf4ebe –version 1 –signature STRATASYS -o 400MC.bin

  25. Hello, we are students that are working in a company. We have a problem that we don’t know how to resolve: when we copy the neweeprom.bin file into the chip and put it into the printer, it says “Model empty” or “Could not read model”. Could you help us, please?
    (Sorry for our English, we are Italian)

    • Which model printer are you working with? How did you create the new image file? Did you verify that it was written back to the EEPROM properly?

      • Thank you for the answer. We realized that we were not modifying the serial number, so the printer was saying that.
        Last question: is it possible to do all of this automatically during the boot of the Raspberry Pi ?

        • Absolutely, though you’ll certainly have to create a script to do so.

  26. could you sell me all complete ,fuctioning..?

    • Just buy a Raspberry Pi and breakout board and follow the instructions in the post!