Firmware update failure..
-
@Phaedrux said in Firmware update failure..:
Normally I would suggest to replace the 4-wire cable with a new one, but you've already tried the ribbon cable option with the same result.
Which version of PanelDue is it? Which PanelDue firmware did you use to flash it? Perhaps there was a mismatch. It is a Paneldue 7i and I used 1.24 for 7i downloaded from your repository...
-
@Phaedrux said in Firmware update failure..:
@Helensdad said in Firmware update failure..:
after downloading the combined firmware.bin file, I tell it to update, it then drops the Wifi connection and reverts back to 1.0.3...
This part makes me think that the files might not be placed in the /sys folder or that there might be other files there or files not named correctly and so an older file is being used.
Can you provide a screenshot of the SD card directory structure?
-
Ok, so your screen shot of the /sys folder shows the bin file is actually a
._
file which is a metadata file used by MacOS and is normally hidden. So at some point there was a firmware bin file, but there isn't at the moment.I took a look at the workbee docs and I would try downloading the 1.0.7 full install zip, extracting it, and then trying to upload the combined firmware bin file to the /sys folder in DWC. It should detect it and update the firmware.
https://ooznest.co.uk/wp-content/uploads/2019/11/WorkBee-Firmware-v1.0.7.2-Full.zip
Maybe it helps, maybe not, but at least we can confirm that 1.0.7 installed correctly.
-
@Phaedrux I have just connected the Paneldue to my Maestro board and get the same problem, when I look at the card contents, Paneldue says files on card 0, nothing works except foe settings....
-
Alright, well that narrows it down to the PanelDue at least.
I would try updating the firmware on the PanelDue again. Redownload the correct file for the 7i and check the file size.
Hopefully it's just a case of a bad flash.
-
I have uprated the firmware again and tried on Duet 2 WiFi and Duet Maestro to no avail. I even used a brand new good quality USB lead. I bought it on May 24th last year so out of warranty. Do you know if it is repairable?
-
@Helensdad have a close look at the 4-wire cable. It’s possible there’s a poor contact, or wire pulled out of a crimp. If you have a multimeter, check resistance of each wire, should be less than 0.1ohm.
Ian
-
Resistance all below 0.1 Ohm, I get the same problem with the 10 way ribbon cable as well...
-
Just to clarify: the PanelDue screen lights up and shows all the buttons etc. but remains stuck at "Connecting" - yes?
-
Yes, that is correct, tried on 2 Duet boards, updated firmware twice, checked resistance of each conductor on 4 way cable and tried 10 way ribbon cable..
-
The usual causes of failure to connect:
- Using RRF 3.1 or later, and not having the correct M575 command in config.g.
- Mismatched baud rates. Check that both ends are set to 57600, in M575 on the Duet and on the Setup page of PanelDue.
- Faulty cable, either a bad crimp or Tx/Rx wires crossed. Check the that wire colours at the 2 ends of the 4-pin cable are reversed from one end to the other.
-
PS - it's occurred to me that I may not have tested connecting a PanelDue to a Maestro with recent firmware, because it's an unusual combination. So if you are using RRF 3.1.x then it could be a firmware issue.
-
@dc42 Well, I feel a bit daft now, changed baud rate to 5700 and all is well! If my Duet has incorrect baud rate set could that be the cause of my Firmware problem?
-
@Helensdad said in Firmware update failure..:
If my Duet has incorrect baud rate set could that be the cause of my Firmware problem?
What firmware problem is that? I suggest you start a new thread about that unless you already have.
-
@dc42 ok, apologies, I thought the two problems may have been interconnected as the paneldue went on the blink immidiately after the firmware update...interconnected
-
@Helensdad said in Firmware update failure..:
@dc42 Well, I feel a bit daft now, changed baud rate to 5700 and all is well! If my Duet has incorrect baud rate set could that be the cause of my Firmware problem?
If slowing down the baud rate that much has an improvement that might indicate an issue with cabling or interference. Either way, glad you got it sorted out.