Advanced Search

so a stiff pulldown to fight the pullup of the mesa card for the inputs?

I am using 7c81_5abobx2d firmware with BOB boards on P1 and P2.

Edit:
I did a little bit of digging.
- The relay pin P17 is IO7 of the Mesa ports, which is on the edge of the pull resistor array. I could desolder the array and put it back on shifted by one to remove the resistor of the pin.
- On the BOB there is a 10k pullup array on the relay pin. but the signal comes through a via in the middle of the pullup resistor and the 74HC... I could cut the trace between the via and the resistor to remove the pull up on the BOB
- solder in a pulldown resistor on the BOB (if for whatever reason the flat cable between the Mesa and BOB gets bad).

The 7C81 only has the option of all pullups and all pulldowns
on its I/O ports.

Simplest solution would probably be to add a stiff pulldown (say 620 ohms)
on the relay I/O pin. There is a firmware option for fixed parallel port type I/O
but currently its global (not per port), This firmware makes the parallel port
output pins default to outputs instead of inputs at startup or watchdog bite
What firmware are you using?

Maybe a stupid question, but how do you use the relay on those cheap MACH3 BOBs with the 7c81?

For the inputs to work I need to enable the pullups on the 7C81.
But enabling the pullups makes the relay close as soon as the BOB is powered.

Ideally I would want the relay to be open until linuxcnc is started and I tell linuxcnc to close the relay.

But the relay closing by default due to the pullups makes it unusable, or did I miss something?

Hi all,For context: I'm currently building the control system for a Samurai 120 CNC machine (please see the attached photo).Machine electronic hardware configuration:

• 3 × Leadshine EL8 EtherCAT servo drives
• 2 × 400W Leadshine motors with optical encoders and battery backup
• 1 × 400W Leadshine motor with motor brake, also with optical encoder and battery backup
• 1 × Beckhoff EK1100 EtherCAT coupler
• 1 × Raspberry Pi 5 for control

Current progress:

1. Successfully installed LinuxCNC on the Raspberry Pi 5
2. Updated to the latest version
3. Installed CIA402 using Rodw’s guide
4. Configured the Pi as an EtherCAT master

Where I need help: I'm struggling to understand how to configure LinuxCNC to communicate with the servo drives in a basic setup.From what I understand, LinuxCNC relies on three main configuration files:

1. .ini

   – Loads the user interface and references the

   .hal

   file

2. .hal

   – The Hardware Abstraction Layer, which defines machine characteristics and connects components

3. .xml

   – Extracts and defines information from the servo drives

I found Marco Reps’ GitHub repository, which uses a similar configuration. I downloaded all the files and attempted to launch LinuxCNC using the "el8" configuration, but it failed to load.
 Could someone please provide a step-by-step  on how to configure Linux CNC for my current setup? Any help would be greatly appreciated! 

I intend on eventually using the probe basic user interface as I an touchscreen this would work well with. https://samuraimachinetools.com/cdn/shop/files/IMG_9964.jpg?v=1722652171&width=1445