So ... 3d Printers....

Main > Everything Else

<< < (13/284) > >>

Howard_Casto:
Ok more stuff.

I tried a different slicer, it didn't help, so I think that rules that out. I haven't been able to do anything via a usb connection. Cura will connect if I force the port number and the printer will reset, but then cura hangs. I've had similar issues with other software.

Skynet includes the stock firmware for A8, but I'm afraid to install it. I used it in avrdude with the verify option (surprisingly avr dude can connect?) and it comes back saying some of the bytes don't match. I checked what is supposedly an updated version and it doesn't match either (shows the exact same byte differences). I'm just scared that I'll brick the thing because there are multiple driver boards and I'm not 100% sure which one I have.

SammyWI:
I found this link for original firmware in one of the Facebook groups. No idea if they are correct.

http://anet3d.en.made-in-china.com/custom-detail/xmQExQndGJUQxmQExQndGJUQ/The-Firmware-Links-You-May-Need.html

Also Skynet does not have to use autolevel. You would just ignore setting up any z offset for the sensor, set z height manually and don't use the gcode for autolevel in your slicer.

Howard_Casto:
Yeah I've got a set of those as well. What worries me is the fact that I can't get the bytes to match via verify with any version of the firmware. I *think* I dumped the firmware to a hex file for backup, but if there is any kind of strange bootloader or funny business going on it could corrupt the dump. I've seen tutorials on how to use an uno to write directly to the serial port in case of issues after a bricked unit, but I would like to avoid that.

Did you flash yours with avrdude or arduino's toolkit?

SammyWI:
I flashed using what was included with Skynet, arduino I think.

What are you comparing to match bytes? Just a non programmer guess but if you are comparing the fw that came on your board wouldn't you expect the bytes to be wrong if that fw was corrupt from the factory?

Howard_Casto:
Well yeah that's true, but what concerns me is that it finds errors so early on... like in the first 30 bytes or so... that could be the boot loader. I opened them up in a hex editor and they look nothing alike. Mind you they are compiled, so a different revision would change things drastically.

I mean at this point it isn't working and I've heard very few complaints about Skynet, so I'll probably take a chance and update it tonight, I just don't want to have a gigantic project of getting things re-flashed if it doesn't work or the boot loader is corrupted, ect.

Oh and this morning just to make sure it wasn't a mechanical issue I used the position commands within the printer and the movement is dead on, down to the millimeter, so that rules one more thing out. It's really odd, it's almost like it can't read the g-code properly, because everything else seems to work ok.

Navigation

 Message Index

Go to full version