Advanced Search

I think I have discovered the root of the problem:

if I do this all in JUST the WHB file:
net machine.is-on                halui.machine.is-on
net machine.is-on                whb.halui.machine.is-on

halshow shows the desired wiring.

But if I have the same exact lines in their respective separate main and WHB files, that's when the pin wiring breaks down.

So... maybe this has something to do with the way hal processes the net commands across files. I can say with certainty the two commands above on separate files = non-working WHB.

Yes, setp uses literals (and only sets the value once at startup if in a hal file)
net commands link a signal to a pin or pins

No sure why halshow does that but halcmd prints the expected (identical) thing:

halcmd: net a hm2_7i95.0.inmux.00.input-00
halcmd: net a hm2_7i95.0.ssr.00.out-00
halcmd: show signal a
Signals:
Type                  Value  Name     (linked to)
bit                   FALSE  a
                                 <== hm2_7i95.0.inmux.00.input-00
                                 ==> hm2_7i95.0.ssr.00.out-00

(new session)


halcmd: net a  hm2_7i95.0.inmux.00.input-00  hm2_7i95.0.ssr.00.out-00
halcmd: show signal a
Signals:
Type                  Value  Name     (linked to)
bit                   FALSE  a
                                 <== hm2_7i95.0.inmux.00.input-00
                                 ==> hm2_7i95.0.ssr.00.out-00



 

Interesting...
So If I have just this one line:
net machine.is-on whb.halui.machine.is-on halui.machine.is-on

halshow shows this for the signal:
Signals:
Type          Value  Name     (linked to)
bit           FALSE  machine.is-on
                         <== halui.machine.is-on
                         ==> whb.halui.machine.is-on

But if instead I have these 2 lines:
net machine-is-on         halui.machine.is-on
net machine.is-on         whb.halui.machine.is-on

halshow shows:
Signals:
Type Value Name (linked to)
bit FALSE machine-is-on
<== halui.machine.is-on

These statements are equivalent:

net a b1 b2 b3

net a b1
net a b2
net a b3

As long as 'a' is a signal and 'b1', 'b2' are pins
and you do not have more than one source pin.

Try Portugal at www.eusurplus.com, they should have 7i96S
And there is no 7i96E but there is 7i76E.

No RPI so not sure how this works ofr it, but for normal Linux this will need editing the GRUB config file so the RT kernel boots instead of the 6.6 that is booting now.
On a PC, holding down the shift keys will show the GRUB menu at boot time so you can choose the kernel to boot, does this work on RPI?

HI
I am getting the "invalid material number" again, last time you said make sure Default material =1 and it is. 
 
Next for some reason there is a problem at the end of a cut,  the torch seems to be at a good height until just before the end and it dives.  These images show it both top and bottom shown. 
 
 
Next the material info seems to be reset to 10000001: temporary 10000001 after it cuts.  Before the cut I set it to one from the list.
 
 
one other question is should I run the Latency test before I do anything at the start??  I am running version V2.10-005-033
Thanks for your time
Tom


 

nauman wrote:

Now I am trying to run it as root user because I don't want to give root access to main user.
 

Why would you give main user root access? There is no need for it, ever if the normal user does not need to install or remove something.
Pretty sure something is amiss, and given the wrong info on the internet, i am not surprised at all.

nauman wrote:

User has no access to file system i have one service running which is doing all the work

That is as simple as setting permissions to a single user folder.

nauman wrote:

I am taking care of the security. Giving root level access to non-root user is more risky for me.

I sincerely doubt it, you do NOT have to give root access to user if you think they do not need it.
Thinking a bit, did you work with Windows Domain Servers?
Linux does not work like that.
You can set the PC to boot into a normal user, you can limit everything to it, so it can run LinuxCNC and not have access to files at all, but this requires someone with SUDO privileges to open a file. Once only.
Or you can limit access to a single folder so he can open files and run the machine, but not save files or open files on other folders, etc, etc
It is a simple as "do not give the user the password", that is it. In normal use they will never need it.

Therein lies my confusion. When I read the basic hal linuxcnc.org/docs/2.6/html/hal/basic_hal.html it says "The same signal-name can be used in multiple net commands to connect additional pins, as long as the rules above are obeyed." (then there's a diagram showing the flow)

My understanding (which may be incorrect?):
machine.is-on (signal)
halui.machine.is-on (signal reader)
whb.halui.machine.is-on (signal reader)

And the man page (their example) states:
"Since the signal xStep contains the value of stepgen.0.out (the source) you can use the same signal again to send the value to another reader. To do this just use the signal with the readers on another line."
So my first attempt was to do just that, but it did not work as I'd expected. Am I incorrect about the nature of these pins?
e.g.
net a b1 b2
does not appear to be the same as
net a b1
net a b2

As I say - maybe my understanding of these pins is flawed. New to the hal concept, and I'm thinking about it like logic circuit wiring.

Looking nice.
And i need help, professional help, i was looking at pictures and started thinking "hey i could do this to my manual lathe"... i have to go past the Mazak to get to manual lathe, Mazak being already CNC and retrofitted and working, sans the hydraulic chuck!

net = connect some pin to some other pin
machine.is-on = LinuxCNC machine on/off pin
halui.machine.is-on = hal UI meaning User interface machine on/off pin
whb.halui.machine.is-on = WHB "joystick" machine on/off pin

@PCW thanks, i knew i was missing something and barking at the wrong tree.

@tommylight, thanks, Modbus was problem due to chinese VSD being fussy and needing 4 other coils set to change speed, with delays between each coil or it would just ignore it all, took me a week to get it working reliably.

I think i'll go with 7i96e/s just need to find one in resonable price and in stock. Used 5i25 would be cheapest but very not future proof.

well, that explains that. I found the in an earlier post the command to install the rt kerne (I think), but I do seem to have the RT kernel already installed because a command
sudo apt install -y linux-image-rt-arm64 linux-headers-rt-arm64
returns a "already at newest version".

But I can't seem to figure out from earlier posts what command instructs to use this kernel?

Thanks for your help!

I am taking care of the security. Giving root level access to non-root user is more risky for me.