Another plasma component...

More
7 years 4 months ago #136202 by AgentWD40

phillc54 wrote: Do you have two Z axes?

Two z motors.

First off try: (assuming this is the path to your git clone)

Code:
$ ~/linuxcnc-plasmac/configs/by_machine/plasmac/configurator.py
select upgrade then your ini file then upgrade and see if that changes things.

If that doesn't help can you post your ini and hal files

Cheers, Phill


I'm away from the machine until this evening so I'll give it a try and update by tomorrow. But I was attempting to do a new clean config, it was nothing more than basic pncconf to get the motors jogging, then processed by the configurator.py to initialize plasmac. Same strategy I used a few days ago before 2.9

Please Log in to join the conversation.

More
7 years 4 months ago #136205 by islander261
Phill

The torch enable button colors are working for me now. Thank you.

John

Please Log in to join the conversation.

More
7 years 4 months ago #136328 by AgentWD40

phillc54 wrote: Do you have two Z axes?

First off try: (assuming this is the path to your git clone)

Code:
$ ~/linuxcnc-plasmac/configs/by_machine/plasmac/configurator.py
select upgrade then your ini file then upgrade and see if that changes things.

If that doesn't help can you post your ini and hal files

Cheers, Phill


Here's the ini and hal files.

And if it matters the console was complaining about missing gmoccapy2.glade, don't know if it matters. Here's a listing of the files in the config directory:
Code:
kyle@debian:~/linuxcnc/configs/lucy$ ls -al total 88 drwxr-xr-x 2 kyle kyle 4096 Jun 8 20:14 . drwxr-xr-x 4 kyle kyle 4096 Jun 6 23:10 .. -rw-r--r-- 1 kyle kyle 1666 Jun 8 20:14 imperial_parameters.txt -rw-r--r-- 1 kyle kyle 1666 Jun 8 20:14 imperial_parameters.txt.bak lrwxrwxrwx 1 kyle kyle 22 Jun 6 23:10 imperial_startup.ngc -> ./imperial_startup.ngc -rw-r--r-- 1 kyle kyle 1348 Jun 6 23:45 lucy_connections.hal -rw-r--r-- 1 kyle kyle 13498 Jun 6 23:47 lucy.hal -rw-r--r-- 1 kyle kyle 9168 Jun 6 23:48 lucy.ini -rw-r--r-- 1 kyle kyle 600 Jun 6 23:10 lucy_material.cfg -rw-r--r-- 1 kyle kyle 316 Jun 8 20:14 lucy.pref lrwxrwxrwx 1 kyle kyle 6 Jun 6 23:10 M190 -> ./M190 lrwxrwxrwx 1 kyle kyle 19 Jun 6 23:10 materialverter.py -> ./materialverter.py lrwxrwxrwx 1 kyle kyle 20 Jun 6 23:10 metric_startup.ngc -> ./metric_startup.ngc -rw-r--r-- 1 kyle kyle 13469 Jun 6 23:10 _original_Base.hal -rw-r--r-- 1 kyle kyle 5148 Jun 6 23:10 _original_Base.ini lrwxrwxrwx 1 kyle kyle 23 Jun 6 23:10 plasmac_buttons.glade -> ./plasmac_buttons.glade lrwxrwxrwx 1 kyle kyle 21 Jun 6 23:10 plasmac_buttons.hal -> ./plasmac_buttons.hal lrwxrwxrwx 1 kyle kyle 20 Jun 6 23:10 plasmac_buttons.py -> ./plasmac_buttons.py lrwxrwxrwx 1 kyle kyle 22 Jun 6 23:10 plasmac_config.glade -> ./plasmac_config.glade lrwxrwxrwx 1 kyle kyle 20 Jun 6 23:10 plasmac_config.hal -> ./plasmac_config.hal lrwxrwxrwx 1 kyle kyle 19 Jun 6 23:10 plasmac_config.py -> ./plasmac_config.py lrwxrwxrwx 1 kyle kyle 23 Jun 6 23:10 plasmac_control.glade -> ./plasmac_control.glade lrwxrwxrwx 1 kyle kyle 21 Jun 6 23:10 plasmac_control.hal -> ./plasmac_control.hal lrwxrwxrwx 1 kyle kyle 20 Jun 6 23:10 plasmac_control.py -> ./plasmac_control.py lrwxrwxrwx 1 kyle kyle 18 Jun 6 23:10 plasmac_gcode.py -> ./plasmac_gcode.py -rw-r--r-- 1 kyle kyle 2266 Jun 6 23:10 plasmac.hal lrwxrwxrwx 1 kyle kyle 23 Jun 6 23:10 plasmac_monitor.glade -> ./plasmac_monitor.glade lrwxrwxrwx 1 kyle kyle 21 Jun 6 23:10 plasmac_monitor.hal -> ./plasmac_monitor.hal lrwxrwxrwx 1 kyle kyle 20 Jun 6 23:10 plasmac_monitor.py -> ./plasmac_monitor.py lrwxrwxrwx 1 kyle kyle 19 Jun 6 23:10 plasmac_run.glade -> ./plasmac_run.glade lrwxrwxrwx 1 kyle kyle 17 Jun 6 23:10 plasmac_run.hal -> ./plasmac_run.hal lrwxrwxrwx 1 kyle kyle 16 Jun 6 23:10 plasmac_run.py -> ./plasmac_run.py lrwxrwxrwx 1 kyle kyle 21 Jun 6 23:10 plasmac_stats.glade -> ./plasmac_stats.glade lrwxrwxrwx 1 kyle kyle 19 Jun 6 23:10 plasmac_stats.hal -> ./plasmac_stats.hal lrwxrwxrwx 1 kyle kyle 18 Jun 6 23:10 plasmac_stats.py -> ./plasmac_stats.py -rw-r--r-- 1 kyle kyle 519 Jun 6 23:10 postgui.hal lrwxrwxrwx 1 kyle kyle 11 Jun 6 23:10 README.md -> ./README.md lrwxrwxrwx 1 kyle kyle 10 Jun 6 23:10 tool.tbl -> ./tool.tbl

