halcompile shared lib

Hi to all

I'm running a soft-plc on RPi4-4G.
To interface with it I have a shared lib that reads/writes the tags from/to the plc ( and Qt ).
I have build a uspace module to Lcnc and it works fine. At 50 - 80 msec.
Now I like to interface with servo thread.
The question is how to compile the function with my shared lib.
What I did so far:
I have the .comp file. Include the header of the symbols.so : symbols.h
With sudo halcompile llx.comp I get the llx.c file.
With sudo halcompile --install llx.comp I get the llx.so inside /linuxcnc/components/
If I start Lcnc without using a lib function it starts up fine.
If I start up using a lib function I get error undefined symbol.

Where do I go from here ???

halcompile runs fine?

how is your running order of hal initialization? load and addf ...
May be the realtime module is loaded and initializied before the uspace module.

hi db1981

I don't think so;

#loadrt threads name1 = test-thread period1=10000
# Load plc-module llxplc3 into userspace
loadusr -W llxplc3

# Load plc-module llxplc into servo-thread
loadrt llxplc
addf llxplc.0 servo-thread

attached the .comp files

as you see in llxplc.comp line 68 - 86 is commented out.
Like this Lcnc starts fine and timer tiks.
else I get an error at startup of Lcnc

I was reading this
www.forum.linuxcnc.org/24-hal-components...my-hal-comp?start=10
but did not get any further.

attached the error window;

hi,

i have no lcnc machine here,
can you post the compiled *.c file from output halcompile --compile (compiled with line 68-86 uncommented...), and the header file?

here it comes

and here the llxplc.so

please rename to llxplx.so

linking work, include works, i not shure how the LL? libs got linked.

try an "LLSYMBOLS_API" in front of the function call LLsym_init(),
like in line 65.

all public functions got an LLSYMBOLS_API prefixed in the header file.

attached the errors

One thing I like to mention: as you can see in the llxplc3.comp these calls are working fine for the uspace module.

by the way... thanks for looking into it. I'm really stuck with this.

best regards
udo

oh, there's a macro.

okay, then coding seems right, my belly thinks it's an execution / startup thing....

for testing put the code line 69-86 in a if construction triggerd by an hal bit, and check if linuxcnc starts. after linuxcnc is fully running set the bit and check for crash....

i gues the rt's code is running before the all other modules finished initializing.