Invalid GPIO

Fishpig

Send: M98 P"CONFIG.G"
Recv: Error: M574: endstop type 0 is no longer supported. Use type 1 and invert the input pin instead.
Recv: Error: M574: endstop type 0 is no longer supported. Use type 1 and invert the input pin instead.
Recv: Turn off the current WiFi mode before selecting a new one
Recv: HTTP is enabled on port 80
Recv: FTP is disabled
Recv: TELNET is disabled
Recv: Error: M307: Heater 3 not found
Recv: Warning: M307: heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 542C.
Recv:
Recv: Error: M106: Fan number 3 not found
Recv: Error: M106: Fan number 4 not found
Recv: Error: M106: Fan number 5 not found
Recv: Error: M106: Fan number 6 not found
Recv: Error: M106: Fan number 7 not found
Recv: Error: M106: Fan number 8 not found
Recv: Warning: M307: heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 763C.
Recv:
Recv: ok

Fishpig

i tried to post those in the </> and it was flagged as spam

Phaedrux

@fishpig said in Invalid GPIO:

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later + DueX5

Are you able to update to 3.3?

It looks like your config is still using a lot of RRF2 syntax.

Fishpig

@phaedrux
don't have a link to the files do you?
also as i have a rare not well known printer i am a little hesitant to update further without some files to make sure it runs on this big girl, it's a work printer not mine personally.

oliof

@Phaedrux the custom vivedino board doesn't work with RRF since RRF3.1RC11 for unresolved reasons, see https://forum.duet3d.com/topic/16997/formbot-troodon-rrf-3-1-1-update/7 for the discussion back at the time.

EDIT: The config provided by vivedino is available at https://github.com/InsanityAutomation/FormbotTroodon/

oliof

@Fishpig check if that M42 P25 is maybe in your slicer's start gcode and remove if from there. Assuming the configuration files haven't been changed, there's no reference to a GPIO 25 in there. And yes, it looks like an RRF2.x config running on RRF3.x, so the configuration for the LEDs doesn't work.

Fishpig

Thanks guys,
i'll test out M42 P25 in a short while, i think i might try and find the RRF2.X firmware and go back to that.

Phaedrux

@oliof said in Invalid GPIO:

@Phaedrux the custom vivedino board doesn't work with RRF since RRF3.1RC11 for unresolved reasons, see https://forum.duet3d.com/topic/16997/formbot-troodon-rrf-3-1-1-update/7 for the discussion back at the time.

EDIT: The config provided by vivedino is available at https://github.com/InsanityAutomation/FormbotTroodon/

Yes I had suspected it was the custom board.

Fishpig

I just entered M42 P25

Send: M42 P25
Recv: Error: Invalid gpio port 25
Recv: ok

and it throws the error outside of starting a print.

Fishpig

@oliof
well would you look at that.....just got the cura going and found not only was it set to marlin but the start code was

M42 P25 S0
M42 P26 S0
M42 P24 S255
M280 P7 S160
T0
G92 E0
G1 E-10 F1800
G32
G29
G1 X0 Y0 F4800
G92 E0
G1 E10 F540
G92 E0
G1 E-3.0000 F1800
G1 Z0.200 F1000
G1 X400 Y0 E43.5631 F1000
G92 E0
G1 E-8.0000 F5400
G1 X205 Y200 F18000
G1 E0 F5400

oliof

@Fishpig good find. You should still update your config to 3.0 syntax.

@Phaedrux you never figured out what change in RRF broke the board, right?

dc42

@fishpig said in Invalid GPIO:

I just entered M42 P25
Send: M42 P25
Recv: Error: Invalid gpio port 25
Recv: ok
and it throws the error outside of starting a print.

Try a lower number than 25. I think 25 may be higher than the maximum allowed.

EDIT: the highest GpOut port number allowed in Duet 2 builds of RRF is 19.

Phaedrux

@oliof said in Invalid GPIO:

@Phaedrux you never figured out what change in RRF broke the board, right?

I don't think anyone affiliated with Duet has a Troodon board in hand to know how it's different.

oliof

Last I heard the only difference is that the TMC2660s stallguard pins are floating since those aren't required on the troodon. Otherwise, it's a single board combining Duet2Wifi and Duex5. Unfortunately, I don't have a board (or schematics) either.

oliof

@Phaedrux I ordered a board and expect it to arrive by October. If I don't manage to find the offending change by a couple bisecting builds, I'm happy to send it over to Duet3D for inspection.