Hello Guest it is April 25, 2024, 10:35:39 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 - Tony Bullard

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 »
11
Thank you Steve.

I installed in build 4612 in "C:\Mach4Hobby-4612". Imported my profile and my screen sets in 4612 and all worked well. Restored my computer to three days ago and updated  "C:\Mach4Hobby" to build 4612 again and all is well. I don't know what the problem was but it is fixed now. Thank you!

Tony

12
I updated to version 4.2.0.4612 from 4.2.0.4300. Now I can't load screens. I get this message:

Mach4gui Error
Unexpected Exception has occurred: bad allocation, the program will terminate.

I switched back to .4300 and all is well. Any help would be appreciated.

Thanks,

13
Mach4 General Discussion / Re: Merry Christmas
« on: December 18, 2020, 03:42:11 PM »
Mary Christmas and Happy new year too Bill and to all the generous and supportive people on this forum who help so many rookies like me. Thank you All.

Tony

14
Mach4 General Discussion / Re: G31 not working in screen function
« on: December 18, 2020, 07:29:25 AM »
The trouble with mc.mcCntlGcodeExecuteWait is that it pauses the PLC script while it is waiting so the position DROs in the GUI don’t update until it is done.

DasTheGas has a great tutorial on coroutines that explains this: https://www.youtube.com/watch?v=t2xQYvAXT8o

15
Mach4 General Discussion / Re: G31 not working in screen function
« on: December 17, 2020, 10:51:58 AM »
I think I'll have to write a coroutine.yield() after the probe move for the rest of the code to execute properly. Stay tuned!

16
Mach4 General Discussion / Re: G31 not working in screen function
« on: December 17, 2020, 10:42:00 AM »
Thank you! That worked. I've been fighting with this for a week. I really do appreciate your help.
Tony

17
Mach4 General Discussion / G31 not working in screen function
« on: December 17, 2020, 09:51:44 AM »
Mach4Lathe: When G31 G01 X-.20 F5 is called from the MDI the machine stops at the probe strike as it should.

I have this function in the screen load script and it is called from a button press.
Code: [Select]
function TestG31()
local inst = mc.mcGetInstance()
mc.mcCntlGcodeExecute(inst, "G31 G01 X-.20 F5")
mc.mcAxisHome(inst,0,0)
end
It doesn’t stop at the probe strike but finishes as a G01 X-.20 command. I eventually would like this code in the RefAllHome() function to stop on an encoder Index pulse.
Any help with this would be appreciated.


18
I found out the SmartBob plugin only supports one probe, probe 0 and it has to be an input signal to the PMDX motion controller.

19
Thank you. I have Pokeys57ECNC on my Hurco Mill and their plugin works beautifully with home with index. The lathe I'm trying to set up for my son in law uses a PMDX 424 motion controller and SmartBob plugin which I don't believe supports this function.

Will your Mach4 Lathe support any G31 functions in the MDI?
Is anybody using G31 functions in Mach4 Lathe?
Thanks,

20
Mach4 General Discussion / Mach4 Lathe Home with limit and encoder index
« on: December 06, 2020, 07:56:27 AM »
I have encoders with index pulse on the lead screws and X and Z limit switches. I would like to home on the limit switches then move off to the first index pulse using a probing call, mc.mcCntlGcodeExecute(inst, "G31.3 X-.5000 f2"), near the end of the refAllHome function.

There is no Probe, Probe1 or Probe2 Signals under the Control Configuration Input Signals. There is Digitizing, and Probe3 through Probe9. The G31 doesn’t work even in the MDI with a probe signal from a push button for test and a LED assigned Input Signal = probe3. The LED lights but the motion doesn’t stop until G31.3 finishes. At that point the X, Z and A probe # variables are updated.

Any help with this would be appreciated. Also is the a different or better way to do this?
Thanks

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 »