Advanced Search

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.

Excellent, it doesn't have a tool changer, which is a plus. I would like to add one eventually if possible, but that’s more of a future upgrade.

Regarding the spindle control, that’s an area I want to dive deeper into, but I'm not sure where to start.
From what I understand, important aspects would include direction of rotation, speed control, and handling alarms or faults. Is there anything else I should be considering?

@andypugh I started from the Marco Reps config. Everything is working as intended except for the delay/following error in the servo drive. I suspect the error to be within the drive, but I uploaded the configs as I am no LinuxCNC EtherCAT professional, and there is always the possibility of some stupid errors. The drive-internal parameter for following error is staying at 0. It is always exactly 0, so that could be a bug as well.

@PCW I tried CSV mode (without success, as the problem seems to be there as well but with different symptoms), and within the scope I can see the first reactions to the control signal within 3–4 ms. So I suspect EtherCAT is running fine and without (or at least with a very small) delay. I think I can confirm the existence of some form of filter, as acceleration values of 10,000–20,000 mm/s² are smoothed out a lot compared to a similar machine with 1 kW servos with step/dir signals.
Regarding the poor position loop – I have had settings without this oscillation, but I was trying around with pretty much all settings within the drives and was at the point of giving up when taking the screenshot. All plots without oscillations had similar bad following errors.

@Hakan Switching to CSV mode and including LinuxCNC within the feedback loop was reported successful by other users, but I was not able to get it working with a following error of <<0.5 mm. As including LinuxCNC within the feedback loop creates many more parameters to be tuned (LinuxCNC PID and parameters within the drives), that turned out to be a very time-consuming project without any real success.All in all, the Lichuan support was very unhelpful, and after trying to tune just one of the four drives (Z-axis first) for about three days, I am thinking of ditching the Lichuan drivers and motors and using Leadshine servos. If there are any ideas, I am open to trying almost everything Thanks in advance.Alex

pin 'hm2_7i95.0.ssr.00.out-01' is connected to a signal

Is the error, you cannot change the state of a pin that's already drive by a signal in hal
You would need to delete (or comment out) the net command that connects
hm2_7i95.0.ssr.00.out-01 to a signal in your hal file for the MXXX script to work.
 

langdons
Thx for you pointing this out and your hint on 5V relay.
I do have a parport based router. All pins are used, and still I want my vacuum clamping, dust extraction, myst (maybe) etc. to be operable from within axis (in my case).

greez
chris

Tried it two ways, still doesn't work. In the first case it gives an error.

pi@raspberrypi5:~/linuxcnc/nc_files $ ./M101
bash: ./M101: cannot execute: required file not found
pi@raspberrypi5:~/linuxcnc/nc_files $ bash M101
<commandline>:0: pin 'hm2_7i95.0.ssr.00.out-01' is connected to a signal
: numeric argument required

Does the script work if run from the command line?

 That is, does:

./M101

work?