Possibly Bricked Qidi Tech printer when installing sailfish?

RCONSTRUCT · 2016-03-09T15:44:33.000Z

Thanks for coming back and updating. I had contacted Qidi Tech and they mentioned that I had Sailfish already installed. However, there may have been some miscommunication. I bought my printer from Amazon and I notice when I boot up my Qidi Tech 1 that the screen says Creator 1.0. Is that simply an error or is it really Creator 1.0? I may go your route or buy a new Mobo if that is the case.

Ryuluce · 2016-03-09T15:56:34.000Z

I had heard in the past that the older version carry the creator firmware, and I assume that is what you have. I have noticed while using sailfish there are several interface options that are quite different. So if your main menu has more than three options, and the options menu has no options regarding the EEPROM, then I think your printer has the creator firmware.

I don’t see why you’d need a new motherboard, buying an AVR programmer is much cheaper (at least, the sparkfun programmer is only $15).

BUT, before even that, I do think I screwed up the process of uploading the firmware by trying sailfish 7.6 in regular replicatorG first (by mistake). I do have a link in the original post to the thread where I first got my instructions to upload sailfish. I am not sure if following those instructions perfectly will work, though.

If you want to upgrade to sailfish, I’d recommend first having an AVR programmer handy. Just so if the firmware won’t take, you can flash the chip manually. Go ahead and try the steps in the tread (I don’t think you’d brick the printer, I didn’t, even with how poorly I think my attempt went), but be prepared if it doesn’t work. If the firmware doesn’t take, just open up the bottom of the printer and flash it manually.

Note: I think the early versions of the QIDI have some unusual settings for the fuses in the ATMEGA1280, so I have heard you cannot flash beyond Sailfish 7.2. That’s what I have on the printer right now, though I didn’t try anything more recent.

And as a testament to sailfish: I think since I started using sailfish the printer has just been functioning so much better. One thing is that the acceleration settings seem to have made the printer move so much more smoothly.

RCONSTRUCT · 2016-03-10T20:35:14.000Z

So I spoke with the representative from QidiTech. They only have ever had Sailfish firmware in their machines. The Creator 1.0 on the screen is just the model name. Here is the response from the rep:

Friend ,

no , the creator 1.0 it is means the model of the printer , it is 7.2 version motherboard you use now . because our company only have these two version . pls trust me ! and you no need to upgrade , it is more stable . i think you can get a good printing from it .

Best regards
Emily

And

Let me explain it .
We have two verison of the board , one is the stable version of 7.2 , another one is the testing version of 7.8 version .
When you order our printer , the 7.8 version is still in the testing .
We hope our customer can get a good printing , so we choose the 7.2 version to you .
In fact , these two version are the same , the only different the 7.8 version can show our company"s name .
So , really dont worry about this , 7.2 is more stable !

Ryuluce · 2016-03-10T22:10:01.000Z

Well, all I can say for certain is that the firmware on my printer was definitively NOT sailfish 7.2 (or newer).

When I flashed the official Sailfish firmware version 7.2 r895, the menus and options provided were vastly different. I am positive also that the printer was shaking more during sudden movements before I flashed as well.

I am also positive that Sailfish versions 7.2 and 7.6/7.7 are vastly different (there’s not even such a thing as Sailfish 7.8). You can check the update notes from the Sailfish people here: http://jettyfirmware.yolasite.com/v74-v44.php .

I think the rep from QIDI was talking about some kind of proprietary firmware THEY have, not the official Sailfish builds.

mcfly777 · 2016-03-31T19:48:29.000Z

I have the newest version of the printer, with the 2560 chip and Sailfish “7.8” installed. I am using it with Octoprint but there are problems in that the communication does not work well. I’d like to use the stable version of Sailfish (7.7). I can’t find 7.7 on RepG. So what is the procedure to install the new firmware?

mcfly777 · 2016-04-01T19:36:42.000Z

Thanks so much for this detailed walk through.Is there a way to back up my current firmware? Qidi has this custom firmware that I can’t download from the web.

thanks

Ryuluce · 2016-04-01T23:58:14.000Z

Yes, actually!

Now, I’m not sure whether or not this will work using the USB method, but if you get an AVR programmer this should definitely work.

AVRDUDE has the ability to read the flash, the eeprom, and the fuses of an AVR chip.

The firmware is stored in flash memory, so you can use AVRDUDE to export the flash memory into a .hex file. I haven’t done this myself, though, so you’ll have to find out the specific command line yourself.

Though I think the Qidi firmware is a derivative of the makerbot firmware, so it may not be fully necessary; but I guess better safe than sorry!

Ryuluce · 2016-04-02T00:00:05.000Z

Okay, so there are two ways to go about this.

But first, a note: do not use RepG to upload the firmware, it’ll be better to use one of the following methods.

The first step for both ways requires you to download the firmware’s .hex file.

Here’s the file for the atmega2560 mightyboard’s firmware version 7.7: http://jettyfirmware.yolasite.com/resources/release/firmware/mighty\_one-2560-Sailfish-v7.7.0-r1432.hex

