Advanced Search

Better to use the on card 7I95T encoders for machine feedback.
You can put high speed encoders on the expansion ports
but for feedback use its better to use differential signaling
and the 7I95T already has 6 encoder input designed for this.

halcmd (and hal)  are fine with true/false for bit types:

pcw@pcw-HP-Compaq-Elite-8300-USDT:~/linuxcnc-dev/src/hal/components$ halcmd setp hm2_7i96s.0.ssr.00.out-00 true
pcw@pcw-HP-Compaq-Elite-8300-USDT:~/linuxcnc-dev/src/hal/components$ halcmd getp hm2_7i96s.0.ssr.00.out-00 TRUE

pi@raspberrypi5:~/linuxcnc/nc_files $ ./M101
bash: ./M101: cannot execute: required file not found

Likely means that bash was not found.



 

To PCW: I would use 5v encoders... are the parallel expansion ports capable of high speed encoders? like 1um linear scales?
7i73 looks like a nice option as well.
Thanks!

I do understand you can vary the scaling of the ppr->movement, the machine im retrofitting never had any scale switch, though never using this machine originally, i dont know exactly how it functioned. It is a good idea though. Thanks!

It's finding bash fine, the command requires either a 0 or 1 as input, going by the error message, not a "True" or "False"


It's kind of hard to debug without seeing the script.

My comment regarding true or false is incorrect, thanks PCW.

Should the command be run from a bash command line or within a halcmd session ?

I've gone all rusty as of late...must be the dust from the build garage storage

Awesome. Glad it's working!

Success!
I moved that line to my posthui.hal and now everything works. 

# --- ESTOP-EXT ---
net pendant-estop     <= hm2_7i76e.0.7i76.0.0.input-29

Thx for the support. 

michaelvdberghe wrote:

so i dont understand how these correspond to physical pins on the remora board itself, do you still have to add those manualy in the code.


espacialy for the x-axis i dont see where the enable pin is or where the xp+, xp-, xd+,xd- are refferencd in the code here. i realy dot get it, the documentaion is not making sence.

forum.linuxcnc.org/18-computer/44828-rem...rd?start=2200#327803

here is how the pins correspond to the physical pins. the xp and xd pins are defined in the config.txt and are turned into stepgen1,2,whatever

It looks like maybe a comflict in pb, the ui tries loading which should set an active work coordinate system. This is how the button synchronization and exclusivity functions.

It may be your pendant code. This is the first error of that nature ive had reported in 8 years and there are thousands of pendant users out there.

I would try moving any items that need to synchronize with the gui into the postgui halfile and see if functionality still works and the error goes away.

You probably want to start your script with:
#!/usr/bin/env bash

I think this error is saying that /bin/bash is not in that location the /usr/bin/env will use the bash thats in your path. 

 

Good question.
I also wonder is this really is a PB issue or maybe a general LinuxCNC topic. What do you think?

I wonder if it's because it's being loaded before the GUI is loaded

 Sorry, I really didn't comment out these lines in Hal when I tested it from the command line. Here are the error messages.

pi@raspberrypi5:~/linuxcnc/nc_files $ bash M101
' invalid for bitvalue 'True
<commandline>:0: setp failed
: numeric argument required
pi@raspberrypi5:~/linuxcnc/nc_files $ 
 

One sserial port can have from 1 to 8 channels so the mesaflash information is correct.

If both cards don't show up in hal, its likely that they are not enabled in the sserial_port_0=nnnxxxx
stanza in the driver command line



 

Hi all,I'm struggling with the following Mesa card combination: 7i92 + 7i77 + 7i76.I’m using the firmware. Unfortunately, only the Smart Serial peripheral on P1 is being detected — nothing shows up on P2.To clarify:
When I flash a different firmware, the same card that previously didn’t communicate on P2 works fine on P1, so I believe the Smart Serial slave and its power supply are OK.Here’s the output of:
 yaml
CopyEditI read somewhere that there should be more than one SSerial interface listed if both ports (P1 and P2) are configured for Smart Serial. It seems like the firmware might not be enabling SSerial on both channels.Has anyone encountered this issue?
Or is there someone with a working build environment who could check the Mesa source files to see if there's a configuration error?Any help would be greatly appreciated.@PCW – if you have a moment, your insight would be very welcome.