Hello Guest it is May 12, 2021, 06:50:36 PM

Author Topic: M62/63 Command issue  (Read 547 times)

0 Members and 1 Guest are viewing this topic.

M62/63 Command issue
« on: December 27, 2020, 12:31:31 PM »
I have searched this forum looking for any help on this issue I am having with M62 / M63 commands. With no luck.

My current setup is Mach 4 and Pokeys57cnc. Everything has been pretty much working perfectly with my CNC mill. I am now trying to add a diode laser and use the M62 and M63 commands. I have been unsuccessful in getting the commands to work. I have been emailing back and forth with Pokeys. They did point out a coupe setup mistakes. I have fixed them but I am still unable to get the M62 / M63 commands to activated the OC output on the Pokeys57cnc.

I have been using the MDI and Machine Diagnostics tab with the following test G-code. I get no LED indication of the output activation.  I have also attached my Packaged Mach4 current profile if anyone is able to look at it.
M62 P0
M63 P1
G01 X0.1

M63 P0
M62 P1
G01 x0

M99

Thanks for any help.

Re: M62/63 Command issue
« Reply #1 on: December 27, 2020, 02:26:32 PM »
i alway use to activate output:
local Osig = mc.OSIG_OUTPUT1
ocal hReg = mc.mcSignalGetHandle(0, Osig)
mc.mcSignalSetState(hReg, 1)
Re: M62/63 Command issue
« Reply #2 on: December 27, 2020, 08:09:26 PM »
I will try to remember to look at this tomorrow morning. I don’t know if the LED will show on the screen or not. You may want to check the output and see if it is on. I say this because the G63/G63 commands are done nothing like the normal outputs. The special M commands put output data in the movement buffer being sent to the motion controller. The normal outputs use the messaging system. So long story short is the plugin may not be telling us that they activated the output....  I can see this as a very easy thing to miss ! 

Please check it with a meter on the output.

Thanks Brian
Fixing problems one post at a time ;)

www.newfangledsolutions.com
www.machsupport.com
Re: M62/63 Command issue
« Reply #3 on: December 28, 2020, 07:54:00 AM »
I will try to remember to look at this tomorrow morning. I don’t know if the LED will show on the screen or not. You may want to check the output and see if it is on. I say this because the G63/G63 commands are done nothing like the normal outputs. The special M commands put output data in the movement buffer being sent to the motion controller. The normal outputs use the messaging system. So long story short is the plugin may not be telling us that they activated the output....  I can see this as a very easy thing to miss ! 

Please check it with a meter on the output.

Thanks Brian

Thanks Brian,

I should have put a meter on it. I was relying on the LED indicator. I will check tomorrow when I am home and let you know the out come.

Thank you for the response and help. 
Re: M62/63 Command issue
« Reply #4 on: December 28, 2020, 08:30:00 AM »
Rob is working remote and is going to test it this morning :)
Fixing problems one post at a time ;)

www.newfangledsolutions.com
www.machsupport.com

Offline Rob G

*
  •  14 14
    • View Profile
Re: M62/63 Command issue
« Reply #5 on: December 29, 2020, 07:32:46 AM »
I finished up testing on this issue yesterday and have sent my results to Polabs.  m64 and m65 are working as they should.  Unlike m62 and m63 that sync with motion to turn outputs on and off, m64 and m65 are immediate on/off.

It appears that Pokeys is not sending confirmation of movement.  I would suspect this will be resolved very quick.  I will post Pokeys information / fixes here on the matter.

Rob G

Re: M62/63 Command issue
« Reply #6 on: December 29, 2020, 07:59:53 AM »
I finished up testing on this issue yesterday and have sent my results to Polabs.  m64 and m65 are working as they should.  Unlike m62 and m63 that sync with motion to turn outputs on and off, m64 and m65 are immediate on/off.

It appears that Pokeys is not sending confirmation of movement.  I would suspect this will be resolved very quick.  I will post Pokeys information / fixes here on the matter.

Rob G

Thank You for all your help.
Re: M62/63 Command issue
« Reply #7 on: January 02, 2021, 05:58:34 PM »
I finished up testing on this issue yesterday and have sent my results to Polabs.  m64 and m65 are working as they should.  Unlike m62 and m63 that sync with motion to turn outputs on and off, m64 and m65 are immediate on/off.

