Back after a while - dc42 hot end probe inop!

Hi folks,

I've been away for a while and so completely lost track of firmware / web versions and everything else. I've got my Ormerod (V1) set up again, and have loaded the latest firmware and replaced all the files on the SD cards with ones from dc42's github.

I use an ultrasonic sensor, so changed to M558 P3, however I'm just getting random numbers above 500 no matter what.

I've also tried P1 and P2, and they both are giving nonsense values.

Is something broken, or have a missed something (for example, has a wiring connection on the Duet changed or something?

Thanks,

Steve

The connection has changed to the upper connector, second row, sixth pin from the right.
[reprappro.com]

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

That didn't solve things I'm afraid.

If I move my blue wire from the 9th to 6th pin, I get a zero reading in all three modes, and the hot end fan runs constantly.

Got it!

Quote
* The Z probe blue wire (and the white wire, if you are using one of my hot end boards) connect to different pins, like this:

pin 2 > ......................... < pin 50
pin 1 > ...................ST.... < pin 49

S is the ZProbe signal output (blue wire, 6th pin from right, bottom row). T is the trigger/modulator input (white wire if you are using one of my hot end boards, 5th pin from right, bottom row).

I needed to move the white wire as well.

Nope, still something weird going on. It's only using IR and not ultrasonic, and if I send M558 P2, the hot end fan goes off!

Edited 1 time(s). Last edit at 09/13/2015 09:17AM by stevelup.

Can you confirm which version of the firmware you are running? My latest is 1.09j.

M558 P2 won't work with my boards, because that's for a simple modulated IR sensor. Have you tried M558 P1 since you moved the connector?

Can you post a photo or photos showing where you have all 4 of the sensor wires connected on the Duet?

Edited 1 time(s). Last edit at 09/13/2015 09:35AM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Hi

I'm running 1.09j.

P1 and P3 both work (in that they give good readings from the IR sensor), but it's not switching to the ultrasonic for some reason with P3.





Thanks for your assistance!

Regards,

Steve

Here's my config.g for reference, using David's dambuster probe and latest firmware

M111 S0; Debug off
M550 PBigfoot ; Machine name (can be anything you like)
M551 Preprap ; Machine password
M552 P192.168.1.14 ; IP address
M553 P255.255.255.0 ; Netmask
M554 P192.168.1.1 ; Gateway
M555 P2 ; Set output to look like Marlin
G21 ; Work in millimetres
G90 ; Send absolute coordinates
M83 ; relative extruder moves
M906 X1000 Y1200 Z800 E1200 ; Set motor currents (mA)
M563 P0 D0 H1 ; Define tool 1
G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
M92 E420 ; Set extruder steps per mm
M558 P1 ; Use an unmodulated Z probe or an intelligent Z probe
G31 Z0.15 P500 ; Set the probe height and threshold (put your own values here)
M201 X800 Y800 Z15 E3600 ; Accelerations (mm/s^2)
M556 S78 X0 Y0 Z0 ; axis compensation
M203 X15000 Y15000 Z100 E3600; Maximum speeds (mm/min)
M566 X1800 Y1800 Z30 E20 ; maximum jerk speed mm/minute(i.e. maximum instantaneous change in speed)
M208 X210 Y205 ; set axis travel
M208 X 0 S1 ; set axis minimum
M574 X0 Y2 Z0 S1
T0

Erik

The probe will switch to ultrasonic when the pin on the sensor board connected to the white wire is pulled low. This should happen when you use M558 P3. If it doesn't switch, there are a few possibilities:

1. The white wire is connected to the wrong pin on the Duet.

2. There is a break in the white wire, most likely at the crimp connection at one of the ends.

3. Although you have M558 P3 in config.g, something else is switching it to P1. This can happen if you are using the RepRapPro homing files, because they switch the sensor between P1 for X homing and P2 for Z homing. So check your homing files. I can't remember exactly what homig files I have in my repository at the moment, so they may be set up for the RepRapPro proximity sensor.

4. There is a firmware bug and the firmware is failing to drive the modulation pin low when you specify P3. The code looks OK to me, but I haven't tested it recently.

5. Something else I haven't thought of.

If you have a multimeter, you could measure the voltage on the pin on the sensor board that the white wire is connected to. It should be around +3.3V when you use M558 P1, and 0V when you use P3.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Hi

The white wire remains at +3.3V regardless of the M558 command.

I currently have it connected to the fifth pin from the right on the bottom row of the top connector.

I've had a look at platform.h:-

#define Z_PROBE_PIN (10) // Analogue pin number
#define Z_PROBE_MOD_PIN (52) // Digital pin number to turn the IR LED on (high) or off (low)

But I don't really understand how those numbers relate to the physical pins on the board. I've looked at the schematic and Z_PROB_MOD_PIN is connected to PC11.

Thanks again!

Steve

Hi Steve,

The problem you are experiencing is caused by a firmware bug - I'm sorry about that! I will fix it in version 1.09k. In the meantime, you could connect the white wire to ground to force the sensor into ultrasonic mode always, but I am not sure whether that will work for X homing.

David

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Many thanks. I'll see if it can home X using the ultrasonic. If not, it's no big deal waiting for the next release. The thing has been in a box since March anyway!