usage of other cam than raspicam ?

[robbyleh]

Hello Joakim,

I'm glad about your project is documented and public for all of us who are having this problems :-) Thank you very much! I'll keep you up2date with my project.
I'm not really a good programmer in C, I would categorize myself in the box of hobbyists always having fun with that ;-), but out of C i'm definitely technically gifted:-)
My question: can I use a standard webcam with your code? I have a RPI 3 Model B and a used Logitech C270 webcam which is also supported by Raspberry.
Following your REAME.txt I got stuck at this position:
... " command line options used by the raspivid program" ...
After investigating I got the fact, this binarys can be used only with the raspi-cam...
So I installed some kind of software which belongs to standard USB webcams:
... sudo apt-get install fswebcam ...
Now I'm able to take captrure some picture for example with
... fswebcam -r 640x480 --no-banner ~/test.jpg ...
But I have no idea to combine this usb webcam with your code. The last few days planning time in mind I was hoping this code would work also wtih other cameras ...
Thak you in advance.
Robby

[JoakimSoderberg]

Hello Robby,

Thanks for the interest in my project, I look forward to hearing of any progress you make.

Short answer

There is full support to use webcams with the code. But to do that on the raspberry pi it will require some small code changes.

• Quickest solution = Get a native raspberry pi cam, they're quite cheap
• I might get to enabling support for webcams this week.

Long answer

There is full support for using webcams with catcierge. But I have kind of written the code to make use of that on non-Raspberry Pi platforms (Windows, OSX, Linux). The reason for this is that at first when I started on this project, only the original Raspberry Pi was available. And that version was way to weak to support doing the things that catcierge does using a webcam. For that reason the code is written to assume that if you're using Raspberry Pi you're always using the onboard camera.

Currently I only have one compile-time flag that decides if it's an RPI, which turns on everything RPI specific, including the use of the special camera. To enable using a webcam on the Raspberry Pi I would have to create a separate flag for setting the camera either to "generic" (webcam or whatever) or the built-in raspberry cam. I might be able to do that this week.

When I initially wrote this code, OpenCV the library I use for the image recognition tasks did not have native support for that camera (I think later versions now do), so there's some special code to handle that.

OpenCV should work out of the box with any USB webcam in Linux, but since I haven't tried that myself I cannot verify that. This is the functionality I use on all other platforms, and what I need to enable on the RPI platform as well.

One benefit with the built-in raspberry pi camera is that it supports a lot more tweaking of settings.

[robbyleh]

Hi Joakim,

great. I'll get a raspi-cam. Its really cheep.
Currently I examine to use a backlight from an old 17" Screen of an old laptop :-)...
Thanks,
Robby

[JoakimSoderberg]

Hello,

I pushed some changes now that should enable you to use a USB webcam on the Raspberry Pi as well.

To get the latest changes:

git checkout master
git pull --rebase origin master

And then to build follow the build instructions in the README.

I added an extra flag --non_rpi_cam that will look for a "generic" camera like a USB webcam instead of the builtin RPi camera.

If there are multiple attached, you can also specify which one using --camera_index.

Since I have no USB webcam myself, I have not tested this myself. So it would be nice if you could try?

[robbyleh]

Hi Joakim, absolutely great! Thank you for your quick action! I'm not as good in GIT. I followed your instruction, but failed at the first command: ( Do I have to replace master with something else? ) history: robby@catpreyblock:~/Katzenklappe $ cd catcierge/ robby@catpreyblock:~/Katzenklappe/catcierge $ ls -l total 112 -rw-r--r-- 1 robby robby 745 Apr 30 15:22 appveyor.yml drwxr-xr-x 8 robby robby 4096 Apr 30 15:55 build -rwxr-xr-x 1 robby robby 484 Apr 30 15:22 build_userland.sh -rw-r--r-- 1 robby robby 305 Apr 30 15:22 circle.yml drwxr-xr-x 3 robby robby 4096 Apr 30 15:22 cmake -rw-r--r-- 1 robby robby 19780 Apr 30 15:22 CMakeLists.txt drwxr-xr-x 2 robby robby 4096 May 2 00:53 doc -rw-r--r-- 1 robby robby 409 Apr 30 15:22 drmemory-suppress.txt drwxr-xr-x 7 robby robby 4096 Apr 30 15:22 examples drwxr-xr-x 4 robby robby 4096 Apr 30 15:22 extra -rw-r--r-- 1 robby robby 18048 Apr 30 15:22 LICENSE.md drwxr-xr-x 2 robby robby 4096 Apr 30 15:22 prototype -rw-r--r-- 1 robby robby 11896 Apr 30 15:22 README.md drwxr-xr-x 11 robby robby 4096 Apr 30 15:25 rpi_userland drwxr-xr-x 7 robby robby 4096 Apr 30 15:22 src drwxr-xr-x 2 robby robby 4096 Apr 30 15:22 test -rwxr-xr-x 1 robby robby 6105 Apr 30 15:22 valgrind-suppress.txt robby@catpreyblock:~/Katzenklappe/catcierge $ git checkout master M doc/README.md M rpi_userland Already on 'master' Your branch is up-to-date with 'origin/master'. Thanks, Robby

