hbot homes correctly but prints mirrored ,
-
i just dont get it either. i even reflashed the firmware, it works when i revert the firmware to 2x.
im at a loss on this one i think..i can always work on the independant z axis for now
-
yes H7_pwm on the end of the expansion board
Where are you getting H7_pwm from .
i'm using this diagram https://d17kynu4zpq5hy.cloudfront.net/igi/duet3d/vqBUAZPsxMC5tRgt.hugepin 31 Heater7
-
-
here is another clue, after initial power up test bltouch goes in and out a couple o times, then i issue a bltouch test, where its sposta cycle in and out,,, well it does not..... but at that point i can unplug it , plug it back in and it wont do a self test.
-
You have it easy, without the expansion board it is I think the 10th pin from the left on the top set of pins.
It is midnight in the UK , so off to bed now , good luck and hope you find the problem.
-
@peter247
thanks for all the help. have a goodnight -
i have tried everything i can, except what works. and decided to revert back to 2.05.1
everything works even the bltouch. im going to wait till a more streamlined 3xx comes along.
want to say thanks to everyone for all the help along the way, it was not wasted as it showed me how to get the proper settings for homing and machine travel and set it all right in 2xx.last question, can the web interface be set up with keyboard commands, such as up , down , left , right arrow keys (keyboard input) to control motion on the printer?
-
Sounds like something hasn't made the upgrade to 3.1 fully , so when you downgrade it back to version 2 you get it working .
When I upgraded the firmware I first made a copy of my SD and put it on a new SD card so I could go back to the same configurations.
If you keep swapping between the versions with different config files , you may be forgetting to change a setting.
an the web interface be set up with keyboard commands, such as up , down , left , right arrow keys ?
No idea , it need some sort of key mapping .
-
@tracar Can you post the probe section of your RRF2 config.g? And I know you have confirmed the wiring, but could you post a picture of your Duet with the wiring connected so we can check? When you are moving between RRF2 and RRF3, are you changing all the files (homing and deployprobe etc) or just config.g? Or just using separate SD cards?
Ian
-
; Z-Probe
M307 H7 A-1 C-1 D-1 ; disable heater on PWM channel for BLTouch
M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y40.9 Z.445 ; set Z probe trigger value, offset and trigger height
M557 X50:400 Y50:400 S100 ; define mesh grid x50:400 starts at 50, ends at 400 SXX moves by what its set to between points -
@tracar Wiring looks very nice! The only thing I would say is that it would be better to route the endstop and probe wiring further away from the ribbon cable. There have been instances, mainly with the Duex expansion boards, when cables are run over or along the ribbon cable (which is unshielded), it can pick up interference, particularly if you are using Normally Open endstops. The interference is often on the SPI bus, and causes issues with the Duet and Duex communications. I don't know if this issue may effect the driver expansion board too, but it can't hurt moving the wires away from the ribbon cable. I don't know of any change between RRF2 and 3 that may increase the chances of interference; I think it's more likely a configuration issue.
The probe config you posted is still RRF3 (the pins are defined), not the working RRF2 config.
Ian
-
@droftarts
this z probe is what i currently have working in the printer right now . and it fully works with the bl touch.
the signal cables are all shielded, and when i get my 4ch optoisolator the machine will be updated to N/O endstops. and again all shielded cables. but for now they are not physically screwed to the machine for an earth ground till later, after its rebuilt and squared off. the wiring you see is temporary till i get everything installed and working, then everything will be shortend and , as you say some seperation of wires. -
@tracar Okay, if this is the code running with RRF2, then please send
M98 Pconfig.g
and I think you'll see errors. M950 is only supported by RRF3, same with the C parameter in M558. Could you please sendM558
and post the response?What is the probe deploy command (M280) in your working RRF2 deployprobe.g? Is it
M280 P7 S10 I1
? If it is, for RRF3, try inverting the heater 7 output in M950, ieM950 S0 C"!exp.heater7" ; create servo pin 0 for BLTouch
Ian
-
will test 7 hours from now when i get back from work.
-
M98 PCONFIG.G
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: M950 command is not supported
Warning: M950 command is not supported
Warning: M950 command is not supportedM558
Z Probe type 9, input 0, invert no, dive height 5.0mm, probe speed 120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-7J9D4-3S86R-KAA3N
Used output buffers: 1 of 24 (9 max)currently on the sd card:
; Z-Probe
M307 H7 A-1 C-1 D-1 ; disable heater on PWM channel for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y40.9 Z.445 ; set Z probe trigger value, offset and trigger height
M557 X50:400 Y50:400 S100 ; define mesh grid x50:400 starts at 50, ends at 400 SXX moves by what its set to between pointsi would have to update to 3xx to test anything else
-
@droftarts said in hbot homes correctly but prints mirrored ,:
current:
M280 P7 S10 :deploy bltouch
M280 P7 S90 I1 ;retract pinalso works the same as :
M280 P7 S90 ;retract pin without I1
and with : instead of ; normal? -
i have printing working as it should, on 2XX
still can not get dual independant z working with bltouch.
-
with it on 3.11
and the servo inverted - M950 S0 C"!exp.heater7" ; create servo pin 0 for BLTouchi get the pin to extend with m401. it will retract with m402
;Alarm Release + Pin UP
M280 P7 S160changed to?
*; Proberetract.g
M280 P7 S90change to M402
; probedeploy.g
M280 P7 S10change to M401
-
figgerd it out must all be P0
-
@tracar said in hbot homes correctly but prints mirrored ,:
figgerd it out must all be P0
The M950 creates a servo number defined by S. So S0 in your case. The M280 P value must correspond to the same servo index number you want to control. So in your case P0.