Advanced Search

Not unless it got there from the easy probe I tried to install.

Thank you for your help, I have had a sick feeling since this started, not because of the lost part but because it didn't seem like I would find the answer. Thank you for helping!!

I have been using the machine for 3 years now. I have even made these parts before. I will post the files in a few.
It does not do this all the time mind you.

net probe-in => motion.probe-input
net probe-in <= parport.0.pin-11-in-not

this should be all you need for the input in your main hal

are you in the sim?

andypugh wrote:

Sviper wrote:

Is it possible to use spindle synchronization with only one initiator that monitors the spindle speed?

Yes. No need for anything particularly clever.

loadrt encoder
...
addf encoder.0.capture-position servo-thread
addf encoder.0.update-counters base-thread
...
net pulse-index-combined parport.0.pin-NN-in encoder.0.phase-A encoder.0.phase-Z
setp encoder.0.counter-mode 1
net spindle-position encoder.0.position-interpolated => spindle.0.revs
net spindle-velocity encoder.0.velocity => spindle.0.speed-in
net spindle-index-enable encoder.0.index-enable <=> spindle.0.index-enable

Basically connect phase-A and phase-Z of the counter to your parport pin, make sure that you set the encoder to counter-mode and ensure that you use the position-interpolated pin to smooth the motion.

Hello.
Is it possible with this one index signal make a spindle orientation always in one position?
Spindle stop at the same position after index input goes active.
I'm reading out now with this example the current rpm of the spindle. (just on a mesa board 24v input)

thanl you for replay , but i want to use arduino with 600ppr encoder can i

So when using the clothoid filles, a divided trim is a signal to not add a trim segment to it. As this can result in going trough
the workplane.
Otherwise when using the bspline fillets, this uses a set off controlpoints. I suggest that bsplines are still valid, as they don't need
to solve the G2 problem.
Line fillets (chamfers) are still valid.

Hi Arciera,

Post 22 Oct 2024 06:03
This go trough workplane bottom problem can be avoided by checking :

1.If you have a trim lenght of 5mm. And the line is 15mm, then the line will be trimmed at the ends, resulting a netto line length 5mm.
2.In the case of your post, the trim dist is divided to fit. The line is for example 5mm. Trimming 5mm both ends will fail, then the trim is
divided to fit, wich results for example in a trim 2.4mm x 2 = 4.8mm, Then the netto line is 0.2mm.

Related calculation:
Solution:
When a trim distance has to be lowered to fit, this then can be a reason to skip this line trim. Let the line as is.
When a full trim fit can be done, the clothoid has no reason to go trough the bottom of the workplane. This then is valid.

Post 22 Oct 2024 07:50
The function loops to all the segments. Here it sets one exception:
Do not trim this line end if upcoming line is colinear to this.

We can add more exceptions here.

Is there a particular reason for not handling one fillet after the other?
In a other function, we start with a list of segments. (gcode input) .
They then already have a flag if they may be trimmed front & back.
It this point the empty fillet segments are inserted inbetween. This is a vector insert operation.

Once the empty segments are in place. Then we add the values to the fillet by looking, what kind of fillet we are going to produce.
We now have 3 types : line, bspline or clothoid.

Nice you are digging into the code!
Are you using qt for it as viewer and editor? This should be the nice as you can load the cmakelists directly in qt.

Good luck.








 

Sorry, it still doesn't work. Following the above method still has problems.

More info, I've been playing around and figured out the probe triggering (as in switching states in HAL_METER from false to true) Just has a wire crossed over.

But the behaviour is still the same I press probe there is no machine movement but the machines DRO in probe basic starts counting down slowly as if the Z axis is going down. Only now I can trigger the tool setter or probe (I have them in series with each other as they are NC) and the DRO stops.

I've also noticed that no matter which direction I select to probe for example X+ direction probe, its the Z DRO that starts counting down, same if I click Z- probe or Y- probe or any of them.