Please Log in to join the conversation.

More
7 years 4 months ago #136329 by phillc54
It seems all your links are pointing back to themselves.
mkardasi had the same problem here

Do you have a recent version, if not then download the latest and try the configurator command I gave you earlier.

I have no idea what gmoccapy2.glade is.

Cheers, Phill

Please Log in to join the conversation.

More
7 years 4 months ago #136332 by islander261
Phill etal

Don't worry about the second screen for Gmoccapy. Everyone's install checks for it and no one has a second screen that I have seen. If one of the Python Gurus wants to get rid i of this on their install I am sure that commenting out the appropriate lines in the Gmoccapy Python handler file will cure it.

John

Please Log in to join the conversation.

More
7 years 4 months ago #136334 by AgentWD40

phillc54 wrote: It seems all your links are pointing back to themselves.
mkardasi had the same problem here

Do you have a recent version, if not then download the latest and try the configurator command I gave you earlier

Yes. pulled just now.

Ok I see what you're doing. The links that are created in the config directory are relative to the directory the configurator is called from. I called the configurator and 'upgraded' from both ~/ and ~/plasmac (my install directory). Neither of these worked. I finally just deleted the links and copied over the files directly and it's working now without links.

Please Log in to join the conversation.

More
7 years 4 months ago #136336 by phillc54
Yes, the configurator is run in the same directory the original plasmac source is.
When you do an upggrade you enter the inifile path/name of the configuration you want to upgrade.
The disadvantage of using actual file copies is that you need to recopy any files that have been upgraded whereas with links if they are pointing to the correct location then that is not necessary.

Cheers, Phill.

Please Log in to join the conversation.

More
7 years 4 months ago #136338 by AgentWD40
Any clue why mine aren't working? The paths that were created in my case were in the form of ./plasmac/configs/..., should they start with a ~ instead of a dot. Maybe it would be more bulletproof if the links used full paths?

Please Log in to join the conversation.

More
7 years 4 months ago #136339 by AgentWD40
I changed line #73 of configurator.py to
Code:
self.copyPath = os.path.dirname(os.path.abspath(__file__))

in order to get the links to use full path names and it seems to have worked. My new config loads just fine.

Please Log in to join the conversation.

More
7 years 4 months ago #136340 by phillc54
It is hard to give full paths because not everyone will put their clone into /home/{USERNAME}/linuxcnc-plasmac/

I have run the configurator from different paths that were real clones and have not had a problem. I have used both Stretch, Wheezy and LMDE2.

Cheers, Phill.

Please Log in to join the conversation.

Time to create page: 4.611 seconds
Powered by Kunena Forum