Formbot Troodon RRF 3.1.1 Update

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

TheBasedDoge

Does anyone know how I can fix this? The printer works but on every bootup I still get this after updating to 3.4.4
Driver 9 error: over temperature shutdown, phase A short to ground, phase B short to ground

@nomukaiki

Sorry I only saw this now. here is my fan config
; --- fans ---
M950 F0 C"fan0" ; Fan 0 uses the Fan0 output
M950 F1 C"fan1" ; Fan 1 uses the Fan1 output
M950 F2 C"fan2" ; Fan 2 uses the Fan2 output
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off - PART COOLING FAN
M106 P1 S1 I0 F500 H1 T65 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on - HOTEND FAN
;M106 P2 S.35 I0 F500 H1 T100 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on - CASE FAN

; --- Case Fan ---
M950 P5 C"duex.fan7"
M42 P5 S0.0 ;

; --- Controller Fan ---
M950 P4 C"duex.fan8"
M42 P4 S0.5 ;

droftarts

@TheBasedDoge said:

Does anyone know how I can fix this? The printer works but on every bootup I still get this after updating to 3.4.4
Driver 9 error: over temperature shutdown, phase A short to ground, phase B short to ground

Looking at @oliof 's replies earlier, he said:

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.
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.

Add M569 P9 R-1 to your config.g to disable the driver. And don't worry about it.

Ian

TheBasedDoge

@droftarts

It looks like I already had that line in the config, so i guess i am just stuck with it. That's fine, will just ignore it.

dc42

@TheBasedDoge said in Formbot Troodon RRF 3.1.1 Update:

It looks like I already had that line in the config, so i guess i am just stuck with it.

I presume the error is only reported once. You could try moving that line earlier in config.g if it isn't already near the start.

TheBasedDoge

@dc42 It's only on bootup. I tried putting that line at the very beginning of the config, but no change. I guess config is not being loaded fast enough before it pops the error?