Formbot Troodon RRF 3.1.1 Update
-
Also worth noting the 3 drivers listing error states (2,4, and 9) do not physically exist on this board.
Thanks
-
well they have a few errors for a RRF3 config, but nothing that I can see would cause issues...
M574 Z0 P"nil" ; no Z endstop switch, free up Z endstop input
You can remove that line to stop the M574 type 0 not supported errorM307 H3 A-1 C-1 D-1 ; set PID tuned settings for heater 0
You can remove that line to stop the heater 3 not found errorM140H0There should be a space between M140 and H0; --- Set or report heating process parameters--- M106 P3 I-1 M106 P4 I-1 M106 P5 I-1 M106 P6 I-1 M106 P7 I-1 M106 P8 I-1I'm not sure what their intention is for this block, but inverting the pin is done with M950 in RRF3. I'd just remove those lines. that's the fan not found errors.
M569 P2 R-1 M569 P4 R-1 M569 P9 R-1These lines should function to stop monitoring those missing drivers you mention, but they don't seem to be working in 3.1.1. I'm not sure what has changed.
Can you try sending them again in the console?
What do you get if you send M569 by itself? -
Those do function to stop the flood of warnings that were present before adding them. The command goes green in the terminal after sending on DWC with no error reported. No change in M122 output.
If my memory is correct, the M574 command was included in the 3.0 documentation on setting up the BLTouch to release the z endstop pin. Is there another line required to do the same thing with 3.1.1 or is it unassigned by default?
-
@InsanityAutomation said in Formbot Troodon RRF 3.1.1 Update:
is it unassigned by default?
Exactly. In order to be more generic there are no more assumed assignments. Instead you use M950 to define the pins you are using. In your case for the BLTouch that would be
M950 S0 C"duex.pwm5"Sorry for M569 you'll need to specify the driver number as well so try sending M569 P2
-
M569 P2
Drive 2 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 127 -
Seems akismet wants to flag it as spam for some reason... lol Im adding a bit more content above it to try and get rid of that warning....
M569 P0 Drive 0 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 0 M569 P1 Drive 1 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 0 M569 P2 Drive 2 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 63 M569 P3 Drive 3 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 0 M569 P4 Drive 4 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 63 M569 P5 Drive 5 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 0 M569 P6 Drive 6 runs in reverse, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 0 M569 P7 Drive 7 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 0 M569 P8 Drive 8 runs in reverse, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 0 M569 P9 Drive 9 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x101b4, toff 4, tblank 2, hstart/hend/hdec 3/3/0, pos 63 -
so are you still getting the errors when trying to move the axis after you've sent:
M569 P2 R-1 M569 P4 R-1 M569 P9 R-1 -
@Phaedrux said in Formbot Troodon RRF 3.1.1 Update:
M569 P4 R-1
Yup, no change in function or output sending those manually.
-
Alright. I'm not sure what changed between 3.0 and 3.1.1 that would explain this. You'll have to hold tight until @dc42 has a chance to take a look. It is likely related in some way to the odd combo board being used.
-
Id assume so as well. When I showed Tony the board at ERRF last year he was glad to see something not a direct clone for a change but here is the risk of it not being a direct clone lol
-
Yes it's definitely an interesting beast. Do you have any other info on it? I wasn't able to get much from googling.
-
I can grab some photos of it when I get home (Remote VPN for last testing bits!) Personally I really like the removable drivers despite the thermal constraints as they are still one of the most failure prone components on these boards. People who (ab)use machines like I do tend to go through a few of em....
-
Heres a few photos : https://photos.app.goo.gl/N7Ea1rB1NPq9jCTEA
-
Figured I'd bump this and see if anyone had any other idea before i dig into source myself.
-
@InsanityAutomation It appears newer machines are shipping with a slightly different board:
https://m.facebook.com/photo.php?fbid=2806644909555472&id=100006299702277&set=gm.949439705562814&source=57 -
I have exactely the same issue on my Troodon, but I'm using a different (self made) config.g file. So i'm back on 3.0 for now. And I do have a newer board which is black.
-
@Guzzi Does Troodon give any firmware guidance with regards to the custom board?
-
From what I can tell, the stock firmware for the Troodon isn't even available for download anywhere. The firmware for their other machines is provided via zip files hosted on a variety of file hosts (some on drop box, some on google drive, etc).
Also, Vivedino/Formbot appears to be a very small company. It looks like their entire lineup aside from the Troodon uses the same marlin motherboard.
All of this combined makes me think that perhaps a 3rd party designs boards for them. If that's the case then they may not even have someone who could provide help with firmware.
-
@Phaedrux no they only provide the firmware which the machine is shipped with. So 2.03RC3. I asked them if they already have a config for 3.0. They told me that if I wan't to upgrade I have to write my own. So that's what I did but unfortunately had the fault issue on 3.1.1.
-
@Guzzi Hi. Could you please share you configuration files for the 3.0?