You can also search this xml file to find direct download links to all the sailfish firmwares: http://jettyfirmware.yolasite.com/resources/release/firmware.xml (just replace the “firmware.xml” in the url with whatever is in the “relpath” section of the xml for the firmware you want)

By the way, I’d suggest unplugging the heating bed before continuing, it’s probably safer if you do.

Anyways, here are your two options: USB or ICSP. I can only attest to ICSP being more reliable, though.

To upload over USB, you’ll hook up the printer over USB and use AVRDUDE to flash whatever com port the printer is on. Make sure the programmer option is STK500v2. Also you may need to hit the reset button in the back of the printer when you start AVRDUDE in Command Prompt. I’m not sure on that front because I had screwed up my ability to perform the this method so I needed to use second one.

To upload via ICSP, you’ll need an AVR programmer that can flash a memory size of up to 256 Kb. The atmel avrisp mkII should work: Amazon.com

You need to open up the bottom of the printer and attach the programmer to the ISP port for the atmega2560 chip. You then flash the memory using AVRDUDE again. Also make sure AVRDUDE is using the correct programmer setting (it should be avrisp2 or something like that). (You can try atmel studio too, but I haven’t tried it so I can’t say how well it works).

If you try over USB first and it doesn’t work and the printer stops working all together (I don’t mean that it won’t turn on, I mean that it ends up with a blank LCD screen), then you’ll need to use the ICSP option to fix the printer.

You can also try and find a cheaper AVR programmer, just make sure it can support a flash size of up to 256 kb!

FINAL NOTE: If you didn’t understand any part of what I said, then do not try to do anything without performing significant research first. If you jump into this without enough understanding, you risk bricking your printer.

RCONSTRUCT · 2016-06-11T15:36:21.000Z

Where do you get AVRDUDE?

RCONSTRUCT · 2016-06-11T18:02:53.000Z

Could you link the tools I need to do this?

RCONSTRUCT · 2016-06-14T20:11:29.000Z

Hi again Ryuluce. I have accidentally screwed up my printer by trying to reset the board after having a stepper motor failure. I now have the AVR programmer but am unsure on how to use it. Do you happen to know the orientation of the pins on the motherboard? I’d hate to put power to ground.

Ryuluce · 2016-06-14T21:45:46.000Z

Okay, so you’ll notice that the ICSP pins for the ATMEGA1280 have a white dot near one corner, right? That white dot represents the upper-right of the standard ICSP pin configuration.

You’ll also notice that the programmer plug has a notch on one of the long sides, that represents the top of the ICSP pin configuration.

So, the notch on the programmer plug should be on the same long side as the white dot.

In other words, the white dot points out pin one.

RCONSTRUCT · 2016-06-14T22:12:31.000Z

Unfortunately I don’t have either of those. I have uploaded a photo.

Do you k now where I can get AVR studio 4?

IMG_4859[1].JPG3024×3024 1.53 MB

RCONSTRUCT · 2016-06-14T22:48:36.000Z

Okay, I have AVR studio 4 but am failing to connect.

Ryuluce · 2016-06-14T23:32:25.000Z

The programmer appears plugged in correctly to me.

As for the AVR studio 4, I’m afraid you’re on your own on that front. I’ve used only AVRDUDE and ATMEL Studio.

Ryuluce · 2016-06-14T23:32:55.000Z

I can’t help on that front, I’ve never worked with AVR Studio.

RCONSTRUCT · 2016-06-15T00:02:43.000Z

Ah no problem. I’m going to use AVRDUDE. I have some help from another person who went through it and gave me the hex files. I guess what I need to know now is how to use AVRDUDE such as making sure the connector I bought even works. I’ll come back and update.

RCONSTRUCT · 2016-06-23T00:44:30.000Z

Hi there and thanks again for replying. I have an programmer now and am familiar with avrdude. Do you have the commands I need to flash to the motherboard in order to get this working?

Right now I’m using:

avrdude -p m1280 -F -P usb -c usbasp -U flash:w:/Makerbot-usbserial.hex \ -U lfuse:w:0xFF:m -U hfuse:w:0xDA:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

and

avrdude -p m1280 -F -P usb -c usbasp -U flash:w:/atmega1280.hex \ -U lfuse:w:0xFF:m -U hfuse:w:0xDA:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

to the 8u2 ICSP port but to no avail. Avrdude says it completed but had a verification error. Also I see no com6 in repG

Ryuluce · 2016-06-23T01:01:32.000Z

Okay, to make troubleshooting easier, could you try again with a verbose output and funnel the command’s output to a text document?

To do that, use this command:

avrdude -v -v -v -p m1280 -F -P usb -c usbasp -U flash:w:/Makerbot-usbserial.hex \ -U lfuse:w:0xFF:m -U hfuse:w:0xDA:m -U efuse:w:0xF4:m -U lock:w:0x0F:m > Troubleshoot.txt

That should output all the command’s response into a .txt file that can be used for troubleshooting.

RCONSTRUCT · 2016-06-23T03:06:15.000Z

Will do. Just so I’m clear. I was flashing the atmega1280.hex to the 1280 header and the usbserial.hex to the 8u2 ICSP. Is this correct?