Solved Formbot Troodon RRF 3.1.1 Update
-
Interesting. I upgraded from 3.0-RC4 to 3.1.1 just the other day and (on a Duet3) board this worked just fine. So I guess this is one for the experts and not an innocent bystander (-:
-
So the config.g is the same, and only the firmware version is changing?
Can you send M98 Pconfig.g in the gcode console and see what errors if any are reported?
Can you also send M122 and report the result.
-
Thats correct, no changes other than bringing the firmware bin file back and forth.
With 3.0.0 Installed :
M98 Pconfig.gError: M574: endstop type 0 is no longer supported. Use type 1 and invert the input pin instead. HTTP is enabled on port 80 FTP is disabled TELNET is disabled Error: M307: Heater 3 not found Warning: M307: heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 542C. Error: M106: Fan number 3 not found Error: M106: Fan number 4 not found Error: M106: Fan number 5 not found Error: M106: Fan number 6 not found Error: M106: Fan number 7 not found Error: M106: Fan number 8 not foundM122
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DJM-9178L-L4MSJ-6J9FG-3S86S-982QP Used output buffers: 3 of 24 (10 max) === RTOS === Static ram: 30516 Dynamic ram: 92392 of which 60 recycled Exception stack ram used: 504 Never used ram: 7600 Tasks: NETWORK(ready,640) HEAT(blocked,1240) DUEX(suspended,160) MAIN(running,3676) IDLE(ready,156) Owned mutexes: === Platform === Last reset 45:02:35 ago, cause: software Last software reset at 2020-05-04 22:19, reason: User, spinning module GCodes, available RAM 7356 bytes (slot 1) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 24.5, current 26.7, max 27.8 Supply voltage: min 23.8, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max 0/223 Driver 1: standstill, SG min/max not available Driver 2: temperature-shutdown! short-to-ground standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: temperature-shutdown! short-to-ground standstill, SG min/max not available Driver 5: standstill, SG min/max 0/244 Driver 6: standstill, SG min/max 0/242 Driver 7: standstill, SG min/max 0/234 Driver 8: standstill, SG min/max 0/241 Driver 9: temperature-shutdown! short-to-ground standstill, SG min/max not available Date/time: 2020-06-16 09:59:35 Cache data hit count 4294967295 Slowest loop: 77.99ms; fastest: 0.09ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 167, MaxWait: 27507ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 11, completed moves: 11, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Stack records: 2 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 15.49ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.23 WiFi MAC address 2c:f4:32:58:8a:07 WiFi Vcc 3.38, reset reason Turned on by main processor WiFi flash size 4194304, free heap 23992 WiFi IP address 172.16.0.213 WiFi signal strength -58dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: no filamentAnd with 3.1.1
M98 Pconfig.g Error: endstop type 0 is no longer supported. Use type 1 and invert the input pin instead. HTTP is enabled on port 80 FTP is disabled TELNET is disabled Error: Heater 3 not found Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 542C Error: Fan number 3 not found Error: Fan number 4 not found Error: Fan number 5 not found Error: Fan number 6 not found Error: Fan number 7 not found Error: Fan number 8 not foundM122
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DJM-9178L-L4MSJ-6J9FG-3S86S-982QP Used output buffers: 3 of 24 (12 max) === RTOS === Static ram: 27980 Dynamic ram: 94372 of which 100 recycled Exception stack ram used: 264 Never used ram: 8356 Tasks: NETWORK(ready,392) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1552) IDLE(ready,80) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:57 ago, cause: software Last software reset at 2020-05-04 22:19, reason: User, spinning module GCodes, available RAM 7356 bytes (slot 1) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 25.9, current 26.6, max 26.9 Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: temperature-shutdown! short-to-ground standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: temperature-shutdown! short-to-ground standstill, SG min/max not available Driver 5: standstill, SG min/max not available Driver 6: standstill, SG min/max not available Driver 7: standstill, SG min/max not available Driver 8: standstill, SG min/max not available Driver 9: temperature-shutdown! short-to-ground standstill, SG min/max not available Date/time: 2020-06-16 10:02:11 Cache data hit count 57130340 Slowest loop: 78.89ms; fastest: 0.62ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 3.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 20.11ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.23 WiFi MAC address 2c:f4:32:58:8a:07 WiFi Vcc 3.38, reset reason Unknown WiFi flash size 4194304, free heap 24160 WiFi IP address 172.16.0.213 WiFi signal strength -54dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: no filament === DueX === Read count 1, 1.04 reads/min -
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?
