Yes, this comes from the fact that we are using the mass_storage way of exporting the microSD card over USB, which does not allow simultaneous access by the host and the camera CPU. The MTP way of sharing the microSD would be better but we cannot use it due to hardware limitations (number of USB endpoints).
I agree with you, python is quite tedious because it does not have a compiler to check for simple mistakes before you run your code just to discover a typo. Usually, I develop my code in "host" mode first, and, once it works, I copy it to the camera. The workflow is a bit faster:
- get the jevois-sdk-dev Ubuntu package installed on your machine (or a virtualbox)
- in jevois, add a videomapping for your new module in ~/jevois/Config/videomappings.cfg and ./rebuild-host.sh
- in jevoisbase, or your custom module, do a ./rebuild-host.sh, then cd hbuild/
- open an editor and edit your python file
- when you are done, save, and then, in the terminal that you had open in hbuild/, just type "make && sudo make install" (once you have typed it once, next time you can just use the up arrow to run it again)
- then jevois-daemon --videomapping=XXX where XXX is the mapping number of your module. When you are done testing, issue a "quit" to jevois-daemon.
- Then loop: edit again (editor remains open the whole time), save, up arrow twice to make again, up arrow twice to run jevois-daemon again.
Once it works on host, transfer to microSD and it should work in the camera too.