Posts made by fmeleard

Hello
I have an open question.

I would like to be able to create intermediate control points to ensure the position of the X axis

Let me explain.
My machine is very big (8 meters wide), 4 meters on the right and 4 meters on the left on the X axis.

I would like to create intermediate endstops to check at each tool change that the X axis has not moved without having to systematically travel 4 meters.

Basically, I would like to test the original endstop at the beginning (at + 4 meters) but after that, I would like to test the position from time to time only at the center.

I use HALL probes for my endstop and everything is fine, I don't know how to set up an intermediate endstop in Gcode...

I can do it in python via my raspberry by testing the probe value, but I think there is a Gcode solution that would allow me to do it.

In advance, thank you for your help
Francis

@dc42 @deckingman Thanks for your feedback
Concerning the analysis, with my Raspberry, I get a pretty accurate analysis (a few millimeters)...

In this case, if I understand correctly, the simplest thing would be to analyze the distance with the Raspberry, and to send the displacement via my python program in Gcode...

This is a possibility.

Otherwise, for my need of height analysis (outdoors for a max distance of about 90 cm) without need of accuracy higher than a millimeter, would you have a tip for a probe more adapted to the Duet3?

Francis

@phaedrux Hello,
I need some kind of Z probe.

My machine needs to do actions on variable terrain (from dirt). So I use an sensor ultrasonic to identify the height of the ground to trigger a DC motor.

My machine needs to work outdoors, so I don't use IR or Laser because of light disturbances, and I don't need to be accurate to the millimeter, but overall to the centimeter on the Z axis, so the sensor ultrasonic is fine.

My Need is:

1. You position yourself in X and Y (precisely)
2. You analyze the height of the ground -> Z (max analysis about 90 cm)
3. Go down Z (analysis of the height - the dimension of your current tool which can be variable depending on the current tool)
4. Engage the tool once it is in place
5. When it's done, you move Z back to the zero point of 0 (since there is vibration, I have to make sure Z hasn't 'moved' too much)
6. After your zero point, you go back to the tool change tray
7. You start the same process again with a tool that probably has a different height

I think it's a Z probe set up in a special way, I think

@fcwilt And normally I configure the Out with m950 j0 c "io8.out" q10000 and I read the result with "m950 j0"...
I think so

@fcwilt said in No results with an ultra sound sensor:

Well you have used io8.out to trigger the sensor but where have you connected the output signal from the sensor to the Duet?

Yes, I have connected the following items:

• 5V
• GND
• Trigger in out
• Echo in in

@fcwilt How can I check?

Hello,
I need to connect an ultrasonic sensor (picture below) but I can't read the returns from the probe

I have done :
m950 j0 c "io8.out" q10000 ; (the sound needs an implusion of 10u)
The result is "Pin io8.out, active: true"
But when I do "m950 j0" the result is always null....

I don't understand why.

Could you help me ?

PS: I know that the ultra sound sensors are not precise but in my project I don't need precision of height

Thanks in advance

@dc42 @dc42 Hello,
yes the connections are well on IN and GND and I have good feedback but not very precise.

I tested with the following options:
m308 s0 y "thermistor" p"^io6.in"
m308 s0 y "linear-analog" p"^io6.in"
m308 s0 y "linear-analog" p"!io6.in"
m308 s0 y "pt1000" p"!io6.in"
m308 s0 y "pt1000" p"^io6.in" T100000 B4725

I have some reactions but they seem strange, because for example I go from "Sensor 0 type PT1000 using pin !io6.in, reading 58.6 , last error : success, R:2200.0 L:0 H:0" to Sensor 0 type PT1000 using pin !io6.in, reading 2000.00 , last error : success, R:2200.0 L:0 H:0.

Which type should be used?
Is there any way to calibrate more or less the reading?

Thank you very much

Hello,
I'm trying to add a photocell to capture a laser.

I used (m308 s0 y "linear-analog" p"^io6.in") but when I do (M308 S0) the returns are random... the Y type must not be good, I think, but I don't understand what to take...
between ("thermistor", "pt1000", "rtd-max31865", "thermocouple-max31855", "thermocouple-max31856", "linear-analog", "dht21", "dht22", "dhthumidity", "current-loop-pyro", "drivers", "mcu-temp" ) unless I have understood absolutely nothing...

Thanks in advance for your help.

Below is a picture of my cell just in case

@dc42 Problem solved

My motors were on 800 ma when they should be on 3A... So, they did not seem to hold the position ...

Now the steppers stay well in place

Thanks a lot for your help

@dc42 The result :
M569 P0.3
Drive 3 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x08053, toff 3, tblank 1, hstart/hend/hdec 5/0/0, pos 8, tpwmthrs 2000 (0.9 mm/sec), thigh 200 (8.9 mm/sec)

M569 P0.1
Drive 1 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x08053, toff 3, tblank 1, hstart/hend/hdec 5/0/0, pos 520, tpwmthrs 2000 (4.7 mm/sec), thigh 200 (46.9 mm/sec)

M569 P0.2
Drive 2 runs forwards, active low enable, step timing fast, mode spreadCycle, ccr 0x08053, toff 3, tblank 1, hstart/hend/hdec 5/0/0, pos 264, tpwmthrs 2000 (4.7 mm/sec), thigh 200 (46.9 mm/sec)

@dc42 How to check if my configuration is on stealthChop ?

@dc42 Thanks a lot for your quick feedback

• I don't use M18 or M84
• I have applied M917 Z100 and M906 Z1000

The problem remains the same... it stalls a few seconds after reaching its location

Hi,
I use the Duet3 6HC to control a PLC on 4 axes.

The equivalent of the Z axis carries tools, and must remain in position in a certain case.

But it is impossible to lock its position, each axis moves correctly, but none is locked in position. My Z axis goes up, then down .... when I would like it to stay in position.

Is it possible to lock a motor in position?