Hello Guest it is January 29, 2020, 11:48:33 AM

Author Topic: Pokeys57CNC and probing  (Read 8722 times)

0 Members and 1 Guest are viewing this topic.

Pokeys57CNC and probing
« on: June 29, 2016, 02:49:16 PM »
Hi

I have been running succesfully pokeys57cnc controller to drive my cnc router, but now that i have been trying to get probing to work i have seriously "hit a wall". Whatever settings i have tried it says either no contact with probe or that probe is obstructed. When i check the machine diagnostics and pokeys own input diagnostig it seems work well and in mach it shows that probe input gets activated when i close the switch (i am using NO switch to test the probing function). I took log of what is happening and will past it here so if anyone can help me to find out what is causing this error.

Code: [Select]
2016-06-29 18:48:54.528 - API: mcCntlEnable(true) called.
2016-06-29 18:48:54.530 - Signal id 1018, (Enable #0), changed from LOW to HIGH.
2016-06-29 18:48:54.541 - Signal id 1019, (Enable #1), changed from LOW to HIGH.
2016-06-29 18:48:54.548 - [PoKeys] Axis enabled changed 1

2016-06-29 18:48:54.552 - Signal id 1020, (Enable #2), changed from LOW to HIGH.
2016-06-29 18:48:54.564 - [PoKeys] Updating enable output signals
2016-06-29 18:48:54.569 - Signal id 1021, (Enable #3), changed from LOW to HIGH.
2016-06-29 18:48:54.583 - [PoKeys] Axis enabled changed 7

2016-06-29 18:48:54.586 - Signal id 1120, (Machine Enabled), changed from LOW to HIGH.
2016-06-29 18:48:54.596 - [PoKeys] Updating enable output signals
2016-06-29 18:48:54.612 - [PoKeys] Axis enabled changed 15

2016-06-29 18:48:54.627 - [PoKeys] Updating enable output signals
2016-06-29 18:48:54.640 - [PoKeys] PoKeys Pulse engine enabled
2016-06-29 18:48:54.652 - [PoKeys] Enabling motion - Buffer with 0 moves is being cleared!
2016-06-29 18:48:54.668 - [PoKeys] Updating motion parameters in device
2016-06-29 18:48:54.706 - All motors marked as still.
2016-06-29 18:48:54.707 - All motors marked as still.
2016-06-29 18:48:54.707 - All motors marked as still.
2016-06-29 18:48:54.707 - All motors marked as still.
2016-06-29 18:48:54.708 - All motors marked as still.
2016-06-29 18:48:54.708 - All motors marked as still.
2016-06-29 18:48:54.708 - All motors marked as still.
2016-06-29 18:48:54.709 - All motors marked as still.
2016-06-29 18:48:54.710 - API: mcMotionSync() called.
2016-06-29 18:48:54.710 - SyncPosition()! Clearing planner.
2016-06-29 18:48:54.710 - [PoKeys] Switching to RUNNING state...
2016-06-29 18:48:59.644 - API: mcCntlGcodeExecuteWait() called. (G0 G90 G40 G80)
2016-06-29 18:48:59.848 - Attempt transition from "Idle" on event "MDI Start" Controller.cpp:1961
2016-06-29 18:48:59.849 - S_IDLE_on_exit
2016-06-29 18:48:59.849 - MACH_STATE_start_mdi
2016-06-29 18:48:59.849 - S_MDI_RUNNING_on_entry
2016-06-29 18:48:59.849 - S_MDI_RUNNING2_on_entry
2016-06-29 18:48:59.851 - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2016-06-29 18:48:59.966 - Attempt transition from "MDI Running" on event "Stop" GcodeExec.cpp:943
2016-06-29 18:48:59.966 - S_MDI_RUNNING2_on_exit
2016-06-29 18:48:59.966 - Signal id 1114, (Gcode Running), changed from HIGH to LOW.
2016-06-29 18:48:59.967 - S_MDI_RUNNING_on_exit
2016-06-29 18:48:59.967 - MACH_STATE_stop
2016-06-29 18:49:00.035 - S_IDLE_on_entry
2016-06-29 18:49:00.036 - API: mcCntlGcodeExecuteWait() called. (G43 H1)
2016-06-29 18:49:00.241 - Attempt transition from "Idle" on event "MDI Start" Controller.cpp:1961
2016-06-29 18:49:00.241 - S_IDLE_on_exit
2016-06-29 18:49:00.241 - MACH_STATE_start_mdi
2016-06-29 18:49:00.241 - S_MDI_RUNNING_on_entry
2016-06-29 18:49:00.241 - S_MDI_RUNNING2_on_entry
2016-06-29 18:49:00.242 - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2016-06-29 18:49:00.362 - Attempt transition from "MDI Running" on event "Stop" GcodeExec.cpp:943
2016-06-29 18:49:00.362 - S_MDI_RUNNING2_on_exit
2016-06-29 18:49:00.362 - Signal id 1114, (Gcode Running), changed from HIGH to LOW.
2016-06-29 18:49:00.363 - S_MDI_RUNNING_on_exit
2016-06-29 18:49:00.363 - MACH_STATE_stop
2016-06-29 18:49:00.426 - S_IDLE_on_entry
2016-06-29 18:49:00.428 - API: mcCntlGcodeExecuteWait() called. (G31,0 Z-50,5000 F50,0)
2016-06-29 18:49:00.632 - Attempt transition from "Idle" on event "MDI Start" Controller.cpp:1961
2016-06-29 18:49:00.632 - S_IDLE_on_exit
2016-06-29 18:49:00.632 - MACH_STATE_start_mdi
2016-06-29 18:49:00.632 - S_MDI_RUNNING_on_entry
2016-06-29 18:49:00.633 - S_MDI_RUNNING2_on_entry
2016-06-29 18:49:00.634 - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2016-06-29 18:49:00.649 - Attempt transition from "MDI Running" on event "Stop" GcodeExec.cpp:994
2016-06-29 18:49:00.649 - S_MDI_RUNNING2_on_exit
2016-06-29 18:49:00.649 - Signal id 1114, (Gcode Running), changed from HIGH to LOW.
2016-06-29 18:49:00.650 - S_MDI_RUNNING_on_exit
2016-06-29 18:49:00.650 - MACH_STATE_stop
2016-06-29 18:49:00.712 - S_IDLE_on_entry
2016-06-29 18:49:00.714 - API: mcCntlEStop() called.
2016-06-29 18:49:00.715 - API: mcCntlEnable(false) called.
2016-06-29 18:49:00.718 - Signal id 1018, (Enable #0), changed from HIGH to LOW.
2016-06-29 18:49:00.733 - Signal id 1019, (Enable #1), changed from HIGH to LOW.
2016-06-29 18:49:00.735 - [PoKeys] Axis enabled changed 14

2016-06-29 18:49:00.744 - Signal id 1020, (Enable #2), changed from HIGH to LOW.
2016-06-29 18:49:00.751 - [PoKeys] Updating enable output signals
2016-06-29 18:49:00.761 - Signal id 1021, (Enable #3), changed from HIGH to LOW.
2016-06-29 18:49:00.779 - [PoKeys] Axis enabled changed 8

2016-06-29 18:49:00.781 - Signal id 1120, (Machine Enabled), changed from HIGH to LOW.
2016-06-29 18:49:00.789 - [PoKeys] Updating enable output signals
2016-06-29 18:49:00.818 - [PoKeys] Axis enabled changed 0

2016-06-29 18:49:00.834 - [PoKeys] Updating enable output signals
2016-06-29 18:49:00.850 - [PoKeys] PoKeys Pulse engine disabled
2016-06-29 18:49:00.864 - [PoKeys] Disabling motion - Buffer with 0 moves is being cleared!
Re: Pokeys57CNC and probing
« Reply #1 on: July 12, 2016, 08:29:53 AM »
i get the same with my pokeys ... just does not work .. although sometimes it does, you just never know. i only really need auto z for the machining I do, so made my own button with a script I found on the forum. the new touch module in the pre-release also does not work properly .. at least for me.

Offline NeoTO

*
  •  504 504
    • View Profile
    • PoLabs
Re: Pokeys57CNC and probing
« Reply #2 on: July 21, 2016, 11:54:17 AM »
Hi, guys

We haven't been checking the Mach4-related forums...

Can you please let us know which Mach4 plugin version you have been having problems with probing? We fix some early bugs a while ago and are eager to know whether anybody is still having issues with it.

* early PoKeys57CNC boards (v1.0 and v1.1) required an external pull-up resistor to be added to the probing input due to a hardware bug.
* pin 17 should be selected as probing input with invert option enabled. This should also work with simple contact-based probes.

Regards,
Matevž, PoLabs
www.poscope.com home of PoKeys USB HID, IO, USB, Ethernet controler and PoScope USB PC oscilloscope
Re: Pokeys57CNC and probing
« Reply #3 on: July 21, 2016, 12:00:24 PM »
Hi, guys

We haven't been checking the Mach4-related forums...

Can you please let us know which Mach4 plugin version you have been having problems with probing? We fix some early bugs a while ago and are eager to know whether anybody is still having issues with it.

* early PoKeys57CNC boards (v1.0 and v1.1) required an external pull-up resistor to be added to the probing input due to a hardware bug.
* pin 17 should be selected as probing input with invert option enabled. This should also work with simple contact-based probes.

Regards,
Matevž, PoLabs

So we do not need an external pull-up with v1.2 boards ? Will it make any difference if I have a pull-up on the v1.2 board ?

I am not 100% sure if it is Mach4 or Pokeys .. probe is connected to pin 17 and whenever I touch the touchplate, the "probe led" in Mach4 lights up. I created my own script for my z-zero touch probe and it seems to work consistently, it's just the new touch module in mach4 that seems to have some issues.

before i tested, I did download the latest dev build of Mach4 and the latest mach4 plugin as well.

Offline NeoTO

*
  •  504 504
    • View Profile
    • PoLabs
Re: Pokeys57CNC and probing
« Reply #4 on: July 21, 2016, 12:08:34 PM »
The external pull-up on v1.2 boards is not required.

Are you able to replicate the issue with probing? We are testing it now and can't make it fail.
www.poscope.com home of PoKeys USB HID, IO, USB, Ethernet controler and PoScope USB PC oscilloscope
Re: Pokeys57CNC and probing
« Reply #5 on: July 21, 2016, 12:11:12 PM »
The external pull-up on v1.2 boards is not required.

Are you able to replicate the issue with probing? We are testing it now and can't make it fail.

Thanks, i wonder if my pull-up is then causing issues ?

Also, are you using the touchoff module in the latest mach4 dev build available here ? (http://www.machsupport.com/forum/index.php/topic,27039.msg227697.html#msg227697)

Offline NeoTO

*
  •  504 504
    • View Profile
    • PoLabs
Re: Pokeys57CNC and probing
« Reply #6 on: July 21, 2016, 01:32:06 PM »
We are using the latest dev version, but are not aware of the touchoff module. We will check it out.
www.poscope.com home of PoKeys USB HID, IO, USB, Ethernet controler and PoScope USB PC oscilloscope

Offline Stuart

*
  •  204 204
    • View Profile
Re: Pokeys57CNC and probing
« Reply #7 on: July 21, 2016, 02:21:56 PM »
The external pull-up on v1.2 boards is not required.

Are you able to replicate the issue with probing? We are testing it now and can't make it fail.

Thanks, i wonder if my pull-up is then causing issues ?

Also, are you using the touchoff module in the latest mach4 dev build available here ? (http://www.machsupport.com/forum/index.php/topic,27039.msg227697.html#msg227697)

I have tried that module and I find it very iffy my be the way I use it but its not intuitive and has been changed in the beta 3116 it smashed a hamier tip I use in my home made probe , yes its beta for a good reason , caveat emptor

Stuart

ESS and C25

Offline NeoTO

*
  •  504 504
    • View Profile
    • PoLabs
Re: Pokeys57CNC and probing
« Reply #8 on: July 21, 2016, 11:56:35 PM »
Hi, guys

We haven't been checking the Mach4-related forums...

Can you please let us know which Mach4 plugin version you have been having problems with probing? We fix some early bugs a while ago and are eager to know whether anybody is still having issues with it.

* early PoKeys57CNC boards (v1.0 and v1.1) required an external pull-up resistor to be added to the probing input due to a hardware bug.
* pin 17 should be selected as probing input with invert option enabled. This should also work with simple contact-based probes.

Regards,
Matevž, PoLabs

There was a typing error - pin 19 should be used for probing, as described in the manual and pinouts.
www.poscope.com home of PoKeys USB HID, IO, USB, Ethernet controler and PoScope USB PC oscilloscope

Offline NeoTO

*
  •  504 504
    • View Profile
    • PoLabs
Re: Pokeys57CNC and probing
« Reply #9 on: July 22, 2016, 12:15:17 AM »
Update: we have been using 3112, which is the latest dev version with SDK, but have now tested 3124 also.

If you experience any problems with probing, I suggest upgrading the firmware to the latest 4.2.5 version and execute 'Device > Clear settings in device' from PoKeys configuration application to restore the device to factory defaults. Except for the IP address configuration and PoNET (kbd48CNC) devices discovery, all Mach4-related settings should be automatically be configured by the plugin on the first start.
www.poscope.com home of PoKeys USB HID, IO, USB, Ethernet controler and PoScope USB PC oscilloscope