Formbot Troodon RRF 3.1.1 Update

Robthide37

@Veti You did not read the thread i assume lol

Veti

@Robthide37
not the klipper part.

would it be possible to cut the pin on the driver?

nomukaiki

Has anyone tested the Troodon with the latest release v3.2 ?

Guzzi

Just tried the PRF 3.3RC3 with the same result! No changes so far! motor phase A may be disconnected_release_3.3RC3.jpg

koreandi

Good morning together..

I just got a Vivedino Trodoon 400.
It ran with Duet 2.x and I wanted to upgrade it to an actual Duet Firmware.

However.. After upgrading to 3.0 all seemed to work fine.
After upgrading to 3.3 I got the same issues as reported by Guzzi.

I should have read this topic before upgrading my system.

I am not able to downgrade the Firmware to earlier FW releases.
After uploading the Firmware the machine refuses to upgrade with error, something like that:

M997 In-application programming binary Duet2_SDiap32_WiFiEth.bin not found

Even if I manual put this file in to System it does not work.

Any tipps or workflows how to downgrade back to 3.0?
I have read different topics but it was too much input last night and I had to got to bed...

greetings
Andreas

PCR

@koreandi was already fixed. Try updating to 3.4B6

All hail to @oliof who bought a formbot board only to solve the issue.

koreandi

@PCR
Sounds great. I didn´t considered any beta realeses till now.
I will try that in the afternoon and will report about it.

Thanks a lot.

koreandi

@pcr
Hmm. I still don´t manage to get any other version installed.
Still the same message:

Error: M997: In-application programming binary "0:/firmware/Duet2_SDiap32_WiFiEth.bin" not found

koreandi

@koreandi
Okay.. I rerolled 3.3 and afterwards 3.4B6 worked...
I will test the functions.

Thanks a lot.

nomukaiki

With the RRF 3.4 these problems seem to have gone.
Can this thread be marked as resolved to help anyone that is searching the forum?

patate1684

@nomukaiki I got a formbot Troodon and I am looking to updating the firmware. After reading this entire thread, from what I understand, i can safely update to RRF 3.4 and everything should work as intended. (With the appropriate changes to the config file of course). Am I correct ?

jay_s_uk

@patate1684 that appears to be the long and short of it, yes

TheBasedDoge

I updated my Troodon to Release 3.4.1 RC1 and it works but i have two issues

When the printer first starts up, it says the motor phase error, but if i click ok it just seems to work.
The screen won't connect anymore, it just says "connecting.." forever.

any ideas?

oliof

@thebaseddoge the motor phase error in the beginning is due to the missing drivers in the board design. If they only happen during startup you have nothing to worry about.

For the display you may need to add an explicit M575 P0 B57600 at the end of config.g -- this wasn't required in earlier releases of RRF, but is required for the current ones.

TheBasedDoge

@oliof said in Formbot Troodon RRF 3.1.1 Update:

l

thanks, unfortunately no go on on adding the M575 P0 B57600
It still says connecting. I confirmed the baudrate on the screen is set correctly.

also is there any way to surpresss the motor warning?

oliof

@thebaseddoge the motor warning should go away if you disable them in config.g. But they may pop up at start before config.g is fully parsed.

Phaedrux

@thebaseddoge said in Formbot Troodon RRF 3.1.1 Update:

M575 P0 B57600

Please try M575 P1 B57600 S1

You may also want to update your PanelDue firmware to 3.4 as well if you haven't already.

TheBasedDoge

@phaedrux

Thanks I will try it and report back. unfortunately I now have to wait for a 10 hour print to finish to try it lol. I'll check the paneldue firmware too.

TheBasedDoge

@phaedrux said in Formbot Troodon RRF 3.1.1 Update:

M575 P1 B57600 S1

Thanks, this worked. I think it's all working now. I noticed the fans are running louder than before so that's next to figure out.

nomukaiki

@TheBasedDoge sorry to open this old topic, but only now I've upgraded my Troodon to 3.4.4.
I'm also noticing that the fan to cool off the MCU is now constantly on at high speed, when on 3.0.0 it was controlled by temperature.
Did you managed to fix yours?
Thanks