Another interesting 'feature' that I've bashed up against.

our machine was working well during development, but recently I've generated a new profile cloned from a previous one. Now the spindle speed doesn't quite work as expected. M3 S400 turns it on, but only at the last running speed, it seems to ignore the s word for speed until a feedrate override button is pressed (163 or 164), and then the speed jumps to the speed requested.

not quite sure how to get round this one !

I will try issuing further S words in the morning to see if they change the speed in the same way as pressing the overide buttons.

I'll also try winding back to the previous configuration to see if that makes it work.

All other suggestinos welcome !

Tim

Are you issuing the M3S400 from code? Certainly never a problem here either on mills or lathe.
If you are issuing the M3S400 from VB then probably you need to enter the S400 then A sleep to let the DRO update then issue the M3.
Hood

thanks Hood, but it's not that. Once the spindle is running (after pressing the override button) I can issue a further S word, and the DRO (817) updates happily, but the change is not implemented until the override button is pressed again, and then it is implemented with the overide up or down as relevant.

Tim

Thats a strange one, not sure if it could/would affect it but have a look on General Config page and see if you have "No FRO on Queue" checked.

Hood

I think you have piece of VB code working against you constantly updating the Sdro. The tip is that the FRO works as it is totally different from the GcodeSpeed.

Just a thought, (;-) TP

hmmm - thanks folks.

TP - there's no VB doing anything with speeds except issuing an M3 S... command to start the spindle at a speed and then run a series of G81 cycles at scipt defined locations. Certainly nothing trying to override the speed or adjust it once it's started. Seems strange, because I have had the spindle starting and stopping correctly from VB script and the MDI, but now it simply wont !

Hood - "No FRO on Que" is not checked - should it be ?

Ta, Tim

I did not say override or adjust(;-) I said over write. I have done the very same thing long ago had a script running that ended up in a loop constantly overwriting the S DRO. NOTHING could change it BUT the SSO function. TOOK DAYS to run that one down.

Other than that I have never HEARD of what you are seeing happen.

Just a thought, (;-)

Sure, i can see where you're headed, but it can't be that.

DRO 817 is deisplayed, and that updates nicely as expected when an S word is entered either through script or MDI, but the change doesn't happen until an overide up/down button is pressed.

There's no VB that addresses any of the DROs that could affect the spindle - I've just double checked. I have looked for the following DROs - 39, 57, 74, 99, 117, 121, 202, 817.

Thanks for your thoughts, It certainly is odd.


Tim

Do you have any Brains or a macropump running?

(;-) TP

Does this happen anytime mach is running or just during running after a button push?

A duplicate DRO# can do the same thing.

Just some thoughts, (;-) TP