Pokeys

Based on the message it seems to me that theres to less memory. But as in my system IT euns on an Raspberry Pi 4 (4gb) i cannot qite believe that. (Maybe there IS a way to Reserve more memory for Realtime Part)

Anyway i think the way to go is to reduce Code, especially removing Pins which are Not needed. I might have some time later today to Check thar

I dont think it can be too less memory, too, I use a normal PC with 8GB RAM...
If you could check this would be nice. The pokeys.comp I use is the file that Andy posted on page 10.
I don´t understand very much of this code, but maybe you can copy/paste the needet things in the .comp file from andy?

Hi,

i did a quick merge with my implementation - could you please give it a try? 
pins are named like "pokeys.0.encoder.1.count" 

BR
Dominik 


****Edit****
removed attachment as it does not seem to work as expected

- with added debugging-pin "deb"
0 ... connect fails (check if 'devSerial' matches to your device)
3 ... PK_DigitalIOGet(dev) fails
5 ... PK_AnalogIOGet(dev) fails
12 ... PK_EncoderValuesGet(dev) fails
other values indicate last executed action 

Hello Dominik,

the compiling had worked without error.
Also in Linuxcnc in Halshow I see the new Pins.
But the "alive" pin is not on, I dont get the signals from the input through linuxcnc...
Also the "error" pin is on...

Best regards and thanks for your help,
Marcel

please note updated COMP file in my previous code

Thank you, i will give it a try after work

Hello Dominik,

have try it out, but without sucess...
Compiling without errors,
the pins are visible in halshow.
but the .alive isn´t blinking.
Also the .err is not on.
in the .deb is a 0.

Best regards
Marcel

so it seems that there is an problem to connect

thats the sequence of code:
theres not much between setting deb 0 an 1. And as this section is still similar to the one found at page 10, we should get it to work with some simple checks.

- the command used expects the pokeys connected via USB
- the other thing is to check the value of "devSerial" (which is kind of the address to ensure that the right device is connected)- this should match the serialnumber of your pokeys device (you may set it in HALConfiguration and/or HAL-File using "setp pokeys.0.devSerial [pokeys serial]")
- it hink you already checked if it's powered on
- besides that you might doublecheck instructions in forum.linuxcnc.org/24-hal-components/298...rnet?start=90#162953

BR
Dominik
 

Hey Dominik,

-Pokey is connected via USB, yes
-dev-Serial is correct, set in hal with setp pokeys.0.devSerial 12345
-power is on, the red and green light are on on pokeys.
-done all the steps again...

If I compile the pokeys.comp from page 10, everything runs as it should, beside of the potis.
the alive is blinking, the err pin is off.

Then I close Linuxcnc and compile your pokeys.comp.
no error, see the pins in Linuxcnc, but no alive and deb = 0

If then I close Linuxcnc, compile the pokeys.comp from page 10, and start linuxcnc, everythink works just fine...

I don´t know what to do... :/

Hi,
yes trying the original file of page10 is a good idea - to ensure that the system is basically working.

anyway i managed to access my system remotely and tried to reproduce the problem - on my raspberry having a dummy config it seems to work - but as the deb=13 it seems that it is periodically disconnecting
 
i can hradly see the alive-flag flashing on "HAL Konfiguration" page - i assume because of display latency due to remote connectionbut in HAL-Osziliskope you can see the values changing. 

So i reverted that part of DigitalIO and AnalogIO to be similar as on page10 compiled and - this time - tested if the code runs
(anyway still no encoders connected as i'm not there)
 
 

hope that's similar on your system