Work with probe
17 Mar 2016 02:00 #71759
by gizmo6023
Replied by gizmo6023 on topic Installing Work with probe
The only difference between the working and broken .ini files are the lines from Verser's install instructions.
broken ini:
# Generated by stepconf 1.1 at Mon Mar 14 19:49:20 2016
# If you make changes to this file, they will be
# overwritten when you run stepconf again
[EMC]
MACHINE = ShopFoxMill
DEBUG = 0
[DISPLAY]
DISPLAY = axis
EMBED_TAB_NAME=Probe Screen
EMBED_TAB_COMMAND=halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -u python/probe_screen.py -x {XID} probe_icons/probe_screen.glade
[RS274NGC]
FEATURES=30
SUBROUTINE_PATH = home/dave/linuxcnc/configs/subroutines
[TOOLSENSOR]
# Control probe rapid feed
RAPID_SPEED = 600
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
vs working .ini:
# Generated by stepconf 1.1 at Mon Mar 14 19:49:20 2016
# If you make changes to this file, they will be
# overwritten when you run stepconf again
[EMC]
MACHINE = ShopFoxMill
DEBUG = 0
[DISPLAY]
DISPLAY = axis
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
broken ini:
# Generated by stepconf 1.1 at Mon Mar 14 19:49:20 2016
# If you make changes to this file, they will be
# overwritten when you run stepconf again
[EMC]
MACHINE = ShopFoxMill
DEBUG = 0
[DISPLAY]
DISPLAY = axis
EMBED_TAB_NAME=Probe Screen
EMBED_TAB_COMMAND=halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -u python/probe_screen.py -x {XID} probe_icons/probe_screen.glade
[RS274NGC]
FEATURES=30
SUBROUTINE_PATH = home/dave/linuxcnc/configs/subroutines
[TOOLSENSOR]
# Control probe rapid feed
RAPID_SPEED = 600
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
vs working .ini:
# Generated by stepconf 1.1 at Mon Mar 14 19:49:20 2016
# If you make changes to this file, they will be
# overwritten when you run stepconf again
[EMC]
MACHINE = ShopFoxMill
DEBUG = 0
[DISPLAY]
DISPLAY = axis
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
Please Log in or Create an account to join the conversation.
17 Mar 2016 04:36 #71763
by verser
Replied by verser on topic Installing Work with probe
There is a syntax error.
To repair attach here your broken ini.
To repair attach here your broken ini.
Please Log in or Create an account to join the conversation.
17 Mar 2016 10:39 #71774
by andypugh
Replied by andypugh on topic Installing Work with probe
You have moved a number of INI entries from one section to another.
The actual error message is because the system isn't finding any entry at all called "MAX_FEED_OVERRIDE" in the [DISPLAY] section because you have moved it into the [TOOLSENSOR] section.
The actual error message is because the system isn't finding any entry at all called "MAX_FEED_OVERRIDE" in the [DISPLAY] section because you have moved it into the [TOOLSENSOR] section.
Please Log in or Create an account to join the conversation.
17 Mar 2016 12:05 #71777
by gizmo6023
Thank you for having a look at broken my file.
Replied by gizmo6023 on topic Installing Work with probe
There is a syntax error.
To repair attach here your broken ini.
Thank you for having a look at broken my file.
Please Log in or Create an account to join the conversation.
17 Mar 2016 12:48 #71783
by verser
2. Text from the .axisrc file do not need to put in the .ini file.
Replied by verser on topic Installing Work with probe
1. Error: .ini file sections are confused. INI Configuration .Thank you for having a look at broken my file.
2. Text from the .axisrc file do not need to put in the .ini file.
The following user(s) said Thank You: gizmo6023
Please Log in or Create an account to join the conversation.
17 Mar 2016 18:18 #71824
by gizmo6023
Replied by gizmo6023 on topic Installing Work with probe
Thank you for the assistance and the link.
I will read the whole Ini configuration instructions when I get home. Now that I can see the correct configuration it makes sense that LinuxCNC is having issues with my broken ini.
I will read the whole Ini configuration instructions when I get home. Now that I can see the correct configuration it makes sense that LinuxCNC is having issues with my broken ini.
Please Log in or Create an account to join the conversation.
18 Mar 2016 04:20 - 19 Mar 2016 17:52 #71846
by gizmo6023
Replied by gizmo6023 on topic Installing Work with probe
Thank you for the help Verser.
I now get the probe screen but also get an error 'NoneType' object has no attribute 'rfind'
I canceled the error and attempted to run the probing routine ( no probe installed to be safe) and get numerous "Unable to open file" errors . Pressing probe down generates no move and Error: Unable to open file <down>, pressing X- moves the spindle down and generates Error: Unable to open file <xminus>, pressing X-Y- out moves the table - and spindle down and generates Error: Unable to open file <xminus>
Seems the program gets lost before the last rapid move is called, just before the measurement routine should start.
I have attached my .ini .hal and output from dmesg and a couple of screen shots, perhaps this information will help diagnose the reason for this behavior.
I now get the probe screen but also get an error 'NoneType' object has no attribute 'rfind'
I canceled the error and attempted to run the probing routine ( no probe installed to be safe) and get numerous "Unable to open file" errors . Pressing probe down generates no move and Error: Unable to open file <down>, pressing X- moves the spindle down and generates Error: Unable to open file <xminus>, pressing X-Y- out moves the table - and spindle down and generates Error: Unable to open file <xminus>
Seems the program gets lost before the last rapid move is called, just before the measurement routine should start.
I have attached my .ini .hal and output from dmesg and a couple of screen shots, perhaps this information will help diagnose the reason for this behavior.
Last edit: 19 Mar 2016 17:52 by gizmo6023.
Please Log in or Create an account to join the conversation.
21 Mar 2016 13:27 #71983
by verser
Replied by verser on topic Installing Work with probe
Please show me the look of a full path to the down.ngc on your computer.Pressing probe down generates no move and Error: Unable to open file <down>
Please Log in or Create an account to join the conversation.
22 Mar 2016 00:03 #72001
by gizmo6023
Here is a screen capture showing the location of the down.ngc
If I am reading this file structure properly it is Home/dave/linuxcnc/configs/ShopFoxMill/subroutines
Second screen shot shows errors produced for pressing Y- X- Y+ X+ all produced a move of the head toward the table then an error.
Pressing probe down produces error with no head movement. Pressing cylinder produced head down table left moves then error.
Replied by gizmo6023 on topic Installing Work with probe
Please show me the look of a full path to the down.ngc on your computer.Pressing probe down generates no move and Error: Unable to open file <down>
Here is a screen capture showing the location of the down.ngc
If I am reading this file structure properly it is Home/dave/linuxcnc/configs/ShopFoxMill/subroutines
Second screen shot shows errors produced for pressing Y- X- Y+ X+ all produced a move of the head toward the table then an error.
Pressing probe down produces error with no head movement. Pressing cylinder produced head down table left moves then error.
Please Log in or Create an account to join the conversation.
22 Mar 2016 03:14 #72003
by gizmo6023
Replied by gizmo6023 on topic Installing Work with probe
I am not sure if this error is connected to the unable to open file down.ngc error but it only happens with the modified .ini for work with probe.
Please Log in or Create an account to join the conversation.
Time to create page: 0.133 seconds