Configuring control of PTZ unclear?

[eiger3970]

Hello, I'm working on taking control of PTZ from ZM, however the configuration is unclear.
ZM: version 1.36.33
Camera: IPG-7920PSS-AI

ZM is showing a live feed.
I navigated to ZM -> Options -> Control -> a page asked for source path and settings from memory.
However now when navigating to ZM -> Options -> Control -> a page opens with a list of cameras from 3S Domo N5071 to WanscamPT.
I have ticked the checked box ONVIF Camera, but there's no option to Save?

[eiger3970]

Reading documents, but unclear on the steps to control the camera?

https://koshka.ddns.net/?p=194
https://zoneminder.readthedocs.io/en/st ... ntrol.html
VM -> Terminal -> /usr/share/perl5/ZoneMinder/Control/onvif.pm -> lines 67-70 have example Control Address values. A bit unclear what to do?

[eiger3970]

Tried a number of configurations:
ZM v1.36.33 -> Console -> 192.168.1.180 -> Control ->
Control Type: ONVIF, Control Address: admin:80@192.168.1.180
Control Type: ONVIF, Control Address: admin:554@192.168.1.180
Control Type: ONVIF, Control Address: admin:6060@192.168.1.180
Control Type: ONVIF, Control Address: admin:6066@192.168.1.180
Control Type: PelcoD ffmpeg, Control Address: admin:80@192.168.1.180
Control Type: PelcoD ffmpeg, Control Address: admin:554@192.168.1.180
Control Type: PelcoD ffmpeg, Control Address: admin:6060@192.168.1.180
Control Type: PelcoD ffmpeg, Control Address: admin:6066@192.168.1.180
Control Type: PelcoD local, Control Address: admin:80@192.168.1.180
Control Type: PelcoD local, Control Address: admin:554@192.168.1.180
Control Type: PelcoD local, Control Address: admin:6060@192.168.1.180
Control Type: PelcoD local, Control Address: admin:6066@192.168.1.180
Control Type: Pelcop ffmpeg, Control Address: admin:80@192.168.1.180
Control Type: Pelcop ffmpeg, Control Address: admin:554@192.168.1.180
Control Type: Pelcop ffmpeg, Control Address: admin:6060@192.168.1.180
Control Type: Pelcop ffmpeg, Control Address: admin:6066@192.168.1.180
Control Type: Pelcop local, Control Address: admin:80@192.168.1.180
Control Type: Pelcop local, Control Address: admin:554@192.168.1.180
Control Type: Pelcop local, Control Address: admin:6060@192.168.1.180
Control Type: Pelcop local, Control Address: admin:6066@192.168.1.180

This is the camera seen directly from browser 192.168.1.180, not via ZM: (I attached 2 files, but ZM forum is duplicating attachment 1 for some reason? The attachments and the code show 2 files, not 3?)

Screenshot from 2024-03-23 18-33-57.png (83.08 KiB) Viewed 932 times

Screenshot from 2024-03-23 18-33-57.png (83.08 KiB) Viewed 932 times

[dougmccrary]

Maybe I'm just not understanding what you're trying to do, but I'm afraid you've gone down a rabbit hole...
What you're looking at is the list of known cameras and what the script for it is capable of.
You select one of those for a given camera, like so:

Screenshot 2024-03-23 at 02-34-00 ZM - Monitor - Garage.png (60.17 KiB) Viewed 927 times

Most modern cameras support onvif, and the onvif selection will work, at least a little.

HTH...

[eiger3970]

Thanks, but unfortunately, the rabbit hole has become the abyss of death.
I hired some remote support, but they had no clue, just hacking away and working off my navigation and use of the software.
I woke up in the morning and the always in focus camera is somehow now out of focus.

I was unable to refocus the camera, so I selected Restore Defaults.
Now I can't access the camera directly via the browser at 192.168.1.180.
Terminal output shows 192.168.1.180 is there, but no more access?

Code: Select all

