No Connection to DCS After Update to 3.2beta4

Veti

@Frederik

yes if the firmware is erased, the diag led should be on constant

Veti

some people have had to use up to 18 different cable until they found one that worked.

Frederik

@Veti you are joking, right ?!? 18 Cables....holy...i cant find what the meaning of the static diage led is ?

Veti

see
https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond

If the firmware has been erased the DIAG LED will be on permanently.

Frederik

@Veti Thank You SOooooooOO much for your tip with the usb cable....i tried a 10 year old usb2 dvd cable (with dual A Plugs on one side). After connecting the second the firmware flashed perfektly on the first try ;).

I would be so lost without you guys and this forum

Have a nice Day !

Frederik

@Frederikfor information purposes:

The cable that did NOT work: brand new Ugreen with 3Meters in lenght.

The cable THAT worked: 10 Year old usb2.0 with dual USB-A Plug on one side.
Like the on the external dvd or harddrives. Lenght ~ 40cm

Frederik

So, the cable worked. The firmware flash over bossa worked. Also verifying. I did 2 times exact what's mentioned in the getti g startet wiki. I loaded the additional files, flashed a new copy of duet pi desktop on the 16gb card. After that I copied my .g files in the /sys folder on the boot partition together with the 3.1.1 firmware .bin.

After that, I Did all the steps like network, keyboard layout etc. Without any errors.

Even the update at the end + restart showed no errors. Only in the dcs log is constantly starting and stoping with the meassage:

No connection to duet3

Should I do a standalone firmware reset and after that reconnecting the pi?

It seems that the reset button did not reset the board, even if I hold it like 10 seconds

Frederik

I do all the actual test without Vin.
Only connection over usb and wlan

Phaedrux

@Frederik said in No Connection to DCS After Update to 3.2beta4:

Should I do a standalone firmware reset and after that reconnecting the pi?

Yes I would set it up in standalone to confirm that the Duet is working correctly otherwise and see what firmware version is flashed.

Frederik

@Phaedrux Thanks. I will test that later.

chrishamm

@Frederik You did not mention that you changed the package feed from stable to unstable which is a required step if you want to use DSF 3.2-b4 as well. If you don't do that, you'll get the error message you mentioned.

See here for further information.

Frederik

@chrishammyes, i have the unstable all the time.

After i changed to the standalone mode, made the specific sd card + filestrukture, the board accepted the firmware and the diag led is now out . after that i startet a complete new installation with the pi.

this time everything works fine..

The new Visualizer is amazing
Tomorrow i will install and test the new DuetLapse .

But that way did not work at first with the sbc attached.

Thanks for all your help

Regards
Frederik