Work with probe
14 Sep 2020 13:51 #182082
by RayJr
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Replied by RayJr on topic Work with probe
It was the INI from ebartel that had the duplicated [RS274NGC] section.
Ray
Ray
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Please Log in or Create an account to join the conversation.
26 Sep 2020 18:39 #183866
by RayJr
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Replied by RayJr on topic Work with probe
Harvey, did you ever get a reply to your jog issue?
Are you using the version of probe screen for version 2.8?
Ray
Are you using the version of probe screen for version 2.8?
Ray
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Please Log in or Create an account to join the conversation.
26 Sep 2020 23:16 #183900
by RayJr
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Replied by RayJr on topic Work with probe
I am working on getting Probe Screen V2 (with mods for LCNC 2.8 or master) on my knee mill.
I am running on master (2.9.0-pre0-2806).
I have checked most of the probe routines are working, but the manual tool change is not.
when I issued an m6 t1, the machine moves to the change position and stops. Then nothing. I can see that the run button on the GUI is depressed, so something is going on. There is nothing indication any error in the terminal that LCNC is running in.
(I also checked for a hidden dialog box)
I have tried this with remap in the probe screen both checked & unchecked, with the same result.
A few taps on the escape key will get it out of this hang-up.
have a few R8 tool holders, so I am looking to get the tool change working the way it was before I added the Probe_Screen system.
But eventually I will want it to work along with the tool length check (remap enabled) mode.
So it has me thinking that the m6 remap is lost somewhere.
Any tips would be appreciated!
Ray
I am running on master (2.9.0-pre0-2806).
I have checked most of the probe routines are working, but the manual tool change is not.
when I issued an m6 t1, the machine moves to the change position and stops. Then nothing. I can see that the run button on the GUI is depressed, so something is going on. There is nothing indication any error in the terminal that LCNC is running in.
(I also checked for a hidden dialog box)
I have tried this with remap in the probe screen both checked & unchecked, with the same result.
A few taps on the escape key will get it out of this hang-up.
have a few R8 tool holders, so I am looking to get the tool change working the way it was before I added the Probe_Screen system.
But eventually I will want it to work along with the tool length check (remap enabled) mode.
So it has me thinking that the m6 remap is lost somewhere.
Any tips would be appreciated!
Ray
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Please Log in or Create an account to join the conversation.
27 Sep 2020 08:36 #183943
by harvey
Replied by harvey on topic Work with probe
@RayJr
No I got no reply. I used the probe screen V2 from Github.
Because i have no time I gave it up to test.
No I got no reply. I used the probe screen V2 from Github.
Because i have no time I gave it up to test.
Please Log in or Create an account to join the conversation.
27 Sep 2020 17:18 - 28 Sep 2020 05:25 #184009
by RayJr
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Replied by RayJr on topic Work with probe
OK then.
Look in the probe_screen.py file, on or around line 383 for a line that starts with "velocity."
If is is "velocity = int(self.inifile.find("TRAJ", "DEFAULT_VELOCITY"))", change int to float, save and try again.
I think the change was made for metric machines, but makes no sense for inch machines.
Ray
Look in the probe_screen.py file, on or around line 383 for a line that starts with "velocity."
If is is "velocity = int(self.inifile.find("TRAJ", "DEFAULT_VELOCITY"))", change int to float, save and try again.
I think the change was made for metric machines, but makes no sense for inch machines.
Ray
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Last edit: 28 Sep 2020 05:25 by RayJr.
Please Log in or Create an account to join the conversation.
28 Sep 2020 06:11 #184110
by harvey
Replied by harvey on topic Work with probe
Hi Ray
I have an metric machine but if i have time i will test it then i will report
I have an metric machine but if i have time i will test it then i will report
Please Log in or Create an account to join the conversation.
28 Sep 2020 14:05 #184171
by RayJr
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Replied by RayJr on topic Work with probe
If you don't want to change the probe_screen.py file, you can get around the issue by entering integers in all of the velocity settings.
Ray
Ray
"No problem can be solved from the same level of consciousness that created it"
Albert Einstein
Please Log in or Create an account to join the conversation.
30 Sep 2020 09:36 #184368
by harvey
Replied by harvey on topic Work with probe
Hi Ray
Now I tried it with linuxcnc 3.8
This is the error message i got with float-entry
Traceback (most recent call last):
File "python/probe_screen.py", line 383, in on_btn_jog_pressed
velocity = float(self.inifile.find("TRAJ", "DEFAULT_VELOCITY"))
TypeError: float() argument must be a string or a number
Traceback (most recent call last):
I give it up I will write my own routines. So I could learn a little bit python.
Now I tried it with linuxcnc 3.8
This is the error message i got with float-entry
Traceback (most recent call last):
File "python/probe_screen.py", line 383, in on_btn_jog_pressed
velocity = float(self.inifile.find("TRAJ", "DEFAULT_VELOCITY"))
TypeError: float() argument must be a string or a number
Traceback (most recent call last):
I give it up I will write my own routines. So I could learn a little bit python.
Please Log in or Create an account to join the conversation.
13 Oct 2020 05:10 #185919
by Mokuleia
Replied by Mokuleia on topic Work with probe
Hi everyone. I am experiencing some issues with running Probe Screen V2 (PSV2) in Gmoccapy 3. Basically, the PSV2 tab is not showing anywhere, although I can see it in Axis when changing DISPLAY from Gmoccapy to Axis in my .ini file. I looked a bit at some of the python scripts and found the following command line in probe_screen.py: def get_display(self): #gmoccapy or axis ? temp = self.inifile.find("DISPLAY", "DISPLAY"), so I presume changing the display from Axis to Gmoccapy should in theory work (or at least it appears that PSV2 developers had that in mind). Did any of you were able to install PSV2 with Gmoccapy successfully? Any idea where to look and what to change to make it work? Thanks
Please Log in or Create an account to join the conversation.
21 Oct 2020 21:40 #186847
by depronman
Replied by depronman on topic Work with probe
Hi I have this working perfectly in LinuxCNC V2.8.0 using Gmoccapy GUI
Please Log in or Create an account to join the conversation.
Time to create page: 0.257 seconds