linuxmint@linuxmint:~$ arp -a
? (192.168.1.100) at 1c:ca:e3:77:c5:53 [ether] on br0
? (192.168.1.147) at 52:54:00:a1:d1:e2 [ether] on br0
? (192.168.1.180) at <incomplete> on br0
? (192.168.1.1) at <incomplete> on br0
? (192.168.1.160) at 3c:2a:f4:60:b5:7b [ether] on br0
? (192.168.1.210) at b4:fb:e4:80:77:db [ether] on br0
? (192.168.1.146) at 52:54:00:ac:44:b5 [ether] on br0
_gateway (192.168.1.170) at 52:54:00:09:d3:92 [ether] on br0
linuxmint@linuxmint:~$ nmap 192.168.1.180
Starting Nmap 7.80 ( https://nmap.org ) at 2024-03-24 09:43 AEST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.04 seconds
linuxmint@linuxmint:~$ nmap -Pn 192.168.1.180
Starting Nmap 7.80 ( https://nmap.org ) at 2024-03-24 09:43 AEST
Nmap scan report for 192.168.1.180
Host is up (0.049s latency).
All 1000 scanned ports on 192.168.1.180 are filtered

Nmap done: 1 IP address (1 host up) scanned in 5.94 seconds
linuxmint@linuxmint:~$ ping 192.168.1.180
PING 192.168.1.180 (192.168.1.180) 56(84) bytes of data.
From 192.168.1.120 icmp_seq=1 Destination Host Unreachable
From 192.168.1.120 icmp_seq=2 Destination Host Unreachable
From 192.168.1.120 icmp_seq=3 Destination Host Unreachable
From 192.168.1.120 icmp_seq=4 Destination Host Unreachable
From 192.168.1.120 icmp_seq=5 Destination Host Unreachable
From 192.168.1.120 icmp_seq=6 Destination Host Unreachable
^C
--- 192.168.1.180 ping statistics ---
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6142ms
pipe 3

[dougmccrary]

ugh.
Couple things - can you give a link to the specs/manual/where you got this thing?
And, sometimes these things need an app to get them initially set up. If that's the case, have you tried it?
Given the focus problem, it may have just failed such that it can't re-initialize. Have you tried killing power to it to reset?

[eiger3970]

Model:
IPG-7920PSS-AI
MAC address:
5a:58:39:d5:2a:8c
Name:
Software:
IPC
Sticker on back of camera:
JK-PHD46??324AERS
Module: 324 ??N POE
IP: DHCP
Username: admin
Password: blank
Bar code: AF20201016-02
Serial number:
I207414A5AEC41E0CED4F23
Software version:
1.0.10-20200805CN_PT
Web version:
19.08.01.6929

I don't think the camera came with an app, just a web browser to configure it.
I power cycled the camera and now my Desktop's Terminal on the LAN can ping 192.168.1.180.
However the web borwser can't reach the site http://192.168.1.180.
Today, the Desktop cannot ping 192.168.1.180 nor browse?

Code: Select all

linuxmint@linuxmint:~$ arp -a
? (192.168.1.122) at 40:6c:8f:2e:7b:18 [ether] on br0
? (192.168.1.147) at 52:54:00:a1:d1:e2 [ether] on br0
? (192.168.1.160) at 3c:2a:f4:60:b5:7b [ether] on br0
_gateway (192.168.1.170) at 52:54:00:09:d3:92 [ether] on br0
? (192.168.1.180) at <incomplete> on br0
? (192.168.1.210) at b4:fb:e4:80:77:db [ether] on br0
linuxmint@linuxmint:~$ ping 192.168.1.180
PING 192.168.1.180 (192.168.1.180) 56(84) bytes of data.
From 192.168.1.120 icmp_seq=1 Destination Host Unreachable
^C
--- 192.168.1.180 ping statistics ---
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6138ms
pipe 4
linuxmint@linuxmint:~$ dig 192.168.1.180

; <<>> DiG 9.18.18-0ubuntu0.22.04.2-Ubuntu <<>> 192.168.1.180
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56165
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;192.168.1.180.			IN	A

;; AUTHORITY SECTION:
.			86391	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2024032702 1800 900 604800 86400

;; Query time: 56 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Mar 28 10:12:40 AEST 2024
;; MSG SIZE  rcvd: 117

[dougmccrary]

I power cycled the camera and now my Desktop's Terminal on the LAN can ping 192.168.1.180.
However the web borwser can't reach the site http://192.168.1.180.
Today, the Desktop cannot ping 192.168.1.180 nor browse?

Starting to sound like possible power supply problem - can you replace/change?

[eiger3970]

No, it's an old camera.
Power has always been fine.
Something I don't understand is:
Desktop on the same LAN -> Terminal -> arp -a

Code: Select all

linuxmint@linuxmint:~$ arp -a
? (192.168.1.122) at 40:6c:8f:2e:7b:18 [ether] on br0
? (192.168.1.147) at 52:54:00:a1:d1:e2 [ether] on br0
? (192.168.1.160) at 3c:2a:f4:60:b5:7b [ether] on br0
_gateway (192.168.1.170) at 52:54:00:09:d3:92 [ether] on br0
? (192.168.1.180) at <incomplete> on br0
? (192.168.1.210) at b4:fb:e4:80:77:db [ether] on br0
? (192.168.1.100) at <incomplete> on br0

Camera used to be 192.168.1.180, however browser won't load page http://192.168.1.180
Intercom camera used to be 192.168.1.100, however browser won't load page http://192.168.1.100.
So, I ran an intercom camera support link (entering the username, password and security token) to find the ip address and it said 192.168.1.124.
Ran the arp -a again after the support link and 192.168.1.124 appears and is connected.
Is there some type of network fix trick to fix up any issues with the security camera's IP address?

Code: Select all

linuxmint@linuxmint:~$ arp -a
? (192.168.1.122) at 40:6c:8f:2e:7b:18 [ether] on br0
? (192.168.1.147) at 52:54:00:a1:d1:e2 [ether] on br0
? (192.168.1.160) at 3c:2a:f4:60:b5:7b [ether] on br0
_gateway (192.168.1.170) at 52:54:00:09:d3:92 [ether] on br0
? (192.168.1.180) at <incomplete> on br0
? (192.168.1.210) at b4:fb:e4:80:77:db [ether] on br0
? (192.168.1.100) at <incomplete> on br0
? (192.168.1.124) at 1c:ca:e3:77:c5:53 [ether] on br0

Code: Select all

xmint@linuxmint:~$ dig 192.168.1.124

; <<>> DiG 9.18.18-0ubuntu0.22.04.2-Ubuntu <<>> 192.168.1.124
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27757
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;192.168.1.124.			IN	A

;; AUTHORITY SECTION:
.			86362	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2024032800 1800 900 604800 86400

;; Query time: 68 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Mar 28 18:53:46 AEST 2024
;; MSG SIZE  rcvd: 117

linuxmint@linuxmint:~$ dig 192.168.1.180

; <<>> DiG 9.18.18-0ubuntu0.22.04.2-Ubuntu <<>> 192.168.1.180
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45896
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;192.168.1.180.			IN	A

;; AUTHORITY SECTION:
.			86320	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2024032800 1800 900 604800 86400

;; Query time: 140 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Mar 28 18:53:59 AEST 2024
;; MSG SIZE  rcvd: 117

[eiger3970]

Solved, found the new IP address.
Password failed, don't know the default and admin failed.
Just tried no password and I'm in again?

So, back to setting up ZM and troubleshooting ptz control via zm.
I understand the zm controls are not in that giant list of cameras, so I'll read up and play around.

[eiger3970]

Post Sat Mar 23, 2024 8:39 pm shows some configuration.
Control Type: Netcat ONVIF
Control Device: /onvif/ptz_service
Control Address: 192.168.1.214:8080/onfiv/ptz_service

Additional to the configurations I tried in Sat Mar 23, 2024 7:10 pm, I just tried this:
Zone Minder v1.36.33 -> Control ->
Control Type: ONVIF Camera
Control Device: 1
Control Address: 192.168.1.180:8080/onvif/ptz_service
Auto Stop Timout: blank
Return Location: None

Where can I find configuration for my camera?

The ZoneMinder https://zoneminder.readthedocs.io/en/st ... ntrol.htmldocumentation show no configuration?

Desktop -> Browser: 192.168.1.180/rsmain.html -> camera shows PTZ Settings:
PTZ: Open
PTZ Address: 1
Bitrate: 115200
PTZ Step: 5
PTZ Protocol: PelcoD

ZoneMinder -> Source -> source Path shows: rtsp://<userName>:<password>@192.168.1.180/main.html?first=0

[mikb]

Camera used to be 192.168.1.180, however browser won't load page http://192.168.1.180
Intercom camera used to be 192.168.1.100, however browser won't load page http://192.168.1.100.
So, I ran an intercom camera support link (entering the username, password and security token) to find the ip address and it said 192.168.1.124.
Ran the arp -a again after the support link and 192.168.1.124 appears and is connected.
Is there some type of network fix trick to fix up any issues with the security camera's IP address?

Congratulations, you just discovered what the "D" in DHCP stands for. Dynamic.

A little *too* dynamic, sometimes.

You need to either set the camera's setting from "IP: DHCP" to "IP: Static" and nail it down to an IP address of your choice. That's my preferred option.

Or you need to find your DHCP server (something on your network is answering an handing out addresses) and set it to either keep the IP address for a long time (e.g. a permanent lease) so once it's been dynamically assigned it will stick. Or, tell the DHCP server to associate that MAC address with a particular IP address so it will always answer with that address.

If you have TWO DHCP servers in your network, it's possible that one (or the other) is already doing that -- but it depends which one gets to respond first. Just a warning

[eiger3970]

Thanks, DHCP and Static IP is quite clear and a non issue.
I wasn't aware the camera reset removed the set static ip and had reset the camera's static IP to 192.168.1.180.

The main and outstanding issue is finding whatever the Control Address is for the camera's PTZ control via ZM.

[dougmccrary]

So the camera's in focus again?
Have you tried any of the onvif tools out there or in zm?

[eiger3970]

Yes, the reset camera is in focus, albeit upside down as the camera is hanging from a ceiling upside down, which I fixed by setting the local camera settings.

I tried
1:
ONVIFViewer, but it doesn't load from Linux Mint 21.3 Software Manager.
Downloaded ONVIFViewer https://sourceforge.net/projects/onvifd ... t/download but directory EventsConsole has no info on how to make it run?
Git clone of https://gitlab.com/capermeijn/onvifviewer.git won't run, error:

Code: Select all

-- Found Gettext: /usr/bin/msgmerge (found suitable version "0.21", minimum required is "0.19") 
CMake Error at CMakeLists.txt:46 (find_package):
  Could not find a package configuration file provided by "ECM" (requested
  version 5.44.0) with any of the following names:

    ECMConfig.cmake
    ecm-config.cmake

  Add the installation prefix of "ECM" to CMAKE_PREFIX_PATH or set "ECM_DIR"
  to a directory containing one of the above files.  If "ECM" provides a
  separate development package or SDK, be sure it has been installed.

2:
iSpy software installed quite nicely, however confused also how to configure its PTZ control?
iSpy -> General -> Name: Camera1 -> Source Type: ONVIF -> Location: None -> Groups: blank -> select OK -> error: Configure the Source Type (general).
If I change Source Type to Network Camera and enter the live path http://192.168.1.180/main.html?first=0 iSpy shows error:
Camera1 NETWORK Reader: Camera1: OPEN_INPUT: Invalid data found when processing input.
Camera1 shows live video when I use the same URL as ZoneMinder: [url]rtsp://admin:<password>@192.168.1.180/main.html?first=0[/url]