Advanced Search

tommylight wrote:

Are you trying to run LinuxCNC in sim mode inside a VM?
 

No.

Now, what was your question?

I need a Parallels LinuxCNC VM created in Parallels on an Intel Mac.

JT wrote:

Your screen shot looks correct. I added multi state labels on the 20th, how are you updating?
JT
 

I'm downloading the deb release from the git page. It's still at 1.1.1 but is says it's been updated since then.

Looks like apt didn't update it right this time since it's still version 1.1.1, I used gdebi and now it works. I did get a wierd error about a different label already having that hal pin name but that wasn't the case. I'm not sure if that stems from the multi-state label having the same widget name as it's hal pin name or the hal pin name having underscores. I had other regular labels with a single hal pin with underscore in the name and it was fine. I just changed the underscores in the hal pin name to dashes and the error went away.

See network can't connect to to them. What am I missing? 

Are you trying to run LinuxCNC in sim mode inside a VM?
Then it all pertains to it, several options:
Using the official ISO, should work as any other distro in VM, but might have issues with RT kernel and VM not getting along nicely
Using Debian or LMDE6, if those work in VM, then adding LinuxCNC is easy, and should work as you can use them without booting into the RT kernel.
Now, what was your question?

JT wrote:

Take a look at this thread for the coordination of an external E-Stop with LinuxCNC
forum.linuxcnc.org/47-hal-examples/25861-external-e-stop
 

Nah estop-loop doesn't work right in practice without extra logic components either. The way it's shown in the other thread it does block the UI Estop, but the reset won't trigger until you toggle the UI button afterwards. I just didn't notice I still had iocontrol.0.emc-enable-in connected to iocontrol.0.emc-enable-in. I just needed to break that with a NC circuit. Maybe one day somebody will rework the mess that exists between halui and iocontrol estop pins. It would probably be as simple as adding 2 pins to halui to break the iocontrol loop when is-activated=true. If that loop is unused it would behave as it does now, like a toggle off a momentary switch.....That's besides the point, I figured it out.

I have not tested an external E-Stop so the colors may not stay in sync.

If they followed the same logic as the actual E-stop and Power states like the button labels do they'd be fine. You can test it easily by setting the halui.estop activate, reset and halui.machine.on pins

Have a look at mdi_command as in this example (instead of 'net coolant-flood => halui.mdi-command-00' you would connect it to the button hal pin):
forum.linuxcnc.org/qtvcp/54583-call-cust...om-gui-button#315402

Ok, thank you PCW, I will do that and try it out these days. I'm just getting a cold and my garage has 9°C, thats not very comfortable.
I will report the results asap!

Kind regards

I would make some changes in the hal file.

Change:

setp hm2_7i76e.0.dpll.01.timer-us -50

to:

setp hm2_7i76e.0.dpll.01.timer-us -200

and change all joint PID "P" terms to 666



 

tommylight wrote:

If you can use any Linux x86_64 on it, then download the official ISO and try installing it, but might have issues with RT kernel running in a VM.
You can try Debian 12.x or Linux Mint Debian Edition 6, and if they work just install LinuxCNC with
sudo apt install linuxcnc-uspace
This will also install the RT kernel, but it will not be the default one, so LinuxCNC should work OK in SIM mode.
 

I have been looking at this response for almost a whole day, and I still can't figure out what part of it applies to my question.

Yeah, the GUIs don't list all possible connections so you
need to connect these by directly editing the hal files.

Thanks for your patience.
I get that I can find all the available pins using the methods above.
What I don't get is that when I use mesaCT or PNCConf to create ini and .hal files and have selected say channel 0 for the X encoder, The physical pins that will be used don't show up the hal file.
Its to me like when you make the selection in the gui, some things are automatically known like the pins, and the hal file doesn't need to show all of them, just ones you might need to edit.
So the hal file isn't the place to look for the full details of a setup right back to pins.
I will learn this system...

The hal file is what connects things (it does not show all possible pins) ,
so to use an encoder input, you would do something like this:

net min-x <= hm2_7i92.0.encoder.01.input-a

You can use halshow to browse pins and parameters:

 


or list all pins/parameters by running this command:

halcmd show all

from a terminal window when LinuxCNC is running.

You can also

halcmd show all > all.txt

to create a copy/paste donor file when editing hal files

if you just want hardware pins/parameters

halcmd show all hm2

will do

If you just want encoder pins/parameters.

halcmd show all *encoder*

or

halcmd show pin *encoder*

if you just want to see encoder pins.

Maybe post your hal and ini files.

I guess that's the bit I am missing.
In the hal file, there are no "input-a" anything for the X,Y and Z encoders so I don't get how lcnc knows what anything is connected to.

Sorry.

The raw encoder pins have names like:

hm2_7i92.0.encoder.03.input-a
hm2_7i92.0.encoder.03.input-b
hm2_7i92.0.encoder.03.input-index