It appears that Pokeys is not sending confirmation of movement.  I would suspect this will be resolved very quick.  I will post Pokeys information / fixes here on the matter.

Rob G

Rob have you had any response from pokeys yet on this issue? They did message me and said they where in contact with you on the issue.

Offline Rob G

*
  •  14 14
    • View Profile
Re: M62/63 Command issue
« Reply #8 on: January 04, 2021, 12:20:54 PM »
There are a couple of key items for making this all work with PoKeys 57 CNC

One, On the pulse engine page of their plug in, there will be  a check box for enabling outputs with M62 and M63.  This should be checked.

Second, Pokeys limits these outputs to 4.  They are the OC outputs.  when mapping these in Mac4, you can map them to any output you would like, but in the device list you will choose Pokeys_*********x PE.  Then all of the four OC outputs will show up in the Output Name drop down menu.  Once these are mapped when M62 Px, or M63 Px are called from a G code file there will be leds on the pokeys that are associated with the outputs 1-4  and will toggle when they are active.

I mapped output #3 in Mach outputs to PoKeys OC output 1.

I executed this G code file and OC output 1  is working as expected.  I then tested outputs 2-4 as well.

M62 P3
G0 X.1 F1.0
M63 P3
G0 X0
M99

Please let me know if this works in your configuration.
I have also attached a link for the most current PoKeys firmware as well.

https://www.dropbox.com/t/z6LEZqujDCXhfnkq
Re: M62/63 Command issue
« Reply #9 on: January 04, 2021, 02:48:34 PM »
There are a couple of key items for making this all work with PoKeys 57 CNC

One, On the pulse engine page of their plug in, there will be  a check box for enabling outputs with M62 and M63.  This should be checked.

Second, Pokeys limits these outputs to 4.  They are the OC outputs.  when mapping these in Mac4, you can map them to any output you would like, but in the device list you will choose Pokeys_*********x PE.  Then all of the four OC outputs will show up in the Output Name drop down menu.  Once these are mapped when M62 Px, or M63 Px are called from a G code file there will be leds on the pokeys that are associated with the outputs 1-4  and will toggle when they are active.

I mapped output #3 in Mach outputs to PoKeys OC output 1.

I executed this G code file and OC output 1  is working as expected.  I then tested outputs 2-4 as well.

M62 P3
G0 X.1 F1.0
M63 P3
G0 X0
M99

Please let me know if this works in your configuration.
I have also attached a link for the most current PoKeys firmware as well.

https://www.dropbox.com/t/z6LEZqujDCXhfnkq

I have also done some more testing. When using this test G-Code with M64/M65. I have config MACH 4 to Output#1 mapping to OC1

M64 P1
G01 X.5
M63 P1
G01 X0

This will activate the LED indicator under MACH 4 Machine Diagnostics Output#1 and will also Activate the LED light on the Pokeys control board OC1 . I have monitored the output of OC1 with and oscilloscope and it dose activate. I also was able to trigger the laser. So it seem to function correctly.

When I simple switch the test G-code to M62/M63 the following happens.

M62 P1
G01 X.5
M63 P1
G01 x5

I get no LED indicator in MACH 4 Machine Diagnostics Output #1. The LED OC1 on the Pokeys Control Board will activate but I have no signal output that will register on the oscilloscope and the Laser will not activate.

I have followed the same test as you have indicated to do and this is my results.

1.   I have the box check in the pulse engine to use M62/63 and it has been checked from the begin.
2.   I have the latest Firmware updates 4.4.19
3.   I fixed IP Address issue
4.   I configured Output #3 to OC output #1
5.   I run the following test G code

M62 P3
G01 X.5
M63 P3
G01 X5
M99

The results are no LED indication activation under MACH 4 Machine Diagnostic. I do get a OC1 LED light activation on Pokeys Control Board but no activation on the laser or oscilloscope.
When I run the following M64/M65 test G code.

M64 P3
G01 x.5
M65 P3
G01 x0
M99

The LED indicator activates under MACH 4 Machine Diagnostic Output# 3 and OC4 LED is activated on Pokeys Controller but not OC1 like it should. I put an oscilloscope on both OC 1 and OC 4 and neither generate a signal or activate the laser.

I almost feel there is something wrong with the board at this point.

Thanks Jimmy