Vivedino Troodon 300 RRF 3.4 config

[nomukaiki]

I started my upgrade of the Troodon from RRF3.0 to 3.4, and I'm having some challenges with the config.g settings.
The firmware and web console loaded fine after following the recommended steps: 2.01 > 3.0 > 3.1.1 > 3.4

I had it running on 3.0 for a while with a set of config files that I managed to build months ago, but not so straighforward to convert them to 3.4.

Maybe someone already done all the configurations for 3.4, drivers, heaters, fans, leds, probe, etc, and can kindly share it?

Thanks
Joao

[nomukaiki]

I had nothing better to do, so I went ahead and manually fixed all the details of the /sys files to work with the default configuration of the Troodon 300.

Here is the gist of my config.g: https://gist.github.com/nomukaiki/31571fcbb0474f4bf1351e45d5c1bbcd
Please suggest any changes if you find anything not optimal.
And if anyone needs the other files as well do let me know.

bed.g
config.g
config.json
deployprobe.g
filaments.csv
heightmap.csv
homeall.g
homex.g
homey.g
homez.g
pause.g
resume.g
retractprobe.g
sleep.g
stop.g
tfree0.g
tpost0.g
tpre0.g

[oliof]

@nomukaiki great work! You could submit it to the https://github.com/Duet3D/RRF-machine-config-files repo -- see the README included.

[Fred-Y]

@nomukaiki Are the LED working?

If I remember (I might be wrong) when I upgraded my long time ago I had to change this part, the pin names are not the same.

; --- RGB leds - White ---
M42 P24 S255                                       ; R-
M42 P25 S255                                       ; G-
M42 P26 S255                                       ; B-
M42 P28 S195                                       ;

I have since a Duet 3 6HC and I cannot find my old config.

[Fred-Y]

Actually you can have a look at this config created by Insane Automation, it's not the last version of RRF3 but it should provide good insights.
https://github.com/InsanityAutomation/FormbotTroodon/blob/master/sys/config.g

Also, for your information, there is a fairly active FB group dedicated to the Troodon, the group came up with some good upgrades.

[nomukaiki]

@fred-y Thanks for looking.
I have fixed it directly on the printer and forgot to update the gist. Gist has now the LEDs working properly.

; --- RGB leds ---
M950 P4 C"duex.fan4"			   					; create pin 24 for Red
M950 P5 C"duex.fan5"			   					; create pin 25 for Green
M950 P6 C"duex.fan6"			   					; create pin 26 for Blue
; --- RGB leds - start with White ---
M42 P4 S255 					   					; G-
M42 P5 S255 					   					; R-
M42 P6 S255 					   					; B-

[nomukaiki]

@oliof thanks for the suggestion, I wasn't aware of that repository.
I have now submitted my files in a pull request.

[nomukaiki]

Config files are now available on https://github.com/Duet3D/RRF-machine-config-files/tree/master/Vivedino Troodon 300

I get a warning when the board restarts with the message:

Driver 9 error: over temperature shutdown, phase A short to ground, phase B short to ground

I didn't manage to fix this, and I doubt it is an hardware problem.
It doesn't seem to cause any issues when printing, but it is annoying to see.

Any improvements and suggestions are more than welcome. Thanks

[tak21]

@nomukaiki I do have the same error. The "driver 9" does not physically exist and is is disabled in the config. But somehow the web-ui is triggered to send an event every time a browser session is started. I have no other error anywere and the printer is running well. (I: I am not using your config but my own and have now to compare your settings with mine. Thank you so much for posting them!)

[nomukaiki]

@tak21 Thanks for looking. It would be great if you share any findings with improvements.
I didn't manage to get the filament sensor working yet. Also I didn't have time to fix all the Macros, if you have them and you can share that would be fantastic. Thanks

[oliof]

Are you disabling the stepper with M569 P9 R-1? if that doesn't disable the warning it's likely a bug.

I have a Troodon board which I bought to figure out what broke it with RRF 3.1 -- that's been fixed in 3.4. I can try a config to look into it if you have one to share that is current/up to date.

[nomukaiki]

@oliof said in Vivedino Troodon 300 RRF 3.4 config:

Are you disabling the stepper with M569 P9 R-1? if that doesn't disable the warning it's likely a bug.

I have a Troodon board which I bought to figure out what broke it with RRF 3.1 -- that's been fixed in 3.4. I can try a config to look into it if you have one to share that is current/up to date.

Yes, the driver 9 is disabled on the config.g with M569 P9 R-1 but it doesn't stop the warning.
https://github.com/Duet3D/RRF-machine-config-files/blob/master/Vivedino Troodon 300/sys/config.g#L33

[oliof]

@dc42 is there anything else that needs to be done to disable a missing stepper being monitored or is this a bug?

[tak21]

@nomukaiki Sure I can share my config + macros. My printer is running but I made some changes compared to your config. E.g. I slowed down movements (your config is really chasing the axes around !)
I need to figure out how I can upload everything to github as this will be my first time ever I use github to upload [...]

@oliof thanks to your suggestions/effort my printer is running! Honestly if I knew that they were not using the orig. board I would have not bought the printer. And I plan to upgrade to the 3 mini as soon as I have enough time. To the "error": there was a change in one of the betas, when it started to appear. Sorry, I do not know any more when it accured but I think it was beta4. And the "error" is on all disabled drivers, not only on 9 as I falsly reported (I had a more closer look into the messages on the printer on restart).

[dc42]

@oliof my guess is that the warning is generated before that M569 command to disable the driver is executed. Putting that command right at the start of config.g may help.

[tak21]

@dc42 FYI: in the beta firmware 3.4 Beta 5 this "error" did not display.

For your suggestion: if the three "M569" commands are in line 1-3 it works without any event beeing triggered! THX!!!

[nomukaiki]

@tak21 said in Vivedino Troodon 300 RRF 3.4 config:

@dc42 FYI: in the beta firmware 3.4 Beta 5 this "error" did not display.

For your suggestion: if the three "M569" commands are in line 1-3 it works without any event beeing triggered! THX!!!

I still get the error even with the disable commands are at the top of the config.
Interesting the error used to be with driver 9 but now it says driver 4.

M569 P2 R-1                                         ; physical drive 2 disabled
M569 P4 R-1                                         ; physical drive 4 disabled
M569 P9 R-1                                         ; physical drive 9 disabled 

This popup only shows up on the first load of the DWC, or refreshing the page. It doesn't show up after restarting the mainboard saving the config.g or sending M999

[oliof]

In another thread, @dc42 wrote

if you leave the motor currents set at zero in RRF then you won't get any warnings about motors being disconnected.

https://forum.duet3d.com/post/231465

Maybe try that in addition? I am not entirely sure how to do that cleanly since M906 works on axes, not on motors. You could add a virtual V axis, assign the motors, set the current, then hide the axis I guess?

[tak21]

Hi and just to be sure: I really did put them in line 1 to three, so not even a comment line above. If I used e.g. the standard comments before, the warning was there. And if the printer reboots, it complains about all three non exiting motors in the internal log. But just once and with no further noticeable disadvantage.