…

Joakim Söderberg ***@***.***> hat am 3. Mai 2017 um 00:50 geschrieben: Hello, I pushed some changes now that should enable you to use a USB webcam on the Raspberry Pi as well. To get the latest changes: ```bash git checkout master git pull --rebase origin master ``` And then to build follow the build instructions in the README. I added an extra flag `--non_rpi_cam` that will look for a "generic" camera like a USB webcam instead of the builtin RPi camera. If there are multiple attached, you can also specify which one using `--camera_index`. Since I have no USB webcam myself, I have not tested this myself. So it would be nice if you could try? -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #20 (comment)

[JoakimSoderberg]

That's not an error, just to make sure you were on the right branch.

However since you have edited the README you will get an error. (I can see that from the line):

M	doc/README.md

So before you do the second command first type:

git stash

and then:

git pull --rebase origin master

(You can get your changes back after that (if you intended to edit it)):

git stash pop

[robbyleh]

Hi Joakim, I compiled the new code. In the --help section I can see the new Option "--no_rpi_cam". I tried to start (my first time, because I stoped the readme at the position of "Verify the camera orientation" ... "raspivid ...". here the output of the first try. I guess I have to do some researches, It seems these are some issues because I did not configure anything. I just created the empty file "/etc/catcierge/catcierge-rpi.cfg", but it did not help. root@catpreyblock:~# catcierge_grabber --non_rpi_cam Catcierge Grabber v0.6.5-64ea8da (64ea8da-tainted) (C) Joakim Soderberg 2013-2016 Library versions: OpenCV v2.4.9 [2017-05-03 09:31:05.495108] Reading Raspberry Pi camera config: /etc/catcierge/catcierge-rpi.cfg [2017-05-03 09:31:05.495647] Raspberry Pi camera: Failed to split input into command line: [2017-05-03 09:31:05.496449] Using default config [2017-05-03 09:31:05.496601] Config path: /etc/catcierge/catcierge.cfg [2017-05-03 09:31:05.497517] Parsed config -------------------------------------------------------------------------------- Settings: -------------------------------------------------------------------------------- General: Startup delay: 0.0 seconds Auto ROI: 0 Show video: 0 Save matches: 1 Save obstruct: 1 Save steps: 1 Highlight match: 0 Lockout dummy: 0 Lockout method: 1 Lock time: 30 seconds Lockout error: 0 (off) Lockout err delay: 3.0 Match timeout: 0 seconds Log file: - No color: 0 No animation: 1 Ok matches needed: 2 Output path: /home/catcierge/images/%match_group_start_time:&Y-&m-&d% Match output path: %output_path%/%match_group_id% Steps output path: %match_output_path%/%matchcur_idx% Matcher type: haar Haar Cascade Matcher: Cascade: /usr/local/share/catcierge/catcierge.xml In direction: Right Min size: 80x80 Equalize histogram: 0 No match is fail: 0 Prey method: Adaptive Prey steps: 2

…

-------------------------------------------------------------------------------- [2017-05-03 09:31:05.508489] Failed to write "4" to /sys/class/gpio/export [2017-05-03 09:31:05.509052] Initialized GPIO pins [2017-05-03 09:31:05.522100] Initialized catcierge image recognition Adding user defined variable: 'to_email test@example.com' Adding user defined variable: 'from_email test2@example.com' Adding user defined variable: 'from_email_passw my_secret' [2017-05-03 09:31:05.522240] Loading output templates: [2017-05-03 09:31:05.522415] Event filters: match_group_done [2017-05-03 09:31:05.522456] catcierge_event (%match_group_id%.json) [2017-05-03 09:31:05.522531] Failed to open input template file "/usr/local/share/catcierge/templates/compose_script.sh.in" [2017-05-03 09:31:05.522594] Failed to load output templates Robby

Joakim Söderberg ***@***.***> hat am 3. Mai 2017 um 01:32 geschrieben: That's not an error, just to make sure you were on the right branch. However since you have edited the README you will get an error. (I can see that from the line): ```bash M doc/README.md ``` So before you do the second command first type: ```bash git stash ``` and then: ```bash git pull --rebase origin master ``` (You can get your changes back after that (if you intended to edit it)): ```bash git stash pop ``` -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #20 (comment)

[JoakimSoderberg]

Answer to your questions

Hmm not sure if I understand what you mean:

I tried to start (my first time, because I stoped the readme at the position of "Verify the camera orientation" ... "raspivid ...".

You are using a webcam on your Raspberry Pi now? Correct?

If that is the case, any settings for the Raspberry Pi camera is not relevant for you. Anything found under --camhelp is something you can ignore

Also, I suggest you don't fiddle with any of those settings as the first thing anyway. Remove that config file completely. You have done something wrong in it anyway. From your log:

[2017-05-03 09:31:05.495108]  Reading Raspberry Pi camera config: /etc/catcierge/catcierge-rpi.cfg
[2017-05-03 09:31:05.495647]  Raspberry Pi camera: Failed to split input into command line:

here the output of the first try.
I guess I have to do some researches, It seems these are some issues because I did not configure anything. I just created the empty file "/etc/catcierge/catcierge-rpi.cfg", but it did not help.

That config is only meant for more advanced settings for the Raspberry camera (not the webcam).
(I only have 2 settings in that file myself, and those are only for flipping the camera image since I happen to have mine mounted upside down).

This is definantly NOT the first step :)

Suggested route

I realise I have not created any "getting started guide", and there's a billion settings and config files to thing about. So, let me suggest the easiest route.

Compile the code as you have done

You can test the executable and play around, it's best to do this at first, to understand how things work.

Here's an example of me running (I use --no_default_config to make sure no default config found on the system is used).

(Note in the examples below my build dir is named build2. That does not matter)

pi@picat ~/dev/catcierge/build2 $ bin/catcierge_grabber --no_default_config

Catcierge Grabber v0.6.5-c04a0b9 (c04a0b9-tainted)
(C) Joakim Soderberg 2013-2016

Library versions:
 OpenCV v2.4.1

Failed to open PID file "/var/run/catcierge.pid"
[2017-05-03 16:46:36.310457]  Reading Raspberry Pi camera config: /etc/catcierge/catcierge-rpi.cfg
[2017-05-03 16:46:36.312266]  Failed to open file /etc/catcierge/catcierge-rpi.cfg
[2017-05-03 16:46:36.317047]  Could not read Raspberry Pi camera config
[2017-05-03 16:46:36.319051]  Using default config
[2017-05-03 16:46:36.319782]  Default config turned off, ignoring: /etc/catcierge/catcierge.cfg
Usage: catcierge_grabber [--help] [--config CONFIG] [--config_rpi CONFIG_RPI] [--no_default_config] [--chuid CHUID]
........................
                         [--roi X Y WIDTH HEIGHT, --auto_roi] {--template_matcher, --haar_matcher}
One of these variables is required:
--template_matcher, --haar_matcher

Here it tells me I need to pick one of the matcher types... Here you ALWAYS want the --haar_matcher, since that's the best and latest. So I add that to the command line. But then I get a new error:

pi@picat ~/dev/catcierge/build2 $ bin/catcierge_grabber --no_default_config --haar_matcher
..........
[2017-05-03 16:49:02.074377]  Haar matcher: No cascade xml specified. Use --cascade
[2017-05-03 16:49:02.075903]  Failed to init Haar Cascade matcher

Which might not be obvious what it is ... But you can find that out in the --help under the Haar cascade matcher settings.

Here I quickly search for it using grep ... The -C10 just says "show 10 lines before and after each matched line":

pi@picat ~/dev/catcierge/build2 $ bin/catcierge_grabber --help | grep -C10 cascade
...
Haar cascade matcher settings:
  Settings for when --haar_matcher is used.
  This is the recommended matcher type.

    --cascade CASCADE                        Path to the haar cascade xml generated by opencv_traincascade.
....

This file is what's used to find the cat head in the picture. One is available in the code under the path ../extra/catcierge.xml relative to our build directory:

pi@picat ~/dev/catcierge/build2 $ bin/catcierge_grabber --no_default_config --haar_matcher --cascade ../extra/catcierge.xml

This time it starts working and you will get a bunch of output like below. Since your camera will be pointing at something random it will probably trigger right away and give you Lockout errors like I get. However if the camera simply is pointing at a white uniform background it will work fine.

pi@picat ~/dev/catcierge/build2 $ bin/catcierge_grabber --no_default_config --haar_matcher --cascade ../extra/catcierge.xml

Catcierge Grabber v0.6.5-c04a0b9 (c04a0b9-tainted)
(C) Joakim Soderberg 2013-2016

Library versions:
 OpenCV v2.4.1

Failed to open PID file "/var/run/catcierge.pid"
[2017-05-03 16:49:52.926438]  Reading Raspberry Pi camera config: /etc/catcierge/catcierge-rpi.cfg
[2017-05-03 16:49:52.928286]  Failed to open file /etc/catcierge/catcierge-rpi.cfg
[2017-05-03 16:49:52.933276]  Could not read Raspberry Pi camera config
[2017-05-03 16:49:52.935659]  Using default config
[2017-05-03 16:49:52.936352]  Default config turned off, ignoring: /etc/catcierge/catcierge.cfg
--------------------------------------------------------------------------------
Settings:
--------------------------------------------------------------------------------
General:
       Startup delay: 0.0 seconds
            Auto ROI: 0
          Show video: 0
        Save matches: 1
       Save obstruct: 0
          Save steps: 0
     Highlight match: 0
       Lockout dummy: 0
      Lockout method: 1
           Lock time: 30 seconds
       Lockout error: 0 (off)
   Lockout err delay: 3.0
       Match timeout: 0 seconds
            Log file: -
            No color: 0
        No animation: 0
   Ok matches needed: 2
         Output path: .

        Matcher type: haar
Haar Cascade Matcher:
           Cascade: ../extra/catcierge.xml
      In direction: Right
          Min size: 80x80
Equalize histogram: 0
  No match is fail: 0
       Prey method: Adaptive
        Prey steps: 2

RFID:
          Inner RFID: -
          Outer RFID: -
     Lock on no RFID: 0
      RFID lock time: 0.00 seconds
        Allowed RFID: -
--------------------------------------------------------------------------------
[2017-05-03 16:49:52.943196]  Failed to write "4" to /sys/class/gpio/export
[2017-05-03 16:49:52.946046]  Initialized GPIO pins
[2017-05-03 16:49:52.989180]  Initialized catcierge image recognition
[2017-05-03 16:49:52.990018]  Initialized output templates
[2017-05-03 16:49:52.990709]  Initialized RFID readers
[2017-05-03 16:49:53.404457]  Starting detection!
[2017-05-03 16:49:53.405299]  [Initial] -> [Waiting]
[2017-05-03 16:49:53.426211]  Startup delay of 0.00 seconds has ended!
[2017-05-03 16:49:53.428574]  Something in frame! Start matching...
[2017-05-03 16:49:53.463652]
[2017-05-03 16:49:53.464510]  === Match group id: cb4f5f88f7587a185c31e50456b89af4140be768 ===
[2017-05-03 16:49:53.465146]
[2017-05-03 16:49:53.465982]  [Waiting] -> [Matching]
[2017-05-03 16:49:53.530760]  Match in - No cat head detected (4a4b0af15c7d051c76956d92180dd81248c8f665)
[2017-05-03 16:49:53.601247]  Match in - No cat head detected (c2e3e6f47c8dde32ce7c3d962af9aa5c9339a89a)
[2017-05-03 16:49:53.668535]  Match in - No cat head detected (7792a19d6f1dca03a489a208d1bd1f3ff9c2390)
[2017-05-03 16:49:53.736250]  Match in - No cat head detected (bd9caefce07d8fb2cf746ae218d9beed49e3b2d9)
[2017-05-03 16:49:53.737675]  !!! Match group vetoed match success: No head found in any image !!!
[2017-05-03 16:49:53.743001]  Lockout! 0 out of 4 matches failed (for 30 seconds).
[2017-05-03 16:49:53.743234]  Waiting for lockout timer only (Lockout method 1)
[2017-05-03 16:49:53.743376]  [Matching] -> [Lockout]
[2017-05-03 16:49:53.744355]  Saving image ./match__2017-05-03_16_49_53.496674__1.png
[2017-05-03 16:49:53.759913]  Saving image ./match__2017-05-03_16_49_53.566832__2.png
[2017-05-03 16:49:53.771090]  Saving image ./match__2017-05-03_16_49_53.634172__3.png
[2017-05-03 16:49:53.787343]  Saving image ./match__2017-05-03_16_49_53.701802__4.png
[2017-05-03 16:49:55.173878]  Received SIGINT, stopping...

At the end there I pressed ctrl+c on the keyboard to quit. Otherwise it will keep spamming and saving images.

Ofcourse specifying all the settings like this on the command line is a bit tedious. Instead of doing that you can create a config file. By default catcierge will look for one at /etc/catcierge/catcierge.cfg. But you can create it wherever you want and specify the path using --config.

Options:
    -h, --help                               Show this help
    -c, --config CONFIG                      Path to the catcierge config file. Catcierge looks for /etc/catcierge/catcierge.cfg
                                             by default, unless --no_default_config has been specified. Setting this overrides
                                             the default config.
                                             NOTE: Options for the raspberry pi camera settings --rpi, cannot be used in this
                                             config. Please see --config_rpi and --camhelp for details.
    --config_rpi CONFIG_RPI                  Path to config file for raspberry pi camera settings. See --camhelp for details.
                                             Default location: /etc/catcierge/catcierge-rpi.cfg
    --no_default_config                      Do not load the default config (/etc/catcierge/catcierge.cfg) if none is specified
                                             using --config

NOTE --config_rpi is something different, and only meant for advanced settings for the onboard raspberry pi camera.

But it's not advisable to run the final setup like this!
To facilitate a "proper" installation I have made it so that you can build a debian package.

Build a debian package

pwd             # Make sure you are in the `build/` directory.
cmake ..       # Make sure to re-generate the Make files if needed.
make           # And make sure our build is up to date.

# Now we can build the debian package:
cpack -G DEB

You should see something like this:

CPack: Create package using DEB
CPack: Install projects
CPack: - Run preinstall target for: catcierge
CPack: - Install project: catcierge
CPack: Create package
CPack: - package: /home/pi/dev/catcierge/build3/catcierge-0.6.5-64ea8da-armhf.deb generated.

This debian package. will include an example config files that will be placed under /etc/catcierge/catcierge-example.cfg, you get some step by step instructions on how to proceed as well.

It will also help you setting up catcierge_grabber to run as a service. So when you reboot it will start running immediately. It will also setup the GPIO pins in the proper mode at boot (the pin that will be used to trigger the lock being the important one).

So now that you have built the debian package you can install it:

sudo dpkg -i catcierge-0.6.5-64ea8da-armhf.deb

You should now get some more instructions on what more to do.

Here's a full list of the files it will install:

$ dpkg -c catcierge-0.6.5-64ea8da-armhf.deb
drwxr-xr-x root/root         0 2017-05-03 13:40 ./lib/
drwxr-xr-x root/root         0 2017-05-03 13:40 ./lib/systemd/
drwxr-xr-x root/root         0 2017-05-03 13:40 ./lib/systemd/system/
-rw-r--r-- root/root       293 2016-07-03 21:16 ./lib/systemd/system/catcierge.service
-rw-r--r-- root/root       159 2016-07-03 21:16 ./lib/systemd/system/catcierge_rpi_gpio.service
drwxr-xr-x root/root         0 2017-05-03 13:40 ./etc/
drwxr-xr-x root/root         0 2017-05-03 13:40 ./etc/catcierge/
-rw-r--r-- root/root      2771 2017-05-02 23:30 ./etc/catcierge/catcierge-example.cfg
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/local/
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/local/share/
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/local/share/catcierge/
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/local/share/catcierge/templates/
-rw-r--r-- root/root      2586 2016-07-21 13:56 ./usr/local/share/catcierge/templates/event.json
-rw-r--r-- root/root     17747 2016-02-22 02:09 ./usr/local/share/catcierge/templates/match_group.json
-rw-r--r-- root/root     17774 2016-04-29 01:53 ./usr/local/share/catcierge/templates/match_group_done_full.json
-rw-r--r-- root/root       204 2016-04-29 01:53 ./usr/local/share/catcierge/templates/state_change.json
-rw-r--r-- root/root      8903 2016-07-20 14:29 ./usr/local/share/catcierge/catcierge-compose.py
-rw-r--r-- root/root     66096 2016-02-22 02:09 ./usr/local/share/catcierge/catcierge.xml
-rw-r--r-- root/root      2243 2016-02-22 02:09 ./usr/local/share/catcierge/catcierge-twitter.py
-rw-r--r-- root/root      4892 2016-08-01 01:39 ./usr/local/share/catcierge/catcierge-sendmail-new.py
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/local/share/catcierge/fonts/
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/local/share/catcierge/fonts/alex-brush/
-rw-r--r-- root/root     49020 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/alex-brush/AlexBrush-Regular.ttf
-rw-r--r-- root/root      4392 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/alex-brush/SIL Open Font License.txt
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/local/share/catcierge/fonts/source-code-pro/
-rw-r--r-- root/root     88912 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/source-code-pro/SourceCodePro-Black.otf
-rw-r--r-- root/root     90032 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/source-code-pro/SourceCodePro-Semibold.otf
-rw-r--r-- root/root     89596 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/source-code-pro/SourceCodePro-Medium.otf
-rw-r--r-- root/root     92676 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/source-code-pro/SourceCodePro-Bold.otf
-rw-r--r-- root/root     88600 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/source-code-pro/SourceCodePro-Light.otf
-rw-r--r-- root/root     85084 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/source-code-pro/SourceCodePro-ExtraLight.otf
-rw-r--r-- root/root      4525 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/source-code-pro/SIL Open Font License.txt
-rw-r--r-- root/root     90056 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/source-code-pro/SourceCodePro-Regular.otf
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/local/share/catcierge/fonts/Asana-Math/
-rw-r--r-- root/root    428892 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/Asana-Math/Asana-Math.otf
-rw-r--r-- root/root    499052 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/Asana-Math/Asana-Math.ttf
-rw-r--r-- root/root      1591 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/Asana-Math/FontLog.txt
-rw-r--r-- root/root       922 2016-02-22 02:09 ./usr/local/share/catcierge/fonts/Asana-Math/README
-rw-r--r-- root/root       374 2016-07-03 21:16 ./usr/local/share/catcierge/catcierge_rpi_gpio.sh
drwxr-xr-x root/root         0 2017-05-03 13:40 ./usr/local/bin/
-rwxr-xr-x root/root    454576 2017-05-03 13:40 ./usr/local/bin/catcierge_rfid_tester
-rwxr-xr-x root/root    468492 2017-05-03 13:40 ./usr/local/bin/catcierge_fsm_tester
-rwxr-xr-x root/root    468244 2017-05-03 13:40 ./usr/local/bin/catcierge_tester
-rwxr-xr-x root/root    468640 2017-05-03 13:40 ./usr/local/bin/catcierge_grabber
-rwxr-xr-x root/root    464444 2017-05-03 13:40 ./usr/local/bin/catcierge_bg_tester

P.S. If you write your messages via github instead, you can use formatting for your code and such, which makes things a bit easier to read.

[JoakimSoderberg]

Oh yea, and you should use --non_rpi_cam unlike me in the above examples

Also, once you have installed the debian package and followed the instructions that you were prompted with, catcierge should be setup to run as a service and can be controlled using systemctl.

So for example to restart the service:

sudo systemctl restart catcierge

Here's a guide on how systemctl works:
https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units

None of this is foolproof, since I am the only one who has ever used it. So ask if you run into any issues, and please provide as much context as you can so I can easily understand what you have done.

[robbyleh]

Hey Joakim, you answers are so much in detail, wowww. Amazing... Don't forget, I already read your README.txt files ;-). So the DEB packaging I already did :-) Thank you for all your time you spend for help ... I'll continue around midnight with the code stuff. Recent hour I finished the backlight (made from a Laptop Display). See attached picture. It's really perfect I think... Robby Will let you know about my progress soon...

…

Joakim Söderberg ***@***.***> hat am 3. Mai 2017 um 19:06 geschrieben: Oh yea, and you should use `--non_rpi_cam` unlike me in the above examples Also, once you have installed the debian package and followed the instructions that you were prompted with, **catcierge** should be setup to run as a service and can be controlled using `systemctl`. So for example to restart the service: ```bash sudo systemctl restart catcierge ``` Here's a guide on how systemctl works: https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units None of this is foolproof, since I am the only one who has ever used it. So ask if you run into any issues, and please provide as much context as you can so I can easily understand what you have done. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #20 (comment)

[robbyleh]

Hi Joakim, it works !!! ( with usb webcam ) I made a silhouette of paper. With many trys I could get matches with and without pray. I'll construct the Box that all is fixed and correct in place, Furthermore I have to create a pushmagnet lock. I guess I can create it byself. I also wind a lot of loudspeaker coils in the past. But I'll also take a look on the marked what is available there... Robby with pray: [2017-05-04 01:09:25.350873] [Waiting] -> [Matching] [2017-05-04 01:09:25.414932] Match in - No cat head detected (b98bd4dfeccc157a915e60e23275adb8e35ef5) [2017-05-04 01:09:25.471685] Match in - No cat head detected (15e0525b533aa0be3573e9ed3a24d38cc262a61a) [2017-05-04 01:09:25.531324] No Match in - Prey detected (a6267143941451033e1174f8155cacab2024b1c7) [2017-05-04 01:09:25.579501] Match in - No cat head detected (e69326786bd27ae788842d9a7c05c13cebb3c538) [2017-05-04 01:09:25.580095] Everything OK! (3 out of 4 matches succeeded) Door kept open... [2017-05-04 01:09:25.580309] [Matching] -> [Keep open] [2017-05-04 01:09:25.580363] Saving image ./match__2017-05-04_01_09_25.372290__1.png [2017-05-04 01:09:25.593410] Saving image ./match__2017-05-04_01_09_25.430256__2.png [2017-05-04 01:09:25.606085] Saving image ./match_fail_2017-05-04_01_09_25.493738__3.png [2017-05-04 01:09:25.620202] Saving image ./match__2017-05-04_01_09_25.541922__4.png [2017-05-04 01:09:27.453371] Frame is clear, start successful match timer... [2017-05-04 01:09:27.453532] Go back to waiting... [2017-05-04 01:09:27.453603] [Keep open] -> [Waiting] [2017-05-04 01:09:34.813060] Received SIGINT, stopping... without pray: [2017-05-04 01:07:14.355767] [Waiting] -> [Matching] [2017-05-04 01:07:14.410116] Match in - No cat head detected (8af5254a541eac8dfd11c3d04a50b1fa7ff5ded8) [2017-05-04 01:07:14.457036] Match in - No cat head detected (a71c64de83229debb3a2172aab431f522f979fb4) [2017-05-04 01:07:14.507544] Match in - No prey detected (6e84b110fef2418ab8ad0da22edb24d4359832e2) [2017-05-04 01:07:14.558071] Match in - No prey detected (6d77bcbf9f60bab136076a651da21ff3c4bfaec4) [2017-05-04 01:07:14.558613] Everything OK! (4 out of 4 matches succeeded) Door kept open... [2017-05-04 01:07:14.558793] [Matching] -> [Keep open] [2017-05-04 01:07:14.558831] Saving image ./match__2017-05-04_01_07_14.372566__1.png [2017-05-04 01:07:14.571499] Saving image ./match__2017-05-04_01_07_14.419549__2.png [2017-05-04 01:07:14.585537] Saving image ./match__2017-05-04_01_07_14.469966__3.png [2017-05-04 01:07:14.598250] Saving image ./match__2017-05-04_01_07_14.520507__4.png [2017-05-04 01:07:16.190729] Frame is clear, start successful match timer... [2017-05-04 01:07:16.190821] Go back to waiting... [2017-05-04 01:07:16.190839] [Keep open] -> [Waiting] perfect :-))))

