You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm wondering what is the best way to implement tests for hardware interfaces like RS232, RS485, CAN, etc. Our lab setup features a DUT and a RPi that runs the exporter and also acts as remote communication companion for the DUT using USB adapters, etc. to provide the necessary interfaces.
As far as my limited understanding goes, one could:
use labgrid console drivers in pytest to run shell commands on the DUT and the RPi to send some data and check the results on the other side.
use labgrid to copy some test scripts/programs to the DUT and the RPi and run them through pytest and check the return code.
write labgrid drivers to interact with the interfaces on the DUT and the RPi.
Are these assumptions correct? What is the most common/reasonable way? Are there any real-world examples around somewhere to look at?
I also wonder if there is a way to have the hardware interfaces from the DUT and the RPi forwarded somehow to the labgrid client in a way that I can directly access them as "virtual" interfaces from Python code. Python has modules to interact with the interfaces and it would make the test code much more readable and self-contained if I could just implement the tests as if I would for native interfaces on the client machine. But I guess that's out of scope...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I'm wondering what is the best way to implement tests for hardware interfaces like RS232, RS485, CAN, etc. Our lab setup features a DUT and a RPi that runs the exporter and also acts as remote communication companion for the DUT using USB adapters, etc. to provide the necessary interfaces.
As far as my limited understanding goes, one could:
Are these assumptions correct? What is the most common/reasonable way? Are there any real-world examples around somewhere to look at?
I also wonder if there is a way to have the hardware interfaces from the DUT and the RPi forwarded somehow to the labgrid client in a way that I can directly access them as "virtual" interfaces from Python code. Python has modules to interact with the interfaces and it would make the test code much more readable and self-contained if I could just implement the tests as if I would for native interfaces on the client machine. But I guess that's out of scope...
Thanks for any help and additional insights.
Beta Was this translation helpful? Give feedback.
All reactions