Hello Guest it is April 19, 2024, 09:04:23 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 - Davek0974

1231
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 05, 2016, 05:02:35 AM »
Ah, got it, that was the point I ran out of time, it is on my list for tonight, will post answer when i get it tested.

To ensure pump is off, do you need to uncheck the option box and restart Mach or just uncheck the option?


1232
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 04, 2016, 04:05:04 PM »

you still haven't said what happened when you ran the one liner?


I did, in post 446 - it did work but i still needed to press stop before it would run again.

1233
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 04, 2016, 01:46:47 PM »
I guess so - the buttons part of the 2010 screen-set, it used to be the "semi-auto" manual tool-change setup but i cant use that on the Bridgeport as it needs a fixed touch-plate to get the reference height, works well on the engraver though.

I just pulled the original code from M881 that the button calls and replace it with my setter code - seemed like a good way to use an otherwise useless button.

It seems to do exactly the same as MDI'ing "M881"

1234
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 04, 2016, 12:08:33 PM »
Ah, yes ok,

I have no idea how the internals of the 2010 screen set work, maybe Ger21 could chip in with some insight?

But if thats how you call a file based macro then thats probably how it works.

1235
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 04, 2016, 11:42:51 AM »
Yes, this screen-set uses macro calls on most buttons.

How are the macros called? is it with the "code" call e.g.

code "M666"


I can only presume as the buttons are not editable :)

1236
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 04, 2016, 10:31:54 AM »
I can easily change back to the std screen set so thats ok, will kill the pump and try the cut-down code again.

Yes, this screen-set uses macro calls on most buttons.

1237
I did ask to use DRO100 but he said it was the encoder one so would not go for it.

Dro's above 1200 were then suggested as user ones but it seems some have been used by the system, maybe Ger forgot ;)

I have asked for a re-edit to another number.

I did try it on 100 as you suggested and it did seem to work but with no display.

I could not see DRO 100 on the 1024 set either?
Might have not looked hard enough though.

1238
General Mach Discussion / Re: Skip Tool-change if tool is loaded?
« on: September 04, 2016, 09:54:47 AM »
I have the fishing rod out now ;)

I will test this out as soon as other issues have been ironed out :)

1239
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 04, 2016, 09:53:10 AM »
Ok, thats good advice, but I have no idea how to find out why it will not release until stop is pressed, there is no "Terminating Script..." message etc.

All i can figure out is that it works if Stop is pressed first??

Having said that, I need to test again since moving to a UserDRO instead of the Oem803 one i was using, it may just be the DRO causing the hang.

Will have to test this tomorrow night as there was an issue with the DRO chosen which is being fixed now, this will give me a DRO that is totally isolated from the general Mach system so should be safe.

I am doubtful though as I am pretty sure it was  the same when I had the code cut down so far there was no DRO at all - it just read the value and poked it straight into the tool table.

Will find out tomorrow hopefully.

1240
Well, there was a slight hitch, fun to discover but no damage - it seems DRO1200 is really the ToolChange X-axis park position so as i was testing the macro motion I called a go-to-tool-change position macro and off it shoots to the same value as i had the tool setter set at :)

This is only relevant to the 2010 screen set though, i have passed it back to Ger for a fix :)