Machsupport Forum
Mach Discussion => Mach4 General Discussion => Topic started by: lerska83 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.
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!
-
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.
-
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
-
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.
-
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.
-
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)
-
We are using the latest dev version, but are not aware of the touchoff module. We will check it out.
-
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
-
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.
-
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.
-
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.
Thanks, going to try this evening.
-
installed latest 3124, latest firmware 4.2.5 and latest plugin, but still struggling with probing. not sure if it's mach4 issue or not. on the "touch off" module, when I click on the button to find Z, it goes down, touches and retracts as expected. Do it again, then as soon as it touches the plate, it stops dead with error" Cannot transition from MDI to Stop" and disables the pulse engine. When I enable again, click on find Z again, it keeps on feeding down, driving into the touch plate (even when it says probe input is Active) ... just too unpredictable.
I am just going to go creating my own button with an auto z script.
-
Mongoose
Well I do not use the same motion controller as you but the common thing is 3124 Mach ( note I use a ESS with C25 )
I have exactly the same problems the probing Mach4 tab is so flaky its unreal tried to calibrate the probe in Z it did its bob about then drove the probe though a piece of 12 mm MDF I was using ( because I don't trust it ) the probe survived
Some times it goes up to find the surface sometimes down , I have put this down to the probe being to high
The other oddity is that no matter what tool number I have assigned to the probe it uses offset 101
The touch module that you have trouble with is better the TLO touch off is OK measurement is , I don't know what its measuring , there is nowhere in both probing section to input the gauge line lenght of the probe
OK before I am shot down I do Know its a DEV build and is not meant to be used in anger but surly any feed back the team ( or one man ) gets is useful
One last gripe can Newfangled software please keep the manual in step with the current build and screen sets , a brief change log for the dev builds would be great
Sorry for the none constructive post
But that probing screen set has been around for a while it should work or at least give us the paying customers a manual on how to use it , you never know it may well work if used correctly
Stuart
-
Hi Stuart,
Same here, probing screen is unusable for me or I just don't know how to use it :). I mainly only the use an auto z zero probe, so created a button on the main screen with a script found somewhere on this forum as the new "touch" module also does not work for me.
Anyway, the script works for me, so I am happy just to use that for now.
-
Hi guys,
I have still problems with the probe function in Mach4
When I click on the measure button I get the error message "ERROR: No contact with probe"
When I click on the measure button with the probe grounded I get the error message "ERROR: Probe obstructed"
The Probe light in the Machine Diagnostics is working OK, and lights up when I ground the probe.
I am using the latest versions of mach 4.2.0.3233 and Pokeys 8.13.0.3206 mach4 plugin and Pokeys firmware 4.2.13.
For now I use a modified script found on this forum, but I want to use the standaard advanced mach4 probe functions.
Here is the script I am using now.
local ToolSetter = scr.GetProperty("droprobhighvalue", "Value")
local tool_diameter = scr.GetProperty("droSurfZPos", "Value")
mc.mcCntlGcodeExecuteWait(0,"G91 G31 Z-15 F250") -- change feedrate and depth to suit
mc.mcCntlGcodeExecuteWait(0,"G91 Z2 F500") -- change feedrate and retract to suit
mc.mcCntlGcodeExecuteWait(0,"G91 G31 Z-3 F10") -- change feedrate to suit
mc.mcAxisSetPos(0, mc.Z_AXIS, (ToolSetter - tool_diameter)) -- set dro to height of toolsetter
mc.mcCntlGcodeExecuteWait(0,"G91 Z5 F500") -- change feedrate and retract to suit, use this Z rectract value for line 7
wx.wxMessageBox("Remove ToolSetter") -- remove if needed
mc.mcCntlGcodeExecuteWait(0,"G90 Z0 F250") -- move tool to zero, change feedrate to suit
Did anyone solve this issue?
Regards,
Thom
-
You might find this helpful.
http://www.machsupport.com/forum/index.php/topic,33691.msg234024.html#msg234024
-
Thanks for your response!
But the youtube video link didn't work in that topic.
Regards,
Thom
-
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.
NeoTO - could you please clarify this for me?
In the pokeys57CNC manual (26.9.2016) it states that "On PoKeys57CNC v1.0, v1.1 and v1.2 external pull-up resistor must
be used", but here you state the v1.2 does not require it.
I have a NC 3D touch probe setup on a v1.2 with no pull up resistor, and it appears to be working fine in the limited testing I have done... I am however concerned that I may run into issues at some point if I am not connected correctly.
Could you please let me know which is correct - your statement here or the statement in the manual?
Thanks!
Adrian
-
Hi, Adrian
The revision v1.2 should already have the pull-up on the probe input installed. However, this still needs some additional tests and until these are confirmed, we suggest adding an additional external pull-up.
-
Hi guys,
I have still problems with the probe function in Mach4
When I click on the measure button I get the error message "ERROR: No contact with probe"
When I click on the measure button with the probe grounded I get the error message "ERROR: Probe obstructed"
Did anyone solve this issue?
Regards,
Thom
Thom,
I know this thread is pretty old by now, but I messed around again today, downloaded latest Mach4 and latest plugin, but still can't use the "Touch" function in Mach4 :-(
Sometimes it would work, sometimes it drives through the plate (which luckily I keep in the air) and sometimes I get "Can't transition from RUNNING MDI to STOP" or something similar to those lines.
Just too unreliable, so I also use the same script you use at the moment and also created similar ones to probe X and Y.
It is a real shame the builtin Touch function is unusable, at least for us with Pokeys controllers.
-
There is still huge problems with probing. So this issue is not fixed
-
I have been having some mails with Polabs lately, and we might have found the problem with probing and the fix for it.
Anyone else here getting "Probe interrupted" as the probe doesnt work ?
-
I have been having some mails with Polabs lately, and we might have found the problem with probing and the fix for it.
Anyone else here getting "Probe interrupted" as the probe doesnt work ?
Yes I am getting still that error.... Though G code probing works somewhat at least and been using that "temporarily" until the probing gets fixed.
-
Ohh though I have not tried latest version of plugin :D have to test it later when I got time
-
I want to confirm the v1.3 board does NOT need the external pull-up?
-
Hi guys, I have exact issue with the probe as you have. Is this a Pockeys57CNC issue? Is there any update on this?
-
I had the same problem. Turns out that Pin 19 has no input filtering so sometimes it triggers too early especially if you use a mechanical sensor. Mach 4's touch UI checks the state of Pin 19 after each G31 move and throws an error if it is inconsistent. To fix the issue you need to add a RC filter between the probe sensor and Pin 19.
-
RC filter? You talking about an inline coil, or a choke around the wire?
-
RC Filter -> Resistor + Capacitor
This is what I did: (https://i.imgur.com/kWZ1Fw7.jpg)
The red area is the RC filter and the rest is an inverter (N-Channel Mosfet) because @NeoTO said using it with the invert option and also forcing a cleaner on/off state.
I selected the values by choosing an R (500) significantly lower than the Pullup (10k). Based on that I choose a time constant of 10ms and calculated 20µF for C. I didn't measure with the scope, I just pulled the 10ms out of thin air, they might be one or two orders of magnitude to large.
But that doesn't matter because I am probing at 50mm/min, the 10ms will lead to 8µm offset, which stays constant and can be included into the calibration.
-
Excellent. I will try that. I get so tired of MACH4 complaining about the input.
-
Another solution would be removing the sanity check in mcTouchOff.lua. Replace the function CheckProbe(state) with:
function CheckProbe(state)
wx.wxMilliSleep(20)
return true;
end
But that is dangerous and might lead to errors, even crashes.
-
I run it just with a 10k pullup resistor and works fine... with mach4 and tried it with auggie worked ok but probing in auggie isn't 100% done yet but getting there I have been working with art on it and looks like a few more weeks maybe..
It also works with mach3 but for some reason the probe on screen led seems to flash but still seems to trigger ok...
gary
-
Unless you have an older board (v1.0 or v1.2) you don't need a pullup resistor. I tried one with my v1.3 board and it makes no difference. I'm hoping the filter will do a better job. In theory, it should.
-
I think my board is ver 1.2 and I don't need it, it works both ways.. I just made a board just to make things easier for me has all 8 motor ribbon cables to it and I used screw connectors to drivers also have the probe on it with switch for 10k or not, and have 6 screw connectors for home limit and the pokeys ribbon and Schmitt triggers, been testing about a week so far so good used just grounding switches. optic sensors. also the cheep 3d printer positive logic optic switches and all worked. may add more to board don't know only going with what I may need or want...
gary