Skip to content

FAQ

Jump to bottom
Axel Barnitzke edited this page Nov 17, 2018 · 12 revisions

Frequently asked Questions

Start/Stop the tracking Process

Sometimes you need to stop the tracking process.

With a monitor/keyboard connected

If the preview window is in front of all elements you need to type Ctrl-Alt-Del.
Then you get a dialog window which shows all running processes.
Right-Click on the Python process and choose 'Kill' to stop the process. The preview window will disappear immediately and you are able to use all desktop elements. Klick on the Terminal symbol to start a local shell.
If you are unsure please take a look at the Getting Started page.

With MobaXterm or Putty via network

If the Raspberry is connected to your network (WiFi or LAN) you can use a ssh client. (MobaXterm or Putty) Connect to the IP of the Raspberry and open an ssh session with user pi and password Olav01 (if you did't change that default password)
There is a quite a good (and short) description on raspberrypi.org
Once you are connected to the Raspberry you should type:

killall python

This will stop the tracking process.

Manually start the tracking process

You should have had opened a terminal or ssh session. Now you have 2 possibilities to start the tracking:

  1. from command line watching the output of the process
cd piCAMTracker
./runtracker.py

You can stop it at anytime by holding down Ctrl-c.
2. From command line into background If you want to leave the session you need to put the process in background.

runtracker&

Update to latest version

Currently it is not planned to enable the update via the web interface.
You need to login to the Raspberry and update the software with the following git commands:

cd piCAMTracker
git pull

Forced update to latest version

if you get an error that your local changes conflict with the origin you need to force the update and redo your local changes. (Experienced people can do a git stash and merge their changes afterwards. The following commands will remove all changes and update your local files to the latest version on the server:

cd piCAMTracker
git fetch --all
git reset --hard origin/master
git pull origin master

Now you have to adapt your latest changes again.
This will be mostly:

V2 camera V1 camera
yCross: 28 yCross: 30
viewAngle: 90 viewAngle: 270

No motion detection when I am in my workshop

I had this when I wanted to show the tracker in the workshop of a colleague. We found the reason was the neon lights he's using in his workshop. The neon lights completely stop the detection process!
Darkness is not really a problem. Once you passed the twilight time the camera will track all moving lights. In the screen and in the snapshots there will be a "DARK" or "NOISY" marker once the camera comes to it limits

Clone this wiki locally