Work with probe
24 Feb 2019 16:41 #127061
by pl7i92
Replied by pl7i92 on topic Work with probe
I added a Probe Video of the Dececed member Here on YT
to show on non metal part Tool change with copper plate in Gcode
to show on non metal part Tool change with copper plate in Gcode
Please Log in or Create an account to join the conversation.
08 Mar 2019 00:35 #128046
by tony978
Replied by tony978 on topic Work with probe
can someone do a sanity check on my .ini my RS274NGC maybe wrong getting error
"Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/realtime-3.4-9-rtai-686-pae/modules/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.5
LINUXCNC - 2.7.14
Machine configuration directory is '/home/tony/linuxcnc/configs/my-mill'
Machine configuration file is 'my-mill.ini'
INIFILE=/home/tony/linuxcnc/configs/my-mill/my-mill.ini
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./my-mill.hal
Found file(REL): ./custom.hal
Starting TASK program: milltask
Starting DISPLAY program: axis
emc/task/emctask.cc 389: interp_error: File not open
File not open
emc/task/emctaskmain.cc 3017: can't initialize interpreter
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
Shutting down and cleaning up LinuxCNC...
Killing task linuxcncsvr, PID=7136
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Debug file information:
.
NGC file not found: ngc=manual_change - 74:REMAP = M6 modalgroup=6 prolog=change_prolog ngc=manual_change epilog=change_epilog
A configuration error is preventing LinuxCNC from starting.
More information may be available when running from a terminal.
7136
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
"Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/realtime-3.4-9-rtai-686-pae/modules/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.5
LINUXCNC - 2.7.14
Machine configuration directory is '/home/tony/linuxcnc/configs/my-mill'
Machine configuration file is 'my-mill.ini'
INIFILE=/home/tony/linuxcnc/configs/my-mill/my-mill.ini
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./my-mill.hal
Found file(REL): ./custom.hal
Starting TASK program: milltask
Starting DISPLAY program: axis
emc/task/emctask.cc 389: interp_error: File not open
File not open
emc/task/emctaskmain.cc 3017: can't initialize interpreter
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
Shutting down and cleaning up LinuxCNC...
Killing task linuxcncsvr, PID=7136
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Debug file information:
.
NGC file not found: ngc=manual_change - 74:REMAP = M6 modalgroup=6 prolog=change_prolog ngc=manual_change epilog=change_epilog
A configuration error is preventing LinuxCNC from starting.
More information may be available when running from a terminal.
7136
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
Attachments:
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19190
- Thank you received: 6433
08 Mar 2019 00:52 #128048
by tommylight
Replied by tommylight on topic Work with probe
There is a file missing for the remap you are using. It has to be in the same folder where the config files are.Debug file information:
.
NGC file not found: ngc=manual_change - 74:REMAP = M6 modalgroup=6 prolog=change_prolog ngc=manual_change epilog=change_epilog
Please Log in or Create an account to join the conversation.
08 Mar 2019 01:10 #128051
by tony978
Replied by tony978 on topic Work with probe
Does v1 need to be installed before v2 ?
.axisrc needs to be in ./user or root ?
.axisrc needs to be in ./user or root ?
Please Log in or Create an account to join the conversation.
- franstrein
- Offline
- Junior Member
Less
More
- Posts: 29
- Thank you received: 2
08 Mar 2019 17:44 #128097
by franstrein
Replied by franstrein on topic Work with probe
I still run in the error I posted some weeks back. I tried to change the remap line to use ngc=change to test it, but that didn't help.
Is anyone happen any suggestions here?
Thanks a lot,
Frans
Is anyone happen any suggestions here?
Thanks a lot,
Frans
Hi,
As I mentioned in another thread, I added NativeCam and the Probe v2 functions to my gmoccapy 1.5.4 and Linux 2.7.14 setup.
Most things work very good.
The only issue is that when I try to execute a gcode file generated by my HSM Express CAM functions, I get an error:
In line 0 of the gcode file the pycall(remap.change_prolog) call fails
I expect this to be caused by the line
REMAP=M6 modalgroup=6 prolog=change_prolog ngc=manual_change epilog=change_epilog
in my INI file. I needed to add that for the probe screens to work, according to the instructions at
github.com/verser-git/probe_screen_v2
Is there a conflict with a similar mapping ??
Any suggestions?
Thanks,
Frans
Please Log in or Create an account to join the conversation.
08 Mar 2019 18:00 #128098
by andypugh
Replied by andypugh on topic Work with probe
That REMAP is for tool change. I can't see any reason you would need that for the probe screen.
What happens if you comment it out?
What happens if you comment it out?
Please Log in or Create an account to join the conversation.
09 Mar 2019 00:24 #128121
by tony978
Replied by tony978 on topic Work with probe
commenting it out works to get it to start , I'm getting a errpr eof in my loaded nc file
it is seaking o-word<down> from line 1 . so that mean a nc file with probe routines needs to be loaded for this screen to work ?
it is seaking o-word<down> from line 1 . so that mean a nc file with probe routines needs to be loaded for this screen to work ?
Please Log in or Create an account to join the conversation.
09 Mar 2019 09:57 - 09 Mar 2019 09:58 #128147
by Ferdl
Replied by Ferdl on topic Work with probe
Hi all,
I'm facing with one problem. The Probe Screen V2 can be loaded and it seams to work. But if I load a gcode it will not be displayed in the axis Preview.
If I remove the M6 command in the gcode the tool path will be displayed...
Any idea what can be wrong? I saw from some user they having the same problem...
By the way it is a great extension for linuxcnc.
Thanks
Ferdi
I'm facing with one problem. The Probe Screen V2 can be loaded and it seams to work. But if I load a gcode it will not be displayed in the axis Preview.
If I remove the M6 command in the gcode the tool path will be displayed...
Any idea what can be wrong? I saw from some user they having the same problem...
By the way it is a great extension for linuxcnc.
Thanks
Ferdi
Last edit: 09 Mar 2019 09:58 by Ferdl.
Please Log in or Create an account to join the conversation.
09 Mar 2019 11:41 #128155
by pl7i92
Replied by pl7i92 on topic Work with probe
the mauell toolchange is interfeard with the probescreen so M6 is inconsist at this moment they are working to solve this
be patiant within the next 14 days or so it may be fixed
be patiant within the next 14 days or so it may be fixed
Please Log in or Create an account to join the conversation.
09 Mar 2019 20:00 #128177
by vmihalca
Replied by vmihalca on topic Work with probe
I have done everything that was mentioned in the instructions (or at least that's what I think) and now I have an issue at tool change from MDI.
How should I do a tool change now that I have ProbeScreen, whose installation required me to comment the manual tool change in my hal file.
I am attaching a video below with all the settings that I've made and what's the current behavior.
If I've missed something, please let me know
How should I do a tool change now that I have ProbeScreen, whose installation required me to comment the manual tool change in my hal file.
I am attaching a video below with all the settings that I've made and what's the current behavior.
If I've missed something, please let me know
The following user(s) said Thank You: verser
Please Log in or Create an account to join the conversation.
Time to create page: 0.184 seconds