Messages

1261

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 03, 2016, 02:06:09 PM »

Its CS_Labs way of turning on and off the many outputs

1262

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 03, 2016, 12:06:40 PM »

Thanks Stirling, zip file attached with the macro pump as it was at that stage and the macro that is called from a screen button.

1263

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 03, 2016, 10:30:04 AM »

Short video of it in use, this was with the A axis DRO which may have been the cause of some odd behaviour, not sure yet.

https://youtu.be/wqNGfHuCY4w

Anyone know how to add a user DRO? I tried in MachScreen but it seems to only let me add OEMDRO's

1264

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 03, 2016, 08:33:29 AM »

Well, i'm not sure if it is the DRO or the macro pump BUT I have taken it all out of the pump, put the whole lot inside the setting macro - it now operates blind but works ok and all other functions have returned.

I will find my copy of MachScreen and throw a DRO in there and try again but its not installed on the box yet.

Very odd.

1265

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 03, 2016, 07:31:50 AM »

Well, i am being driven to despair with this damn thing, honestly! If i could lift it, i would stuff it in the garden and torch it!

Thought i was getting somewhere, as usual, went to test the values stored which looked good on screen by doing a dummy setup and placing each tool then going to Z zero.

Normally when I put a tool in the "current tool' box the Z DRO updates to reflect the new offset. This has stopped working now, it either does nothing or updates to a random number or updates after a random length of time.

I video'd it here as i needed to cool off over a coffee...

https://youtu.be/FN248GRWwu0

It has values for tool zero - this should always be zero? A value of -881mm - thats a big offset!!
This has nothing to do with whats in the table.

Does this damn system actually work or what? I cannot see anything i have or am doing that can cause this???

Any suggestions?

1266

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 03, 2016, 06:18:23 AM »

Now we're getting there

The SetToolParam version works perfectly with no messing or pauses.

I will stick a bit of video up on the 'tube and a link later.

It's fast, easy, simple - just what is needed.

One oddity - after running the macro once and ok'ing the tool-table etc, the macro will not run again unless the Stop button is pressed?
I tried putting an "End" command on the last line but no change, i added a DoOEMButton(1003) and it works perfectly.
No idea whats going on there but hey-ho

1267

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 03, 2016, 04:08:43 AM »

Ooh, that would explain it nicely, i did not know it worked through the buffer.

I will certainly try that code instead, thanks

1268

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 03, 2016, 03:50:20 AM »

Has Mach4 got CV yet or S-Curve acceleration, I hear thats pretty useful??

I would try it but just not as confident in it as i am with Mach3.

Yes this could well be a PC thing, these are Dell Optiplex Gxx boxes and i've read different things about compatibility but if the fix works then

1269

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 02, 2016, 03:53:32 PM »

I think it was 062 i was previously advised to run.

Just been messing about on my laptop setup - that exhibited the same behaviour whereby the value was not shown in the table until reloaded.

I added a SLEEP 1000 between the Gcode being written and the DoOEMButton(121) and it works perfectly every time.

Will try this tomorrow on the machine but it seems it needs a small delay there?

1270

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 02, 2016, 03:42:50 PM »

Thats what i suspected but i ruled that out by removing the DRO stuff from the macro and just telling it to write 5 as the offset - it would not even do this.

When i was messing with my automatic version before, it still did not show the new value in the table unless it was loaded, unloaded and loaded again?

Something odd going on here, will try again after a reboot in the morning.