…

Joakim Söderberg ***@***.***> hat am 3. Mai 2017 um 19:06 geschrieben: Oh yea, and you should use `--non_rpi_cam` unlike me in the above examples Also, once you have installed the debian package and followed the instructions that you were prompted with, **catcierge** should be setup to run as a service and can be controlled using `systemctl`. So for example to restart the service: ```bash sudo systemctl restart catcierge ``` Here's a guide on how systemctl works: https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units None of this is foolproof, since I am the only one who has ever used it. So ask if you run into any issues, and please provide as much context as you can so I can easily understand what you have done. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #20 (comment)

[JoakimSoderberg]

Nice you got it working! :)

Btw you forgot to attach the image you referred to. I'd love to see your progress.

Furthermore I have to create a pushmagnet lock. I guess I can create it byself. I also wind a lot of loudspeaker coils in the past. But I'll also take a look on the marked what is available there...

You mean a solenoid? That's at least what I use. Sounds interesting to make one on your own.

However if possible make sure it is quite strong. Right now my cat has broken the one I have. When it was subzero temperatures she pushed on the door when it had accidentally gotten locked, and because the shaft of it got very brittle it broke :)

---

Some tips on building your enclosure:

• Keep light pollution down. Make sure you get a uniform light setup for any time of day, if it's pitch black or full sun light.

