RRF3 Config Issues
-
Hi @garyd9
Thanks for your reply. I had a look at DWC and it is saying as you mentioned that the probe is 1000. Putting the ! in front however has not changed that and now it is throwing a fault saying the probe is triggered at the start of the probing move. I have tried changing it from P5 to P8 and that has done nothing as well.
Do you have any other suggestions?
Cheers
SamCustom Core-XY
-
What was your M558 line in RRF2? Using that information would make it easier to know how to convert it.
If it helps, my own precision piezo orion was configured (and functional) in RR3 using:
M558 P8 R0.4 C"!zprobe.in" H3 F300
I also at one point had "^!zprobe.in", but the caret in front didn't seem to make any difference.
In both cases, my G31 had a P parameter of 500
-
HI @garyd9
I had attached both the old and the new to the first post but it seems to have put them on one line so it only looks like 1 file attached.
Here is my homing config for RRF2
M574 X1 Y1 S1 ; X home to min. Y home to max. Normally Closed limit switches.
M574 Z1 S0
M558 P8 I1 R0.4 F300 X0 Y0 Z0 A5 ; digital piezo sensor, output rises on contact, probing speed, not used to home axes
G31 X0 Y0 Z-0.085 P500 ; sensor is nozzle and debounce value.Cheers
Sam -
M558 P8 I1 R0.4 F300 X0 Y0 Z0 A5
X,Y,and Z on M558 haven't been used since RRF 1.19, so can ignore them
I believe that a piezo is consistent enough to not need repeating, so "A" can be removed. (I don't know if RRF3 supports it or not.)
It's missing a dive height (H) param. The default H value is 5.
So, that leaves "M558 P8 I1 R0.4 F300 H5"
Converting that to RRF3 is really easy for me, as it's nearly identical to my piezo orion config. Here's the M558 I used successfully with RRF3:
M558 P8 R0.4 C"!zprobe.in" H5 F300
This assumes the orion is attached to the duet board using the z-probe header, pins for 3.3V, GND, and probe in. (Probe.Mod isn't used.)
That, followed by "G31 X0 Y0 Z-0.085 P500" should work for you (unless something is broken.)
My suggestion is to send both the M558 and G31 commands manually in the console in DWC. Ensure no errors. Run "M558" and "G31" in the console with no parameters to ensure the values it reports back are the same. Then look at the z-probe status in DWC and ensure the z-probe status is 0, AND look at the orion and ensure the red LED is lit.
The orion should have a red lit LED and the z-probe status should be 0. If you tap your nozzle, the red LED on the orion should go out (and perhaps a blue one will flicker on) and you may (or may not) see the z-probe status change to 1000 very quickly.
The the orion doesn't have a red LED while at rest, then something isn't working with the orion. If the orion has a red LED at rest, but DWC is reporting a z-probe status of 1000, then something might be broken with the orion or an issue with wiring. (I don't know which.)
Honestly, that's about as much help as I can give without moving into the realm of pure guessing (which I wouldn't want to do with anyone's printer except my own.)
-
@samlogan87 said in RRF3 Config Issues:
Hi @garyd9
Thanks for your reply. I had a look at DWC and it is saying as you mentioned that the probe is 1000. Putting the ! in front however has not changed that and now it is throwing a fault saying the probe is triggered at the start of the probing move. I have tried changing it from P5 to P8 and that has done nothing as well.
Do you have any other suggestions?
Cheers
SamTry enabling the pullup resistor as well, using "^!zprobe.in" in your M558 line.
-
@garyd9 I changed it to what you had and it made the printer start with a 0 probe reading but as soon as I touched it with my hand, the light on the orion turned blue and turned off after but the probe reading stayed at 1000. Adding the pull up resistor as @dc42 suggested has fixed that now, which is fantastic.
The next issue is my water cooling for the hot end is still running all the time and non of the virtual heaters are being displayed nor working when I change the starting thresholds below the current temp of them.
Cheers
Sam -
So a bit more of an update, I have sorted the water pump running all the time. I had the fan set as fan7 not duex.fan7. That has stopped it from always running, however it is not showing its rpm in dwc.
I have this as the code now:
M950 F7 c"!duex.fan7+exp.^pb6" ; Assign Fan 7 to Fan 7 Port and Inverse
M106 P7 H1 B1 L0.3 X0.7 T60 C"Extruder" ; Water Cooling Pump StartI have just tried it like this:
M950 F7 c"!duex.fan7+^pb6" ; Assign Fan 7 to Fan 7 Port and Inverse
M106 P7 H1 B1 L0.3 X0.7 T60 C"Extruder" ; Water Cooling Pump StartAnd my DWC has locked up with a dark shade to the screen. Refreshing it doesn't seem to fix it so it looks like I will be pulling the SD card out and changing it back as it doesn't seem to like it.
Any more help on this issue and the virtual heater would be gratefully accepted.
Cheers
SamCustom Core-XY
-
Hey everyone,
I was wondering if anyone could shed any more light on my issues with my config. The virtual heaters are not showing and the fans are not working with them when I manipulate the starting thresholds. I have also noticed if it is any help that they are being displayed in the fan section when I did not think they should as they are thermostatically controlled. My part cooling pump is also not working and that I could control with the slider.
Cheers
Sam -
Hey Everyone,
Can somebody please help.....
I am still having the below issues with my board cooling. I am not sure what I am doing wrong but the fans won't run and I can not see them being displayed in the extra box. Here is the code
;Board Cooling Fan M308 S100 P"mcu-temp" Y"mcu-temp" A"Duet Board" ; Map Duet MCU to the Extra Table M308 S101 P"Drivers" Y"drivers" A"MCU Drivers" ; Map Duet Drivers to the Extra Table M308 S102 P"Drivers-duex" Y"drivers-duex" A"Duex2 Drivers" ; Map Duex2 Driver to the Extra Tabl M308 S103 P"e1temp" Y"thermistor" A"Control Area" T100000 R4700 B3950 ; Create Virtual Heater for Control Area M950 F1 c"!fan1" Q25000 ; Assign Fan 1 to Fan 1 Port and Inverse M106 P1 L.3 B.5 T30:65 H100:101:102 C"Duet Fan" ; Set fan 1 PWR fan. Turns on when MCU temperature, hits 45C and full when the MCU temperature reaches 65C or if any TMC2660 drivers (virtual M950 F2 c"!fan2" Q25000 ; Assign Fan 2 to Fan 2 Port and Inverse M106 P2 L.3 B.5 T30:40 H103 C"Control Area" ; Set fan 2 PWR fan. Turns on when MCU temperature, hits 45C and full when the MCU temperature reaches 65C or if any TMC2660 drivers (virtualCheers
Sam -
@samlogan87 Hi Sam. I'm currently in Canberra so closer to you than I am my printer, and I only have my 'phone in front of me so can't be much help. I notice that you have lower case "c" - not sure if it matters but maybe try upper case C?
AFAIK, driver temps are just high temp alarm outputs so they likely won't show on DWC extras. -
@samlogan87 said in RRF3 Config Issues:
M950 F7 c"!duex.fan7+exp.^pb6" ; Assign Fan 7 to Fan 7 Port and Inverse
Use ^exp.pb6 as the tacho pin name.
Max sensor number in M308 commands is 31 on Duet 2, 64 on Duet 3.
I recommend you run M98 P"config.g" so you can see what error messages are emitted by the commands on config.g.
-
Hi @deckingman I hope you are not too affected by the fires there at the moment. It is pretty horrible. David was right in the fact that I had several sensors that we in the 100's for sensor numbers. I guess it was a bit of a hangover from the sensor assignment in RRF2 for the MCU and Drivers.
@dc42 I did not see anywhere in the documentation about the maximum number of available sensors? Also the tacho assignment is not that well defined in the what you need to do document. In some places it is assigned as +^pb6, others are as you have mentioned. It is a wee bit confusing.
Cheers
Sam -
@samlogan87 Off topic I know but yeah, the smoke is pretty bad some days. Had we arrived a day earlier, we wouldn't have been able to get from Melbourne to Canberra because Qantas ground crew in Canberra refused to work in it. My newly arrived grand daughter has been pretty much house bound since she was born. Rain is forecast later this week so hopefully that'll do some good.
