Hello Guest it is April 26, 2024, 10:48:53 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tmead

Pages: « 1 2 3 4 5 6 7 »
11
Thanks for all the comments !

The machine runs with a step/direction spindle, so is perhaps a little different to the PWM issue ?

The key feature that we've seen is that the spindle will only run at the previous speed when an M3 S ********* is issued, although the DRO will show the requested speed. There is no change until a spindle speed override is pressed, then it picks up the new speed as shown on the DRO. I have not tried running a VB script that issues an S word, pauses and then issues the relevant DoOEMButton........ that might have been a work-around !

However, a complete removal and re-install of mach3 fixed the issue. (remembering to grab a copy of the xml, macros, bitmaps, and gcode directories first  ;)  )

Tim

12
Sorry for the delay - new job means this has taken a back seat fro a while.

I took a good look last night, and still have no idea ! I disabled the macropump and loaded the unmodified 1024 screenset, the reaction was still the same - any spindle S words were accepted, the DRO was updated, but the physical spindle speed did not change until a spindle speed override button was pressed.   >:(

i gave up ! :'(

The xml and other bits/pieces were copied out, and a complete uninstall/reinstall of mach completed, using the same version (3.042.025). It works now !  ;D

So, as I said - I'm no further forward in fault diagnosis, but the symptoms are fixed, using the same macropump, same gcode, same bitmaps and same screenset. There must have been a setting in there somewhere that i'd accidentaly changed.   ???

Anyway - thanks for all the people that thought about this, and offered suggestions.

Tim

13
There are only three occasions where a DRO appears twice on one page, and those are the X, Y and Z position DROs.

They are also on an unused screen (17) that was used temporarily for some layout work and trialing.

No access to the machine at present, so testing the presence/absence of the macropump will have to wait.

Tim

14
My apologies - I've read the OP again, and I did slip up and write feedrate override, rather than spindle override.

There are spindle override buttons on the bottom of page 2 I believe (can't open the screenset from here). I orignially identified the issue by switching to the 1024 screenset and using the buttons there.
I have the same issue when entering the M3 S400 command in the 1024 screeenset, which is not running anythign else in the background. Yes, my code does organise some motion, but even without the code doing anything, or using a screenset that has minimal code it still doesn't work. I will have a go at turning off the macropump in the general config, and then starting and stopping the spindle and changing speed from the 1024 screenset, just to check that there is no strange interaction there.

I'll try opening in Mach Screen and looing through for duplicate DROs, is there an easy way to do this ? I'm not quite sure what you mean, as there are two versions of one user DRO on a page, one as a readout and one as a slider.

Tim

15
We're using our own screenset, as attached.

The first screen (Page 1) runs a simple script when the image button is pressed that references all axes and then sorts out a few variables. It then opens page 2, which should use a sensor to determine the position of the clamps as diifferent sizes of material can be used. the third screen allows the user to enter a particular mix of orders and start the cutting. this is the only script place that starts teh simpndle.
there are MDIs on pages 2,3,4 and 5.

Tim

16
Hi TP,

no brains, (and that's just me !) but there is a macropump that updates some user DROs. Definitley not anything to do with the spindle.

The issue is always there, as soon as the machien is turned on and the axes refernced, I've tried using the MDI with an M3 S400 command, and nothing happens until the overide buton is pressed. Same as the issue that occurs when the M3 is issued by the VB from button.

Tim

Tim

17
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

18
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

19
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

20
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

Pages: « 1 2 3 4 5 6 7 »