How did the firmware update evaporate from my board?

NOVAprint

@dc42 Ok so, I loaded the wrong version of the software onto the at91sam4s8-ek. I used the duet maestro firmware and it works the firmware did not evaporate, but it really did give me a hell of a time I suspect that I tried to load teh combined firmware in the inital problem that presented as well. Lost three days because I read someowhere that it was recommneded that the combined be used, but if you have a Maestro, use the maestro bin, not anything else, until something changes.

NOVAprint

Now my motors are making more noise, is there a simple way to address that? more noise after the new firmware which of course should not be happening any ideas?

Phaedrux

At least this should be a one time operation. Now that you're up and running the firmware update for 2.02+ consists of uploading a single zip file to the settings>general page on the DWC.

patakopecek

@novaprint you propably had stealthchop on, so just turn it on again

NOVAprint

@patakopecek I think that you may be right, how do I put stealth chop on again? I think that I went to this:
M569 P0 S1 D3 F1 ; Drive 0 goes forwards,
M569 P1 S1 D3 F1 ; Drive 1 goes forwards,
M569 P2 S1 D3 F1 ; Drive 2 goes forwards,

I think that the D3 now represents stealth chop, unless there is some other thing that i am missing.

NOVAprint

So I was making some physical adjustments to my unit nothing terribly alarming, I generated a little bit of shavings from my drill, who hasn't? Anyhow I went to print something, loaded the file (first time after all this) the heat bed is not heating, the hot end is so I hit emergency disconnect and that is the last I talked to my board. Now the board will not connect to anything again.
Resolved to install the firmware again and the erase function will not work, BOSSA nor SAMBA will connect. Hold the erase button for a fifteen seconds no indication that the board has been made discoverable, Pronterface will not connect, nor will DWC. FML

The board stayed in the enclosure the whole time I was working on it, there was no extraordinary movement or issues when I was doing any of this, no wiring work no holes in the board.

NOVAprint

reset led will not light even with erase jumpered.

NOVAprint

@novaprint The heat bed worked before BTW I am not sure why the temp was not going up. Does it sound like I burned the board with shavings from my drill?

NOVAprint

@novaprint I tried another USB coard and it I still cannot connect with the board.

NOVAprint

I disconnected everything from the board and tried the rest function. No reaction.

dc42

Unless the board is faulty, the only reasons we know of that the firmware gets erased are if you use the Erase button or jumper, or send M999 P"ERASE" to it, or the board is subjected to some type of mis-wiring that causes a transient to be fed into the +5V or +3.3v rail.

After using the Erase jumper, you need to remove it and then press the Reset button before the board is discoverable.

I suggest you check again that the correct LEDs (and no others) are illuminated.

NOVAprint

Going from left to right I have a red light, a green light a red light beside the USB, and another red light on the other side of the USD. With power attached, (left to right) I have a blue, red, green gred, usb and red.

dc42

@novaprint said in How did the firmware update evaporate from my board?:

Going from left to right I have a red light, a green light a red light beside the USB, and another red light on the other side of the USD. With power attached, (left to right) I have a blue, red, green gred, usb and red.

That sounds correct. The LED to the left of the USB socket should light if USB power is present, and not otherwise. The one on the right is the DIAG LED; it will be on if the Duet is not programmed, and may be on or off when it is programmed depending on the Z probe configuration in config.g.

The heat bed worked before BTW I am not sure why the temp was not going up. Does it sound like I burned the board with shavings from my drill?

That's entirely possible, if the shavings caused a short between VIN or +5V and one of the lower voltage circuits.

Which country are you in? In the US there is a forum user who may be willing to diagnose your board and repair it if possible.

NOVAprint

@dc42 I am in the united stats in Virginia.
One other thing that has happened is my OTHER duet board, the one that decided to retire after printing for about three or four hours would not connect to DWC, unrelated to any wiring or firmware assertions. Anyhow, I was able to ping it back to life using a test from my router. The router pinged it and it was connectingto DWC again. That was great BUT then I went to heat up the bed, no issue I went to heat up the hot end no issues, I went to print something and my Z axis would not move. I have a delta printer so one leg, the Z is immobile. I cut off the unit, went to install another motor and the new motor which was installed sis not move either. I checked the vltage assignment in DWC and nothing has changed. The unit reads 12.4 volts which allowed for the unit to work reasonably well until about three or four days ago. Any ideas about that spontaneous failure of the output of a stepper driver?

NOVAprint

@novaprint I went to extrude and the whole thing went and shut down, I have changed nothing, not shorts not electrical changes the voltage is there. This is a real problem, a real problem. The exruder made a serious shake shimmy and I bet that I will not be able to talk to my OTHER duet powered unit again.

NOVAprint

The board actually communicates still I tested the motors that I tested with and the pairs work on the motors. The original z motor works as well (has continuity) offers resistance when the pairs are connected.

NOVAprint

@dc42 David,
I am not so sure that I shorted my board. it is possible but I do not honestly think that I did. Take a look at my following posts, the other printer that I have also started manifesting electrical issues after I tried to install the new firmware. The z motor will not move and moving the extruder causes a complete shut down. What do I need to do to go back to the prior firmware? Is it possible that I have a virus in my systems? None of this makes sense and I really need to be able to get this resolved, you have beena tremendous support, I seem to be up against something substantial.

NOVAprint

@dc42 Ok, the diag light on teh right is illuminated the diag is lit up. I canot ping the board from my router and the Samba is not working either, No speaking to the board at all. It did however speak before. Is there a way to "force feed" it? I will look at the routines and see if I see anything again.

NOVAprint

This post is deleted!