Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→GUI application
Stream #2 originates at the daa3840-30mc camera module. Then, it is hardware-encoded and streamed by the Orca SBC #1. Finally, it is received by the Orca SBC #2, which hardware decodes and displays it.
==GUI application==
A GUI application runs on the Orca SBC #2 too TBD. This application is engineered with [https://www.cranksoftware.com/storyboard Crank Storyboard 6] and shows some parameters of the Social Distancing algorithm while it operates. The GUI application remotely communicates with the SD application — which is written in Python — through [https://resources.cranksoftware.com/cranksoftware/v5.3.0/docs/webhelp/index.html#ww_sbio.html Storyboard IO API]. According to official documentation, ''the Storyboard IO API, formerly known as GREIO, provides a platform independent communication API that allows inter-task and inter-process queued message passing. This is primarily used to allow external communication with a Storyboard application''. For more details, please see [https://support.cranksoftware.com/hc/en-us/articles/360056943752-Receiving-Events-from-a-Storyboard-Application this article].
= Testing =
Functional tests were conducted in an environment that mimics a real-world scenario. TBDThe goal is to use the SD algorithm for people detection in an hazardous area where a cobot operates and thus where only authorized personnel are allowed to enter — the cobot shown below is part of actual DAVE Embedded Systems manufacturing department's [https://en.wikipedia.org/wiki/Automatic_test_equipment ATE] test-benches.
Orca SBC #1 in installed in the proximity of the cobot, while Orca SBC #2 is located in a different room where human operators can monitor remotely the test-bench. Of course, more advance notification mechanisms could be implemented in order to alarm operators if people are detected in the hazardous area. TBD inserire videoe foto
