TigerMX-5 Download Video Data to USB - Windows

TigerMX-5 Download Video Data to USB - Windows

Download Video Data to USB via Windows

Requirements

Laptop with LAN Port
LAN Cable
USB - FAT32 formatted
PuTTY - Windows SSH Client (64 bit preferred). https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html 

Connect Laptop to TigerMX-5 via LAN

TigerMX-5 Service (LAN) Port:
Remove the rubber cover to access the LAN port. 

Service Port to Laptop:

Insert USB

Connect the USB to either USB 2 or USB 3. 
USB 1 will not work and may have a cover over it already.


Connect to the TigerMX-5

PuTTY
Open PuTTY console window, set host to '10.0.0.1', check 'SSH', then click 'Open'. 

This will open a console window where we can process the video data transfer. 
At the next window type in 'root' to log in as the admin user. 

You're now logged into the TigerMX-5 and we can begin mounting the USB device.

Set USB routing and mount

Ensure the TigerMX-5 can detect the USB device by setting the USB route.
Let's check what it's currently set to:
  1. vars get usb_route
If the output of this command is either "null" or "atom" then you need to update 'usb_route' to 'tiger':
  1. vars set usb_route tiger
Restart the usb-route service for the change to take effect:
  1. systemctl restart usb-route
Check if the USB is detected:
  1. ls /dev/sdb*
Expect:
  1. /dev/sdb   /dev/sdb1
If you see /dev/sdb1 then you're we're ready to proceed with mounting the USB partition:
Make sure you are mounting partition /dev/sdb1  not the device /dev/sdb.
  1. mount -t vfat /dev/sdb1 /mnt
Check if you can access files at the mount point:
  1. ls /mnt
Expect it to list what's currently stored on the device:
  1. EFI                        System Volume Information

Transfer Files

When performing a large transfer it's best to use rsync in a background process.
This allows the option for the transfer to continue even if you close the console window. 
If the vehicle turns off, you can turn it back on, remount the USB device, run the rsync command again and it will resume where it stopped.
  1. cd /media/ssd/atlas/dvr
Then, for example, to download all the hopper camera videos for March 2020 and move them to the USB under the folder name 'BlackMothVideo'.
  1. nohup rsync -avhm --include="*/" --include="inside*.mkv" --exclude="*" ./2020-03* /mnt/BlackMothVideo/ > ../rsync.log 2>&1 &
To download everything from every camera use the following:
  1. nohup rsync -avhm --include="*/" --include="*.mkv" --exclude="*" ./* /mnt/dest-folder/ > ../rsync.log 2>&1 &
Now you can monitor progress by tailing the log file:
  1. tail -f ../rsync.log
Remember to sync and unmount when finished
  1. sync && umount /dev/sdb1
Once unmounted you're now complete! 
The USB can be removed and the vehicle can now be turned off and the system timers will turn the TigerMX-5 off. 

F.A.Q.

What size USB should I use? 

Retrieve 1 camera stream:
64GB = 10 - 15 Days of video
128GB = 25 - 30 Days
256GB = Recommended
Retrieve 5 camera streams:
64GB = 2 - 4 Days
128GB = 5 - 8 Days
256GB = 10 - 15 Days
512GB = 25 - 30 Days

How long will the download take? 

Retrieve 1 camera stream:
1 Day = 6 minutes of download
1 week = 40 minutes
1 month = 3 hours

What if there's no USB ports available? 

WinSCP - Windows SCP Client - https://winscp.net/eng/download.php 
Instead of connecting the USB to the TigerMX-5 you can connect it to the laptop and then transfer through WinSCP. 
Connect via user 'root'.
Highlight the files you need from /media/ssd/atlas/dvr/ on the right panel, then drag and drop them into the USB directory on the left panel. 
This is much slower and not recommended if avoidable.

I ran the wrong command, how do I stop it?

If you've run the wrong command and need to stop it from running that transfer you can stop the process ID that it generated. 
  1. nohup rsync -avhm --include="*/" --include="inspection*.mkv" --exclude="*" ./2019-10-23* /mnt/BlackMothVideo/ > ../rsync.log 2>&1 &
  2. [1] 17304
In this case the Process ID is '17304', so we can run a command to stop it.
  1. Kill 17304
If you can no longer find it in the terminal we can search for it with this: 
  1. ps aux | grep "rsync"
It will return something like below:
  1. root     17304 45.0  0.1   3252  1204 pts/0    R    09:15   0:02 rsync -avhm --include=*/ --include=inspection*.mkv --exclude=* ./2019-10-23 /mnt/BlackMothVideo/
  2. root     17305  0.0  0.0   2824   264 pts/0    S    09:15   0:00 rsync -avhm --include=*/ --include=inspection*.mkv --exclude=* ./2019-10-23 /mnt/BlackMothVideo/
  3. root     17306 39.6  0.0   3244   552 pts/0    S    09:15   0:02 rsync -avhm --include=*/ --include=inspection*.mkv --exclude=* ./2019-10-23 /mnt/BlackMothVideo/
  4. root     17338  0.0  0.0   2716   456 pts/1    S+   09:16   0:00 grep rsync
We only want the 'R' running process which is 17304, now that we've found it, we can stop it.