@rsr4z , voxl logger will create different directories and files for different data that it will be logging, so using a single socket for this will now work.
If you REALLY want to have the log files saved directly to your PC and your network connectivity has the bandwidth to do it, then you can potentially map your desktop as a network drive (using sshfs or something like that). Then you can save your logs to the network drive. However, you should be aware of the following potential issues:
ssh is encrypted, so encryption of data will take some additional cpu usage on VOXL (proportional to the amount of data)
network-mapped drives are not always reliable, especially if you connection is not reliable, but there are sshfs flags you can try to automatically reconnect, etc..
if there is not enough bandwidth to save the data over your network connection, voxl-logger can get occasionally blocked and will drop packets on the MPA side
Another option you can consider is saving the logs on voxl, and then using periodic rsync to get the data to your PC. rsync works over ssh as well. I just did a quick search and this came up (i did not try it):
fswatch -o /src | xargs -n1 -I{} rsync -a /src /dest
(https://stackoverflow.com/questions/12460279/how-to-keep-two-folders-automatically-synchronized)
you would need to copy your voxl2's key onto your desktop so that you don't need to enter your password every time..
Finally, if you did not want to write to the VOXL2's drive at all, you could save the logs to tempfs (/dev/shm) and then rsync from there to your PC and have rsync delete the files after syncing in order to avoid filling up your RAM, but you have to be careful and not delete files that are still being written by the logger..
Hopefully this gives you a few options to think about..
