And now for a bit of EEPROM hacking

[3MAR2016 Note: A much newer, better method has been developed and is documented in this post.]

A common question among commenters to this blog when I write about my Stratasys FDM 1600 is “how did you hack the cartridge?”  Newer Stratasys machines such as the Dimension series (P-Class machines – I assume named after the Prodigy, which I think was the first Stratasys machine to use cartridges) don’t have plain old wire welding type spools like the old FDM series – instead, they have the filament stored in a large cassette.  This is nice as it keeps the filament dry without having to keep it in a dry box and it makes loading in new material (or swapping colors) a breeze.  On the down side (as many Stratasys owners have apparently discovered), Stratasys went the route of inkjet printer manufacturers and have ‘chipped’ their cartridges so that you can’t simply refill the cartridge with material and continue on.  While this isn’t a hindrance to me and my old machine, I’ve still been curious to know if there’s a way around this (if I ever come across a Dimension for cheap, I’ll need a way to feed it as well).  Note: I understand the big T-class machines (named after the Titan model, I assume) still use large spools, though I believe the spools also have a chip module (but hey, if you can afford to buy a T-class, the consumables cost probably isn’t a big concern).

Inside each Stratasys cartridge is a Maxim DS2433 one-wire EEPROM (in a SO-8 package) that the machine communicates with. This is a simple 4kb (that’s kilobits – only 512 bytes of storage) device, and reading/writing them is reasonably straightforward – a library most likely exists for 1-wire communication no matter what your microcontroller of choice is (Arduino enthusiasts, look here). Dumping the contents of one yields hexadecimal gibberish, unfortunately. What’s more, you can’t simply clone one of them, as each has a unique 48-bit serial number lasered onto the die at the time of production, and this serial (presumably) is used as the seed to encrypt/obfuscate the EEPROM data. This has been enough to dissuade most tinkerers from playing further with the system, though Bolson Materials may very well have cracked the code, as they are able to provide new EEPROMs with their cartridge refill spools.

Thanks to some hacking by the shadowy figure known as ‘Dervish’, it’s been found that only a small portion (12 bytes) of the EEPROM is dedicated to storing how much material is left on the spool.  As a cartridge was used, the EEPROM was read out at various points and only bytes 0x58-0x63 changed over the life of a cartridge.  Specifically, here’s the layout of data on the EEPROM as known thus far as a result of reading EEPROMs from several brand new cartridges:

0x00-0x41: scrambled data (commenter lgg2 noted that 0x28-0x2F is identical to 0x30-0x37, highlighted in purple)
0x42-0x45: 0x00000000
0x46-0x47: scrambled data
0x48-0x4A: 0x55AA55 (highlighted in green)
0x4B-0x4D: scrambled data
0x4E-0x4F: 0x71BE, 0x72BE, 0x73BE, 0x74BE, or 0x75BE
0x50-0x51: scrambled data
0x52-0x57: 0x000000000000
0x58-0x63: filament remaining (scrambled data, highlighted in yellow) – on an unused spool, 0x62-0x63 is always 0x4BB9, but this gets modified (along with 0x58-0x61) as the cartridge is used.  Perhaps 0x62-0x63 is an unencrypted checksum?
0x64-0x67: 0x00000000
0x68-0x70: 0x535452415441535953 (‘STRATASYS’ in ASCII, highlighted in dark blue)
0x71-0x1FF: scrambled data

Simple enough, right?  Just read in the EEPROM at 100% full, respool it with generic material when empty and write the 100% full data back to the EEPROM…  Well, not quite.  You can certainly use this respooled cartridge in a different machine, but not in the same one, as they remember what cartridges they’ve already used (that serial number on the EEPROM).  This is where Dervish tore into the guts of the machine and began the really clever hacking.  When you open up the side panel of a Dimension, here’s what you see (image taken from Brad Rigdon’s Print To 3D gallery):

Brad also has a nice video on youtube that shows the full workings of the machine. The electronics appear to be composed of 3 boards – the large PDB (Power Distribution Board) on the left, the SBC (Single Board Computer, just a PC) in the center right above the hard drive, and what appears to be a motion controller board (in the upper right, connected to the SBC via a 16-bit PC/104 header). As per the troubleshooting section of the Dimension/SST Service Guide, the motion controller board in the upper right is known as the ‘186 board’.  The SBC pictured appears to be an Ampro P5v, though some Dimensions use a Nova-600.  After connecting a keyboard and monitor to the SBC, Dervish found that the computer is running Linux (Red Hat 8, specifically – not Fedora 8, but the circa 2002 version with a 2.4.x kernel).

