[LinuxCNC/linuxcnc Issue#629] hal status shows wrong spindle speed in constant surface speed

#1 – c-morley 于 2019-08-08

I believe that linuxcnc usually reports the requested speed, not the actual speed.
In constant surface feed you are saying it reports the maximum speed allowable?

Oh in 2.8 + Gstat will report the actual spindle speed as long as you connect something to HAL pin spindle.0.speed-in

#2 – rene-dev 于 2019-08-10

in css mode the requested speed changes, even with no encoder. so this is clearly a bug. the requested speed is send to the drive, so that value should be reported everywhere.

#3 – andypugh 于 2019-08-10

Might be difficult. I think the NML message is the css number, and the calculation is done as the HAL pin is set. There may be no existing path for that number back to the user space layers.

#4 – gmoccapy 于 2019-08-12

> Oh in 2.8 + Gstat will report the actual spindle speed as long as you connect something to HAL pin spindle.0.speed-in

I just looked at the code of GSTAT in 2.8 and I do not see any report of spindle speed. We do not need the spindle feedback, as the value we need is the commanded speed and that do change according to the dieter of the work piece.

#5 – c-morley 于 2019-08-12

actual-spindle-speed-changed is the message to watch for. I assume you are trying to do surfacefeed eater calculations or something similar. This would allow you to calculate the actual rate ad long as there is feedback connected. We could also change requested-spindle-speed message to watch the proper Hal to get what you want..as a work around.

——– Original message ——–
From: Norbert Schechner
Date: 2019-08-12 1:43 p.m. (GMT-07:00)
To: LinuxCNC/linuxcnc Cc: c-morley , Comment
Subject: Re: [LinuxCNC/linuxcnc] hal status shows wrong spindle speed in constant surface speed (#629)

Oh in 2.8 + Gstat will report the actual spindle speed as long as you connect something to HAL pin spindle.0.speed-in

I just looked at the code of GSTAT in 2.8 and I do not see any report of spindle speed. We do not need the spindle feedback, as the value we need is the commanded speed and that do change according to the dieter of the work piece.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/LinuxCNC/linuxcnc/issues/629?emailsource=notifications&emailtoken=ABYGWNIHY4IC6XLSFOCELHLQEG4MNA5CNFSM4IKCMKMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4DTSWA#issuecomment-520567128>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABYGWNOCAJMIGOP4M6DS3KTQEG4MNANCNFSM4IKCMKMA>.

#6 – gmoccapy 于 2019-08-12

Chris, it is not to find a work around, i have such a solution reading the spindle feedback bar of gmoccapy. The fact is, that linuxcnc should report the actual commanded spindle speed, not the maximum allowed one.
Imho the actual behavior is a bug!

#7 – c-morley 于 2019-08-12

Oh I agree. It just might be hard to fix. Using Gstat would not require anyone to connect a HAL pin..if we changed the requested-speed function. But yes ideally it should be reported correctly

——– Original message ——–
From: Norbert Schechner
Date: 2019-08-12 3:08 p.m. (GMT-07:00)
To: LinuxCNC/linuxcnc Cc: c-morley , Comment
Subject: Re: [LinuxCNC/linuxcnc] hal status shows wrong spindle speed in constant surface speed (#629)

Chris, it is not to find a work around, i have such a solution reading the spindle feedback bar of gmoccapy. The fact is, that linuxcnc should report the actual commanded spindle speed, not the maximum allowed one.
Imho the actual behavior is a bug!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/LinuxCNC/linuxcnc/issues/629?emailsource=notifications&emailtoken=ABYGWNN2DSG32W7LTJP22ILQEHGMTA5CNFSM4IKCMKMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4D2VDI#issuecomment-520596109>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABYGWNMNNEJAES3EPIQPOI3QEHGMTANCNFSM4IKCMKMA>.

#8 – andypugh 于 2019-08-13

Speed is calculated on-the-fly here, and put straight on the HAL pin.
https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/motion/control.c#L1878
An element would need to be added to emcmotStatus to transfer that data back upstream to the userspace layers.