@dc42 it was a direct copy from what was on the virtual SD card on the Pi, when I flipped to standalone mode. Config + firmwares, etc. I just grabbed all of that + the duet web control zip from GIT.
The virtual SD card files were automatically pulled down via APT, also.
It's working 100% normally now.
@Phaedrux said in Toolboard firmware issues:
If it's still not functional in standalone we'll look into warranty replacement.
Standalone success! I don't know what was different vs. the last time I tried it, but I dropped the SD card back in for standalone mode, and fired the printer up, it pulled down firmware and all appears to be good.
I hate errors where I can't identify a clear root cause, but I'll take a success on this one.
Thanks for the advice all, hopefully this thing behaves itself from here on out.
I'll try standalone mode tomorrow and see if I can get it to wake up. I played with that a fair bit already, but I'm happy to give it another shot.
I can't get any information on the expansion board, it doesn't respond in any to CAN. I have a ton of CAN tooling, I guess I can sniff the bus and see what's happening at a lower level if need be. I've done a bunch of hacking and software for automotive CAN systems (and build race-spec wiring harness for cars) so I'm more versed than average on CAN.
I'll jack up the logging level as well. Thanks for the advice!
Anybody else have any ideas? Currently I've got a large format CoreXY brick.
I reached out to Matterhackers (who I bought the board from) but I haven't heard back from them in about a week either. There doesn't appear to be an alternate recovery solution for the board that I can find thus far. I'd just buy another board and chalk this up to bad luck, but I don't want to do this again.
Maybe I'd be better of with some BTT stuff and Klipper where I can force recovery properly?
Another 3.4.5 (MB6HC, SBC) with Toolboard 1LC 1.3. Toolboard is gone after firmware update to 3.4.5.
I've done lots of poking at it (initially it was a 2 blink, no firmware) now it's a 3 blink (bad CRC). I forced downgrade to 3.4.4, etc. No dice.
I have a thread on the Firmware board about it also:
https://forum.duet3d.com/topic/30641/toolboard-firmware-issues/
Thanks Jay, I ran the script and it downgraded to 3.4.4 successfully.
I've noticed that on startup, I see "Error: Firmware file Duet3Firmware_TOOL1LC.bin not found" on my PanelDue. This corresponds (logically) to the "2 flash" then "5 flash" on the toolboard. This only happens until "Connection to SBC established!" message on the PanelDue, at which point it does a green "blip" then stops totally. I did double check the /firmware directory and it does have the "Duet3Firmware_TOOL1LC.bin" file, along with a "Duet3Bootloader_TOOL.bin" as well.
Unfortunately that's all it does. I've tried a reset on the toolboard again (2 button, power reset) on version 3.4.4 but no difference.
Error: M122: Response timeout: CAN addr 121, req type 6024, RID=8
Consistent across all of the CAN addresses I've seen discussed as well (10, 20, 121, etc).
To add some more info. The 2 lights/5 lights happens a few times on startup, then I get a flicker of the green light, then no more lights (other than the red/blue status lights).
Good day all,
I picked up a v1.3 Toolboard (via Matterhackers, delivered last week). Installed it today and it initially came up and was identified via M122 B121 as normal. I'm on an MB6HC with an SBC so I did my normal "apt update" and it attempted to install the current firmware (3.4.5) on the MB6HC and the Toolboard. Unfortunately it seems to have hung on the toolboard install and after >90 minutes, nothing occurred (hung on install).
I reset both boards, and the MB6HC works fine, but the toolboard appears to be out to lunch. I did a reset (power on with both buttons pressed) and it gives me the 2 red lights (bad firmware) and then 5 if CAN is hooked up (4 if I do this with CAN disconnected) so it appears it knows it's broken, but it can't seem to recover.
All of the requisite files are in my /firmware folder, so I'm not sure what else to do here. Any ideas? I tried asking it nicely, and giving it dirty looks, all to no avail.
Regards,
Blake