• Build the corridor where the cat enters as an "L" .... So that the cat cannot run too fast by the camera. An added benefit is that wind cannot blow straight into the door either.

• If you ever get subzero degrees where you live, you should build an enclosure for your camera + have some sort of heating for that (I can provide pics of my setup, using a cheap. If you don't do this and use the raspberry pi camera, it will stop working (not break, but produces garbage at those temperatures). This might be different for your webcam of course.

• If you ever get power outages (I live in a small village, so it happens), make sure you have a battery backup for it. I use this: https://www.modmypi.com/raspberry-pi/breakout-boards/pi-modules/ups-pico ... If you don't have this, its just a matter of time before you have a broken SD card. With this, my cat door has been running non stop for 1.5 years now. (I've had SD cards die because of this before that).

[JoakimSoderberg]

This is a picture of a Spiders Ass:

Here is a picture of it camouflaging itself by sitting on the only dark spot nearby :) This was spamming the cat door the entire night, this week... Stuff like this happens at times, but not super often.

[robbyleh]

Ohh, the backlight picture I forgot to attach somehow. Here it is. Robby Von meinem iPhone gesendet

…

Am 04.05.2017 um 01:21 schrieb Robby Lehmann ***@***.***>: Hi Joakim, it works !!! ( with usb webcam ) I made a silhouette of paper. With many trys I could get matches with and without pray. I'll construct the Box that all is fixed and correct in place, Furthermore I have to create a pushmagnet lock. I guess I can create it byself. I also wind a lot of loudspeaker coils in the past. But I'll also take a look on the marked what is available there... Robby with pray: [2017-05-04 01:09:25.350873] [Waiting] -> [Matching] [2017-05-04 01:09:25.414932] Match in - No cat head detected (b98bd4dfeccc157a915e60e23275adb8e35ef5) [2017-05-04 01:09:25.471685] Match in - No cat head detected (15e0525b533aa0be3573e9ed3a24d38cc262a61a) [2017-05-04 01:09:25.531324] No Match in - Prey detected (a6267143941451033e1174f8155cacab2024b1c7) [2017-05-04 01:09:25.579501] Match in - No cat head detected (e69326786bd27ae788842d9a7c05c13cebb3c538) [2017-05-04 01:09:25.580095] Everything OK! (3 out of 4 matches succeeded) Door kept open... [2017-05-04 01:09:25.580309] [Matching] -> [Keep open] [2017-05-04 01:09:25.580363] Saving image ./match__2017-05-04_01_09_25.372290__1.png [2017-05-04 01:09:25.593410] Saving image ./match__2017-05-04_01_09_25.430256__2.png [2017-05-04 01:09:25.606085] Saving image ./match_fail_2017-05-04_01_09_25.493738__3.png [2017-05-04 01:09:25.620202] Saving image ./match__2017-05-04_01_09_25.541922__4.png [2017-05-04 01:09:27.453371] Frame is clear, start successful match timer... [2017-05-04 01:09:27.453532] Go back to waiting... [2017-05-04 01:09:27.453603] [Keep open] -> [Waiting] [2017-05-04 01:09:34.813060] Received SIGINT, stopping... without pray: [2017-05-04 01:07:14.355767] [Waiting] -> [Matching] [2017-05-04 01:07:14.410116] Match in - No cat head detected (8af5254a541eac8dfd11c3d04a50b1fa7ff5ded8) [2017-05-04 01:07:14.457036] Match in - No cat head detected (a71c64de83229debb3a2172aab431f522f979fb4) [2017-05-04 01:07:14.507544] Match in - No prey detected (6e84b110fef2418ab8ad0da22edb24d4359832e2) [2017-05-04 01:07:14.558071] Match in - No prey detected (6d77bcbf9f60bab136076a651da21ff3c4bfaec4) [2017-05-04 01:07:14.558613] Everything OK! (4 out of 4 matches succeeded) Door kept open... [2017-05-04 01:07:14.558793] [Matching] -> [Keep open] [2017-05-04 01:07:14.558831] Saving image ./match__2017-05-04_01_07_14.372566__1.png [2017-05-04 01:07:14.571499] Saving image ./match__2017-05-04_01_07_14.419549__2.png [2017-05-04 01:07:14.585537] Saving image ./match__2017-05-04_01_07_14.469966__3.png [2017-05-04 01:07:14.598250] Saving image ./match__2017-05-04_01_07_14.520507__4.png [2017-05-04 01:07:16.190729] Frame is clear, start successful match timer... [2017-05-04 01:07:16.190821] Go back to waiting... [2017-05-04 01:07:16.190839] [Keep open] -> [Waiting] perfect :-)))) > Joakim Söderberg ***@***.***> hat am 3. Mai 2017 um 19:06 geschrieben: > > > Oh yea, and you should use `--non_rpi_cam` unlike me in the above examples > > Also, once you have installed the debian package and followed the instructions that you were prompted with, **catcierge** should be setup to run as a service and can be controlled using `systemctl`. > > So for example to restart the service: > > ```bash > sudo systemctl restart catcierge > ``` > > Here's a guide on how systemctl works: > https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units > > None of this is foolproof, since I am the only one who has ever used it. So ask if you run into any issues, and please provide as much context as you can so I can easily understand what you have done. > > -- > You are receiving this because you authored the thread. > Reply to this email directly or view it on GitHub: > #20 (comment)

[JoakimSoderberg]

Ah I think it's because you're trying to attach it in a mail. Seems like github throws it away. You need to open the webpage and add it there I think.

[robbyleh]

Hi,
here the photo I missed. ( All my recent comments I sent by email, that's the reason, that my attachments were gone)
The new created Backlight (made of an 2010 Sony Laptop Display)....