By rebooting the system he was able to enter single user mode (at the LILO prompt, enter ‘linux single’) and could change the root password to whatever was desired (type ‘passwd’ at the prompt, enter a new password, then enter again to confirm). After rebooting once more into standard mode as root with his newly minted password, he modified /etc/sysconfig/iptables to open up port 22 so that he could ssh into the system and hack remotely without having to be at the console itself (the sshd daemon does not run by default, so adding the line ‘/etc/init.d/sshd start’ to /etc/rc.local is also required).   While he had been able to modify temperatures on the machine by using Stratasys’s ‘Maraca’ software (the CatalystEX software offers no ability to tweak the system), direct access to the SBC allows much greater control over process parameters such as adjusting rollback.  All the configurations are stored within the /mariner/config tree (the hard drive image covers multiple models), and it can be tricky to determine which ‘gender’ (kona, lanai, spinnaker, oahu etc.) corresponds to a given machine, but noting which directory has the most recent modification date is a dead giveaway.

The holy grail turned out to be the discovery of an innocuous sounding file named ‘system.dat’ located in the root directory.  This is where the Dimension apparently stores a list (in binary) of all the cartridge EEPROM serial numbers that it has seen before.  Delete this file and the machine gets amnesia, allowing respooled cartridges (with the EEPROM rewritten to show 100% full) to be used again.  I assume creating a cron job to delete this file periodically (or using rc.local to delete it on startup) would also work.

As far as I know, this constitutes the cutting edge of Stratasys hacking – I’ve heard rumors before of people having bypassed the cartridge EEPROMs, but this is the first concrete information I’ve seen on how to accomplish it.  If anyone has further information, please leave a comment!

