Hi Nicolai, thank you for your response! Its PiCtory 2.0.6 and the buster image on the new RevPi Connect, on the old Core one i'm not sure, i have it not connected anymore. And yes, that is what i tried to do, to name the IO's by myself in PiCtory to overwrite the default. And from a PiCtory UI pers...

Hi Community, i have a problem with renaming inputs with the Connect S. When i change the names of Inputs or the order of MIO Modules in PiCtory, its not reflected when i read in the inputs via Python (revpimodio2). In Detail: I changed from an old RevPi Core to a Connect S. Old and new setup with f...

Thank you for your response! Yes, you are right, it is indeed the consuming thread. While reading the queue and doing further processing the warning is thrown multiple times (300?). Apart of that it seems to work with 10 ms. With the print(ct.runtime, q.qsize()) i always get around 0.22 (millisecond...

Hello All, i know questions about this warning are asked a lot, and I read a lot about them but have no answer yet to my specific case. I use Revpi Core 3 with 4 MIO Modules to get 30 1-10 V Analog Inputs. I want to achive a frequency of 100 Hz => a cycletime of 10 ms in my thread that reads the inp...