Advanced Search

I get an access denied error if I modcompile without sudo. Can that be the issue?

Sorry, apparently I didn't read your complete post. I'll try again

Gents,

mancave conditions: several cnc machines but will use one at the time. Plan to use lenovo T470 touch laptor with LinuxCNC on it. Each cnc machine will have Mesa on board (some ethernet model). One thing is bothering me: each machine Mesa card will have specific bit file. How about LinuxCNC on laptop? Is it possible to have several "profiles" so i can simply switch one machine off, disconnect ethernet cable, go to the next one with my laptop, plug eth in and just start machine specific profile and just use it? What if i want to use this nice black/yellow high contrast GUI 
on plasma, but then regular AXIC on the router then lathe specific one.

Can it be done?
 

Now it's obvious i'm a newby. I don't know where to find your example. It doesn't looks to be on my machine.

Strange that the example I mentioned above does not work. I just did a complete fresh install of 2.9.4 and it compiled ok, but same error at loadrt.

i found a bug in the avg call (wrong place)

if you use an avg filter and have problems with strange spikes, you should update


fixed in master and dev

That does not seem to compile

Can you try an example file from the modbus directory, say relayboard.mod

or alternatively here's a  simple .mod file I am running right now (linuxCNC 2.9.4)
that works with the common 32in 32 out modbus modules from Eletechsup:


 

Needs to be renamed to mb25ioc32.mod before compiling with

modcompile mb25ioc32.mod

 

forum.linuxcnc.org/plasmac/43127-qtplasm...-user-request-enable
forum.linuxcnc.org/plasmac/54940-qtplasmac-estop-stuck
www.forum.linuxcnc.org/38-general-linuxc...plasmac-wont-turn-on

I'm running x86

To be sure I have no errors in my mod file, I just copied the one from the Mesa Modbus documentation:

 /*
The format of the channel descriptors is:

{TYPE, FUNC, ADDR, COUNT, pin_name}

TYPE is one of HAL_BIT, HAL_FLOAT, HAL_S32, HAL_U32
FUNC = 1, 2, 3, 4, 5, 6, 15, 16 - Modbus commands
COUNT = number of coils/registers to read
*/

#define MAX_MSG_LEN 16 // may be increased if necessary to max 251

static const hm2_modbus_chan_descriptor_t channels = {
/* {TYPE, FUNC, ADDR, COUNT, pin_name} */
// Create 8 HAL bit pins coil-00 .. -07 supplying the values of coils at 0x0000
{HAL_BIT, 1, 0x0000, 8, "coil"},
// Create 8 HAL bit pins input-00 .. -07 supplying the values of inputs at 0x0000
{HAL_BIT, 2, 0x0000, 8, "input"},
// Create a HAL pin to set the coil at address 0x0010
{HAL_BIT, 5, 0x0010, 1, "coil-0"},
// Create 8 HAL pins to set the coils at 0x0020
{HAL_BIT, 15, 0x0020, 8, "more_coils"},
// Create a scaled floating point pin calculated from input register 0x0100
{HAL_FLOAT, 4, 0x0100, 1, "float"},
// Create 4 unsigned integer HAL pins from the holding registers at 0x0200-0x203
{HAL_S32, 3, 0x0003, 4, "holding"},
// Create a single signed int HAL pin to control the register at 0x0300
{HAL_S32, 6, 0x0300, 1, "relay-3"},
// Create 7 scaled FP HAL pins to control holfing registers at 0x400-0x406
{HAL_FLOAT, 16, 0x0300, 1, "more_floats"},
};

x86 or ARM?

If you post the .mod file I can try and duplicate the issue
 

I would like to return to my original question. How is it possible to reference files in source codes? Does anyone know? Or at least have some guidance?

forum.linuxcnc.org/gmoccapy/55011-lcnc-2...-g43?start=10#320387

for the record, I'm running linuxcnc 2.9.4 on Debian bookworm

yes.
I loaded 7i96sd_pktv2.bin and see the PktUARTRX and TX port (0) with mesaflash --readhmid --addr 10.10.10.10 --device 7i96s

My StepperOnline/LeadShine EL7 EtherCAT servo drives don't have a STO (safe torque off) feature.  Because of this, I have the servo drive AC power fed from a contactor that's part of the safety relay / E-Stop loop.  When E-Stop is triggered, the contactor cuts out and the drives will lose AC power entirely.  Unfortunately, these drives do not have separate power inputs for logic vs motor like I have seen on other brands.

I think this is fine from a safety standpoint both for humans and for the lifespan of the drives.  But this means the drives will drop off the EtherCAT bus and LCEC/LinuxCNC will lose their minds.  I'm not sure how recoverable this is beyond shutting LinuxCNC down and starting it back up after the emergency stop condition has cleared.

What approach have others taken to this scenario? 
 

Hi Fabian,

+1 Yes calculating derivates after transforming is more efficient.

Up to 43 is done. Except eq41.
eq39 theta
eq40 kappa
eq42 sharpness
eq43
eq45

Now starting the first 3 of eq44. G3 continuity. Hmm.
I didn't know the big SUM sign. It seems a for loop. Starting at h=1 up to h=4.
That being clearified. We can try to code this.

Does your firmware have a pkt_uart?