244 thoughts on “And now for a bit of EEPROM hacking

  1. Hello Peter,

    We are buying a SST version, but will be delivered at February. If of interest, I have the 768/Elite Service and Maintenance Manual (713 pages), so you can give a look at it.

    About materials, go to take a look on isquared. It is a german company delivering ABSplus and ABS M30 materials for the 768 printers, and it costs 1/3 less compared to original ones.

    Would be nice if we could cooperate in this upgrade challange 🙂

  2. Hey CesarN,

    I was wondering if you could post a detailed how to of how you got it to work for you. I saw you responded to Fabiano about what you did but was hoping you could explain it in more newbie friendly terms. Thanks!

  3. It seems to me that we should just be able to source the DS2433 – it’s a commonly available part, and flash the microcontroller with the same (or similar) micro code as on the factory ones. A careful hack might disable the part of the code that decrements/increments the valued stored in the counter.

    This means that it won’t be neccessary to bypass the ID code in the chip, provided the user data in the chip is correctly implemented. The trick is figuring out how to decipher the user ID data, compared to the chip code. I see multiple avenues for attack here, since the cartridge chip is easily probed, but it will basically boil down to whether the cryptographic polynomial used for the user hash can be bypassed. It might come down to looking at a de-capped device under a microscope.

  4. May have posted too soon. Closer reading of the data sheet indicates that the ID code is not a user setting like some RFID systems (as I’d expected), but entirely fixed. Soooooo, if that’s the case, then it might be possible to simply overwrite a new chip and do a brain-swap. Anybody want to try?

  5. The DS2433 is not a microcontroller – it’s just a serial EEPROM. The unique serial number of the EEPROM is used as part of the encryption key, so simply copying the contents from one EEPROM to another will not work, as the key is different.

  6. Hi all,

    first of all, thanks for the nice docs … I got a BST 768 into my access lately and due to the same motivation to use cheaper or other materials I did open up our machine as well. My colleagues, who were working with the machines did not have the courage to do it 🙂 …
    I also did “backups” of all our cartridge chips using a simple 1wire-usb adapter with the basic 1wire demo software, what allows direct reads and writes. I even played around with a simple battery powered microcontroller circuit what would record the chip content (of an unused cartridge) and write back that data when the spool came close to 0% …
    Next time when I have spare time, I will move the breadboard circuit to a more professional looking built 🙂 … Probably a TI Launchpad micro kit with USB for approx. $5 could be a good platform as well.

    What would be great if those who made experiences with different materials could set up a table with sources, quality evaluation and usage hints, so that others (including me) could more easy gain from those experiences.
    So far we have used original Stratasys materials, Bolson and noname chinese ABS, all with good results without changing parameters. To be more productive here, I probably could play around with the MARACA tool, if I could get hold of it, too.
    In the moment we are looking for good and cheaper breakaway support material. Any good source in Europe known ?

  7. Hi Jarno,

    I have the Elite version of the printer at my work. is it possible for you to send me the service and maintenance manual ?

    I will try to hack it.

  8. I’ve a stratasys 400mc.
    Based in Central UK.
    I’d like to try this modification. I’m looking for a linux consultant to help..Has anyone any recommendations?

  9. Hi all,

    I have a SST1200 which does not boot. The Display on the panel remains empty.
    I tried Power cycling many times. On the Diag port I got the following:

    Running POST
    Internal Flash CRC Test [PASS]
    SDRAM Addr Test [PASS]
    ISA DPM Addr Test [PASS]
    Pmd DPM Data Test [PASS]
    External Flash CRC Test [PASS]
    NVRAM check [PASS]
    Supply Voltages
    5V supply: 5.07V Range: 4.85 to 5.15 [PASS]
    12V supply: 12.00V Range: 11.28 to 12.72 [PASS]
    15V supply: 16.00V Range: 13.50 to 16.50 [PASS]
    -15V supply: -15.77V Range: -13.50 to -16.50 [PASS]
    10V supply: 10.00V Range: 9.84 to 10.16 [PASS]
    3.3V supply: 3.30V Range: 3.23 to 3.37 [PASS]
    Navigator checksum: 0x12345678
    Navigator version: 0x28400F23
    Pilot checksum: 0x12345678
    Pilot version: 0x34100F20
    Pmd DAC Tests
    XSin@0.00V: 0.01V Range: -0.06 to 0.06 [PASS]
    XSin@2.15V: 2.24V Range: 1.96 to 2.34 [PASS]
    XSin@4.30V: 4.35V Range: 3.98 to 4.62 [PASS]
    YSin@0.00V: 0.01V Range: -0.06 to 0.06 [PASS]
    YSin@2.15V: 2.25V Range: 1.96 to 2.34 [PASS]
    YSin@4.30V: 4.33V Range: 3.98 to 4.62 [PASS]
    ZSin@0.00V: 0.01V Range: -0.06 to 0.06 [PASS]
    ZSin@2.15V: 2.25V Range: 1.96 to 2.34 [PASS]
    ZSin@4.30V: 4.34V Range: 3.98 to 4.62 [PASS]
    Controller board EEPROM CRC Test [PASS]
    Controller Configuration ID: 0
    Controller part number: 202414-0001
    Controller serial number: 0641-002175
    Power Dist board EEPROM CRC Test [PASS]
    PDB Configuration ID: 0
    PDB part number: 202143-0003
    PDB serial number: 0647-001636
    CPLD version: 29
    ColdFire version: 0 rev: 0
    Mariner build: 1710.0
    Cause of last reset: Power Cycle
    POST successful
    last act:289216 / req:244297 / malloc:651/0 / stk:1180/11196
    act:279648/268768 / req:234729/231646 / malloc:538/0 / stk:2436/11196
    Running POST
    Internal Flash CRC Test [PASS]
    SDRAM Addr Test [PASS]
    ISA DPM Addr Test [PASS]
    Pmd DPM Data Test [PASS]
    External Flash CRC Test [PASS]
    NVRAM check [PASS]
    Supply Voltages
    5V supply: 5.06V Range: 4.85 to 5.15 [PASS]
    12V supply: 12.00V Range: 11.28 to 12.72 [PASS]
    15V supply: 15.98V Range: 13.50 to 16.50 [PASS]
    -15V supply: -15.74V Range: -13.50 to -16.50 [PASS]
    10V supply: 10.00V Range: 9.84 to 10.16 [PASS]
    3.3V supply: 3.30V Range: 3.23 to 3.37 [PASS]
    Navigator checksum: 0x12345678
    Navigator version: 0x28400F23
    Pilot checksum: 0x12345678
    Pilot version: 0x34100F20
    Pmd DAC Tests
    XSin@0.00V: 0.01V Range: -0.06 to 0.06 [PASS]
    XSin@2.15V: 2.25V Range: 1.96 to 2.34 [PASS]
    XSin@4.30V: 4.35V Range: 3.98 to 4.62 [PASS]
    YSin@0.00V: 0.01V Range: -0.06 to 0.06 [PASS]
    YSin@2.15V: 2.25V Range: 1.96 to 2.34 [PASS]
    YSin@4.30V: 4.33V Range: 3.98 to 4.62 [PASS]
    ZSin@0.00V: 0.01V Range: -0.06 to 0.06 [PASS]
    ZSin@2.15V: 2.25V Range: 1.96 to 2.34 [PASS]
    ZSin@4.30V: 4.34V Range: 3.98 to 4.62 [PASS]
    Controller board EEPROM CRC Test [PASS]
    Controller Configuration ID: 0
    Controller part number: 202414-0001
    Controller serial number: 0641-002175
    Power Dist board EEPROM CRC Test [PASS]
    PDB Configuration ID: 0
    PDB part number: 202143-0003
    PDB serial number: 0647-001636
    CPLD version: 29
    ColdFire version: 0 rev: 0
    Mariner build: 1710.0
    Cause of last reset: Power Cycle
    POST successful
    last act:289136 / req:244217 / malloc:651/0 / stk:1188/11196
    act:279648/268768 / req:234729/231646 / malloc:538/0 / stk:2212/11196

    Any help would be fine.

    Thanks,
    Robert

  10. Hi folks,

    hope you could help out as our BST 768 stopped to work. I assume there is something wrong with the alignment before starting to build the part.
    Whenever were are starting a printout the BST 768 starts to work, the build platform is moving around for some seconds and then the system shows CODE 14,100 on the LCD display and the BST 768 is rebooting.

    Unfortunately, the CDROM with the error codes is archived somewhere where we can’t find it. Probably somebody could help us out with the meaning of that error code or
    behavior ?

    Thanks,
    Yogi

  11. Hi guys!

    I have an older BST1200 with recently updated firmware that I’ve been trying to figure out. I’ve written lines into the rc.local to delete any system.dat files I could find among the various partitions but the reloaded/reflashed cartridges don’t seem to be resetting. If I wipe the printers HDD and reload it with my backup.img the reset cartridges can be used so I figure the firmware update must have started storing the EEPROM data in some other files (aside from just in the system.dat files). Any recommendation on how I could go about finding those files?

    Best,
    Kain
    kain3713@gmail.com

  12. HI Folks,

    after some search and analysis it turned out that the sensor Z home became defective, but only, when the printer was heating up …
    We ordered the switch (a part worth 6€ ) and replaced it and now our BST 768 is running as well as before …

  13. hello peter i am based in Argentina, and I have a 768 now that I have to calibrate, it is used machine. Could you share the Maintence Manual with me. We have no manual down here. Also you advice buying the material from inquired or hacking the machine? Thanks.¡ José

  14. other think
    I have a problem with a full cartridge. It’s blocked because the tip is inside.
    I cut it off and I don’t even see them.
    Is there a chance for this cartridge?

  15. Hi

    My friend have a SST 768 and the hard-drive seem to malfunction. Is there any way that he can get the software (OS etc.) to setup another drive ?

    Regards

  16. Hello all.
    We have a Dimension Elite that we are working over. We successfully installed the rc.local trick to remove the internal cartridge logs, but have been having problems dumping the cartridge chips. We have tried both the arduion approach (1 wire interface etc), and the DIAG port trick. The DIAG report does not echo anything back, and the chips respond with all zeros (including the ROM portion), so it feels like we are doing something wrong on both fronts.

    Can someone look over my code snippet and tell me what I am doing wrong? Should I post a link?

  17. Guys, may be someone of you has Insight software? it should be relatively new, cause i want to experiment with fortus 250mc files.
    I’ve done some research and now i am able to print files with 0.07″ layer height with my sst1200es.

    I wiдl appreciate any help from you. Thanks. you can find me by mail ashanin @ gmail.com (removes spaces)

  18. Well,

    I always used a cheap USB-1WIRE dongle to connect and read/write the chips. BUT, we always are using the DIAG terminal interface as well.
    Is the DIAG not answering anymore or just not giving back any EEPROM data ?

  19. Is there any Progress on this? I’m also trying to get a read from it with an Arduino but it won’t work.

    Is it even possible with an Arduino or do I Need to get a Bus Pirate? I don’t want to cut a trace or anything non reversable because I’m trying to build a deviece to simple scan the chip and write it back later.

  20. Hi Jarno,
    i am a teacher and my school have buy a Elite 3d printer, could you send me “the 768/Elite Service and Maintenance Manual (713 pages)”
    thanks

    vincent

  21. Eureka! Nice site. Now, my problem. I have an FDM-3000 which was running fine until I took head out to clean nozzels. Now on startup, the CTM150 user keypad shows that it booted and passed by displaying “Version 2.00 Test OK”, but the FDM controller no longer displays it’s v9.07 check or the controls for the feed motors to LOAD/UNLOAD or any other FDM controller interface. It did a pin-to-pin continuity check of the head-to-controller cable, all good. I tried pressing the RESET button which connects to the DS1232 guard chip, but no “reset” of the FDM controller. I ordered a new HPC46003V20 microprocessor and DS1232 chip, but I read in the data sheets that the microprocessor has built in user programmable ROM in addtion to the two EEPROM’s called “HI” and “LO” mounted on the FDM controller board. I would really like to connect with someone who can troubleshoot an FDM-3000 for cash or sell me the FDM controller service manuals and any BIOS that I need to flash to the microcontroller. It’s a great machine, just some little fiddly component is FUBAR and needs repalcement. Please advise. Thanks.

  22. Also, I wondered if any clever fellow has worked up an Arduino-based controller that can replace the Stratasys controller. That would be a major benefit.

  23. im using a BST120es but somehow i fail to get a serial connection to the diag port.
    i tried three different USB2Serial converter, different cables, swapping TX/RX a.s.o.
    and all the possible settings for the com-port (38400 8N1) but i never get anything back
    from the printer. i used putty (win7), minicom and gtkterm (ubuntu) nothing worked …

    does anyone have an idea hint what the problem might be ?!

    thnx
    Marc

  24. Any chance you can try using a computer with a built-in serial port? I have had mixed results with USB converters in the past, and I run my FDM printers off of computers with built-in ports.

  25. I’m adding this line:

    rm system.dat

    to etc/rc.local, but it doesn’t seem to be doing the trick. Any pointers would be appreciated.

    Jeff

  26. Also, I notice that etc/grub.conf is now blinking with a red background in the directory listing. How can this be fixed?

    Jeff

  27. Thanks all for all the wonderful information but I am having problems with hacking a dimension 1200. I have followed all the procedures and no go. Has anyone out there simplified the procedure any more? When I try and re-flash the chip it just sits there and does nothing. Any help would be greatly appriciated.

  28. The newest firmware update I downloaded from the server updates the kernel to 2.6.23.15-137.FC8 from the old 2.4.18-24. Instead of the LILO boot it uses GRUB and loads a disk image at boot.

    I guess it’s a nice upgrade but if you opened port 22 before. Updating to this firmware. Closed that hole.

  29. It can certainly be reopened – also, I believe the filesystem is mounted read-only now, so remount r/w before you try making any changes to the firewall settings.

  30. I mounted the drive in another machine with Ubuntu. chroot’d to the drive from the printer. erased the shadow file from /root/etc/ and then ran passwd root to change the root password. I changed all of the grub.conf files and removed the RO from them.

    Best part of this whole thing. Good by Vi. Nano is part of the update.

  31. Yep, mounting the drive in another machine is the easiest way – if you are doing the modifications right on the live system, though, it’s a little trickier with having to remount the filesystem and such.

  32. Just for the fun of it. chkconfig –add sshd will add the sshd to the boot init. chkconfig sshd on turns it on. Then while I was adding port 22 to the iptables I removed the outbound reject rules. Added some DNS name servers to the hosts file. Renamed the hostname to 3D-Printer from Master. Since the printer can now speak to the outside world, I updated yum. And am now in the middle of upgrading the packages from a yum check-update. I think I will either pick up a pata SSD for it. Or possibly a pata/sata adapter and put a more readily available sata ssd in it just because I don’t like old Seagate drives.

  33. Oops. Don’t upgrade the kernel to 2.6.26.8-57.fc8. The mariner modules were not compatible. Grub back to the old one.

  34. I’m guessing they skipped using the CF card to make sure that their main drive image was backwards compatible with older hardware (the system software has been very picky about being run from /dev/hdc, for example).

  35. Just for fun. I think I might up the memory in this thing from the 128 to 512 and DD the drive to a CF card. I wonder if I could order something from Advantech with a newer pc on card that would work with this thing. Probably a waste of time. But I just want to mess with it.

  36. I have a Dimension 768 BST and the hard rive is corrupt, completely lost partition 1, if anyone can get me an ISO, discs or clone a drive for me I would be willing to pay for it. I need my machine!!
    thanks!

  37. Matt, I think the drive image may be tied to whatever firmware your mainboard is using, so it may not be a simple re-image job. Also, I’ll mention it in a future blog post, but there’s apparently a new forum for Stratasys users that you might want to ask on: stratasysusers.org

  38. thank you
    i have the service manual and went through the trouble shooting. i have squares across all the lcds.

  39. I have “Dimension sst1200es” 3D printer. After the voltage source reset suddenly the printer givinig me message “Starting up. Finding home” to lcd display. What should I do? Can anybody help me?

    Running POST
    Internal Flash CRC Test [PASS]
    SDRAM Addr Test [PASS]
    ISA DPM Addr Test [PASS]
    Pmd DPM Data Test [PASS]
    External Flash CRC Test [PASS]
    NVRAM check [PASS]
    Supply Voltages
    5V supply: 5.04V Range: 4.85 to 5.15 [PASS]
    12V supply: 11.98V Range: 11.28 to 12.72 [PASS]
    15V supply: 15.88V Range: 13.50 to 16.50 [PASS]
    -15V supply: -15.82V Range: -13.50 to -16.50 [PASS]
    10V supply: 10.00V Range: 9.84 to 10.16 [PASS]
    3.3V supply: 3.28V Range: 3.23 to 3.37 [PASS]
    Navigator checksum: 0x12345678
    Navigator version: 0x28400F23
    Pilot checksum: 0x12345678
    Pilot version: 0x34100F22
    Pmd DAC Tests
    XSin@0.00V: 0.01V Range: -0.06 to 0.06 [PASS]
    XSin@2.15V: 2.25V Range: 1.96 to 2.34 [PASS]
    XSin@4.30V: 4.49V Range: 3.98 to 4.62 [PASS]
    YSin@0.00V: 0.01V Range: -0.06 to 0.06 [PASS]
    YSin@2.15V: 2.25V Range: 1.96 to 2.34 [PASS]
    YSin@4.30V: 4.48V Range: 3.98 to 4.62 [PASS]
    ZSin@0.00V: 0.01V Range: -0.06 to 0.06 [PASS]
    ZSin@2.15V: 2.25V Range: 1.96 to 2.34 [PASS]
    ZSin@4.30V: 4.49V Range: 3.98 to 4.62 [PASS]
    Controller board EEPROM CRC Test [PASS]
    Controller Configuration ID: 0
    Controller part number: 205627-0002
    Controller serial number: 0945-000285
    Power Dist board EEPROM CRC Test [PASS]
    PDB Configuration ID: 0
    PDB part number: 202569-0006
    PDB serial number: 0948-002057
    CPLD version: 33
    ColdFire version: 0 rev: 0
    Mariner build: 1924.0
    Cause of last reset: Software Reset
    POST successful
    last act:718768 / req:660187 / malloc:849/0 / stk:3240/8792
    act:699104/690720 / req:640523/638280 / malloc:760/0 / stk:2724/8792

    ————————————————————–SS——————————————————————————————–

    NMIStatus: 0x0
    Flags: 0xc8 : Initialized : MhmReady : ShmReady
    PwrControl: 0xd : DC : HeadHeater
    Cartridge: 0x3fc3 : ModPresent : SupPresent : ModLoaded : SupLoaded
    : ModLatched : SupLatched : ModMatInHead : SupMatInHead
    : ReplaceFailed : LoadFailed
    XYAxis: 0x0
    ZAxis: 0x0
    Status: 0x2000
    command flag = 0
    curve count = -1
    modHead = 184 / 0
    supHead = 186 / 0
    Temps = 89.40/0.00 / 89.40/0.00 / 28.60/0.00
    Current Position = 0.00,0.00,0.00
    Gantry: GR5K Stage: SR64K
    current material: model model fc: 0 support fc: 0
    Version: 1924 PLDVersion: 33 Gender: sst1200es

    ———————————————————————FZ———————————————————————————————-
    01/14/14 05:17:24:989: FindZHome.cpp:262:INFO:XY axis not ready:Find Z before Fi
    nd Home.

    maxts1990@gmail.com

Leave a Reply

Your email address will not be published. Required fields are marked *