Hello Guest it is April 23, 2024, 09:14:41 PM

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

1311
General Mach Discussion / Re: Tool Offset Macro...
« on: August 25, 2016, 07:10:22 AM »
sounds about right, didn't think you could macro out of reset.

still, as soon as i get the pulley and belt fitted I will have a working height setter at least, even if slightly clumsy, still better than the probing idea i think.

automating the job via messages would work, the dro does stay where it should when going in or out of reset and if you move it when in reset it does update when going out of reset :)

1312
General Mach Discussion / Re: Tool Offset Macro...
« on: August 25, 2016, 06:54:34 AM »
Yeah, i was one step ahead of you there Hood :)

I did think of automating it but of course as soon as the macro takes mach out of reset its game over for further macro code ( i think? ) Can a macro put Mach back in reset???

There is always a way, your suggestion is exactly my line of thought and will work, just a tad clumsy, but hey if it means i get a height setter for £3 then its not all bad :)

1313
General Mach Discussion / Re: Tool Offset Macro...
« on: August 25, 2016, 06:43:57 AM »
Yes that works well, BUT the DRO in mach does not update if mach is active and there is no motor feedback.

Out of reset it works well but no G-Code, not the end of the world but not 100% cool ;)


1314
General Mach Discussion / Re: Tool Offset Macro...
« on: August 25, 2016, 05:45:01 AM »
:)

To me "in reset" means Mach is not active, out of reset is ready to work.

Not quite an e-stop, just press the reset on mach screen.

1315
General Mach Discussion / Re: Tool Offset Macro...
« on: August 25, 2016, 05:22:14 AM »
Ooh, nice, little circuit works perfectly :)

Ok, now the next step:-

When mach is in reset the DRO works perfectly, accuracy can be set with motor tuning - nice.
But, we can't run the G-Code to read the DRO and load it into the tool table - what Hood said would happen earlier. The CSMIO still gets the data but does not let Mach see it unless in reset.

So, how do we tackle this hurdle :)

Do we have access to the CSMIO data, maybe we can read it direct, scale it and save it?

Any suggestions :)

1316
General Mach Discussion / Re: Tool Offset Macro...
« on: August 25, 2016, 03:26:08 AM »
Just had another look, there are no G outputs, its internal and used to flip the outputs into a third state of "off", looks like for logical use G needs to go high.

1317
General Mach Discussion / Re: Tool Offset Macro...
« on: August 25, 2016, 03:08:41 AM »
Ok, so G has to go one way but in this case it won't matter which way ?

And tie unused inputs to 0v.

1318
General Mach Discussion / Re: Tool Offset Macro...
« on: August 24, 2016, 12:09:46 PM »
Ok, line-driver IC just arrived, will get it wired tomorrow morning as its stupid-hot in the shop now.

I gather its just inputs on 1A, 2A, 3A and outputs on 1Y/1Z, 2Y/2Z, 3Y/3Z with a 0.1uf on the supply rails?

Ignore the G input which i presume is a gate?
Ignore unused 4th input?

Thanks

1319
General Mach Discussion / Re: Tool Offset Macro...
« on: August 24, 2016, 09:54:40 AM »
still waiting for parts but got a reply from Cs-Labs today, they reckon its not the correct way of doing stuff - using an axis input and Mach DRO BUT cant see why it wouldn't work :)

Seems i should be using the ENC module channels 2 or 3 for this.

Will have to see what happens before spending more. Got the linear motion part built and fitted the encoder, just waiting on the line-driver now.

1320
General Mach Discussion / Re: Restart while stop held in?
« on: August 24, 2016, 07:51:55 AM »
Ok, did a two-hour non-stop run this morning, worked perfectly.

The macro code i posted is a bit too basic, once tripped the message always stays on screen and mach is stuck in a loop until the vfd is reset.

Whats a good way to ensure the message only shows/resets mach if the code or spindle is running?

I tried adding GetOemLED(800) to the "If" line of the macro but it still gets locked up.