Actual RPM readout

If you have a question about the software please ask it here.

Actual RPM readout

Postby Vmax549 » Wed May 16, 2018 12:30 am

How long does UCCNC wait not seeing teh signal before it declares teh RPM as Zero ?

We ran into a crash situtation withteh new ATC and PDB. When teh M6 starts it monitors the actual spindle rpm to determine that it reaches ZERO before preceeding on.

What Derek noticed was that teh RPM display randomly displays ZERO while running 5000 rpms.

When teh M6 started and teh spindle started to slow down it SAW one of those ZEROs and activated teh PDB which lower it down onto a Fast spinning spindle. To say the least it made a LOT of noise.

Could be a dodgy signal but normally I see just a variance( up and down) in RPM not a complete zero display when running.
Has anyone else noticed teh Actual RPM going to zero when running ??

(;-) TP
Vmax549
 
Posts: 1009
Joined: Sun Nov 22, 2015 3:25 am
Location: USA

Re: Actual RPM readout

Postby cncdrive » Wed May 16, 2018 1:04 am

I will have to check what is the time constant we used, but the 5000RPM is a so fast speed that I don't think it will be the issue, because it would cause problems on low speed when the spindle is rotating slower than the time constant of the measurements and this is sure not the case with the high 5000 RPM.
I think it is more likely that the problem is the opposite of that, that the index signal is so short that the controller can't read it.
A quick calculation: 5000 RPM is about 83.33 rotations per second and that would be about 0.012 seconds per rotation.
Assuming that you have an encoder with e.g. 1000 counts per second and that the index pulse is 1 pulse long only then one pulse is only 0.012/1000 seconds long which is only 12 microseconds.
The controller needs at least about 20usec to safely read the signal, because there is a small low pass filtering implemented mechanically on the inputs to avoid noise spikes to make false triggers.
cncdrive
Site Admin
 
Posts: 1938
Joined: Tue Aug 12, 2014 11:17 pm

Re: Actual RPM readout

Postby Derek » Wed May 16, 2018 1:09 am

It's an AMT 103 if that helps.
Derek
 
Posts: 278
Joined: Mon Sep 05, 2016 9:57 am

Re: Actual RPM readout

Postby cncdrive » Wed May 16, 2018 1:34 am

With AMT encoders the index signal length is always as long as one pulse.
So, for example if you set it to 250 pulses per per rotation will read as 1000 signal edges (standard 4x encoder decoding mode) and then the signal is too short on 5000 RPM as I described above.
Because the AMT has changable resolution and so the index signal width also changing with the resolution I advice to calculate with minimum 20usec required signal length and adjust the resolution to that to make the index signal longer than that on the highest possible spindle RPM.
Also take into account if any breakout boards are used to connect this signal, because optical isolators may make the 20usec requirement even much higher depending on the optocoupler and the circuit used on the BOB, because optocouplers always delay the signal and so they will cut bandwidth lower. But if the signal is directly connected to the -5LPT motherboard inputs then you can calculate with 20usec which the controller can still read. It is not guaranteed that it will read shorter signals properly.
cncdrive
Site Admin
 
Posts: 1938
Joined: Tue Aug 12, 2014 11:17 pm

Re: Actual RPM readout

Postby Vmax549 » Wed May 16, 2018 1:38 pm

Thanks Balazs that lets me know what we need to do .

(;-) TP
Vmax549
 
Posts: 1009
Joined: Sun Nov 22, 2015 3:25 am
Location: USA


Return to Ask a question from support here

Who is online

Users browsing this forum: No registered users and 1 guest