Pathpilot 2.1.6 on VMWare
09 Feb 2019 14:58 #126058
by slipalong
Pathpilot 2.1.6 on VMWare was created by slipalong
Hi,
having a play with PathPilot in a view to using it on my mill instead of Axis. Have got it up and running in SIP mode, but cant seem to reference it and reset button is permanently blue.
I have hit reset and then the ref x,y,z as per the instruction but no joy.
Thanks,
Ian.
having a play with PathPilot in a view to using it on my mill instead of Axis. Have got it up and running in SIP mode, but cant seem to reference it and reset button is permanently blue.
I have hit reset and then the ref x,y,z as per the instruction but no joy.
Thanks,
Ian.
Please Log in or Create an account to join the conversation.
09 Feb 2019 15:31 #126059
by smgvbest
Replied by smgvbest on topic Pathpilot 2.1.6 on VMWare
Two things i can think of.
if you want to make PP aware of VMware. you can edit ~/tmc/python/vmcheck.py
after this block of code.add (Be sure to make sure the spacing is directly under the above line with same indentation
- Pathpilot is not configured to recognize VMWare as a virtualization machine. so it's not going into SIM mode. you can verify this two ways.
- looking at the lower right corner of the PP screen do you see the word SIM in the model description ie 1100-3-SIM vs 1100-3 if not it's not in SIM mode. so it's looking for limit switches
- look at the log file and you'll see it go into SIM mode, if it doesn't it's looking for real limit switches
- When not in SIM mode, you can go to SETTINGS tab and uncheck the Limit Switches checkbox to disable limit checking
if you want to make PP aware of VMware. you can edit ~/tmc/python/vmcheck.py
after this block of code.
if 'Parallels Virtual Platform' in result:
self.running_in_vm = True
self.vendor = 'Parallels'
returnif 'VMware Virtual Platform' in result:
self.running_in_vm = True
self.vendor = 'VMware'
returnPlease Log in or Create an account to join the conversation.
09 Feb 2019 16:16 #126061
by slipalong
Replied by slipalong on topic Pathpilot 2.1.6 on VMWare
Thanks for getting back to me, I did something similar I
if "VMware" in result
as command was returning VMWare 7.1.
I am seeing 440 SIM as the machine type.
If I hit Z ref I see her-z referenced in queue; stopwatch ....
so its as if its queued a message to LinuxCNC,
but if I then hi cycle start I get Button only permitted when machine is in state(s): referenced
Thanks,
Ian.
if "VMware" in result
as command was returning VMWare 7.1.
I am seeing 440 SIM as the machine type.
If I hit Z ref I see her-z referenced in queue; stopwatch ....
so its as if its queued a message to LinuxCNC,
but if I then hi cycle start I get Button only permitted when machine is in state(s): referenced
Thanks,
Ian.
Please Log in or Create an account to join the conversation.
09 Feb 2019 19:08 #126067
by smgvbest
Replied by smgvbest on topic Pathpilot 2.1.6 on VMWare
Just to check I fired up my VMware 15 instance and selected the 440 as my machine.
I was able to reset, ref x,y and z.
Heres my log section for reference
I did also verify that i was able to jog all 3 axis
i have a few edit's I've made to PP code but nothing for this. mainly customization tweaks.
so the only real difference is I'm on VMware Workstation V15 and it sounds like you're on V7
could it be VMWare related maybe?
Oh I am running it on windows 10 for my host OS
I was able to reset, ref x,y and z.
Heres my log section for reference
2019-02-09 12:58:58.072990 CST (+0:00:02.355230) | ref_z button was pressed. [/home/operator/v2.1.6/python/ui_common.py:1370]
2019-02-09 12:58:58.134293 CST (+0:00:00.061303) | Z-Bot ATC: worker thread started id=140460311144192 [/home/operator/v2.1.6/python/zbot_atc.py:1447]
2019-02-09 12:58:58.136716 CST (+0:00:00.002423) | ATC: do_ref_z pulled from q, wait time 0.000103 [/home/operator/v2.1.6/python/zbot_atc.py:1495]
2019-02-09 12:58:58.600009 CST (+0:00:00.463293) | LinuxCNC status.task_mode change was MODE_MDI is now MODE_MANUAL [tormach_mill_ui.py:8843]
2019-02-09 12:58:59.744381 CST (+0:00:01.144372) | Z referenced in queue; stopwatch: 1.404297 seconds, 7 laps [/home/operator/v2.1.6/python/zbot_atc.py:636]
2019-02-09 12:59:00.761722 CST (+0:00:01.017341) | ref_y button was pressed. [/home/operator/v2.1.6/python/ui_common.py:1370]
2019-02-09 12:59:00.834290 CST (+0:00:00.072568) | ATC: do_ref_y pulled from q, wait time 0.000166 [/home/operator/v2.1.6/python/zbot_atc.py:1495]
2019-02-09 12:59:02.391932 CST (+0:00:01.557642) | Y referenced in queue; stopwatch: 1.403963 seconds, 7 laps [/home/operator/v2.1.6/python/zbot_atc.py:611]
2019-02-09 12:59:03.529217 CST (+0:00:01.137285) | ref_x button was pressed. [/home/operator/v2.1.6/python/ui_common.py:1370]
2019-02-09 12:59:03.596740 CST (+0:00:00.067523) | ATC: do_ref_x pulled from q, wait time 0.000143 [/home/operator/v2.1.6/python/zbot_atc.py:1495]
2019-02-09 12:59:05.154561 CST (+0:00:01.557821) | X referenced in queue; stopwatch: 1.403852 seconds, 7 laps [/home/operator/v2.1.6/python/zbot_atc.py:589]I did also verify that i was able to jog all 3 axis
i have a few edit's I've made to PP code but nothing for this. mainly customization tweaks.
so the only real difference is I'm on VMware Workstation V15 and it sounds like you're on V7
could it be VMWare related maybe?
Oh I am running it on windows 10 for my host OS
Please Log in or Create an account to join the conversation.
09 Feb 2019 20:06 #126079
by slipalong
Replied by slipalong on topic Pathpilot 2.1.6 on VMWare
Could you load a bit of g-code and press cycle start. Im getting a message about it not being allowed as Im not references, paused??
Please Log in or Create an account to join the conversation.
09 Feb 2019 20:19 #126085
by smgvbest
Replied by smgvbest on topic Pathpilot 2.1.6 on VMWare
I loaded a simple facing operation and it worked fine. the only issue I had that had a referencing comment was due to my z was not set to actually allow the travel requested. I raised my z axis and re-zero'd it and it was fine after than
Please Log in or Create an account to join the conversation.
11 Feb 2019 16:43 #126204
by slipalong
Replied by slipalong on topic Pathpilot 2.1.6 on VMWare
Found out what the problem is. the Glib object is used to schedule the internal working of the UI and its doesn't seem to be running.
Could you check what version of glib and pyglib you have in you installation. I think its a bug due to me maybe upgrading some modules.
Could you check what version of glib and pyglib you have in you installation. I think its a bug due to me maybe upgrading some modules.
Please Log in or Create an account to join the conversation.
14 Feb 2019 00:51 #126420
by smgvbest
Replied by smgvbest on topic Pathpilot 2.1.6 on VMWare
glibc is 2.19
pyglib is 2.0
Sorry to take a bit to get his
pyglib is 2.0
Sorry to take a bit to get his
Please Log in or Create an account to join the conversation.
14 Feb 2019 09:47 #126439
by slipalong
Replied by slipalong on topic Pathpilot 2.1.6 on VMWare
Thanks, the problem seemed to be that glibc timeout_add function stopped scheduling the call back function to read the status of linuxcnc due to a function being missing form al old version of psutils. The function was being called to get to get the CPU load and upon failing killed everything in the 50mS thread.
Took a while to track that down as it didn't seem related. All working now so Im trying to modify one of the SIM sets of configs to run a parallel port for step and direction. Without much success.
Took a while to track that down as it didn't seem related. All working now so Im trying to modify one of the SIM sets of configs to run a parallel port for step and direction. Without much success.
Please Log in or Create an account to join the conversation.
Moderators: cncbasher
Time to create page: 0.248 seconds