reComputer Industrial J3011 POE Camera on PSE Port

Products & Technology Single Board Computers
#1

Realtek Ethernet (PSE) shows “connected” for IPv4 manual setting (192.168.0.117) and camera is being correctly powered over cable and is pingable
using
Reolink POE IP camera (A14) – maybe suggest another camera ?

Tested with something like this and it fails
BUT when connected to router (and separately powered) works correctly

import cv2

#print("Before URL")
cap = cv2.VideoCapture('rtsp://admin:[email protected]:554/)
#print("After URL")

while True:

    #print('About to start the Read command')
    ret, frame = cap.read()
    #print('About to show frame of Video.')
    cv2.imshow("Capturing",frame)
    #print('Running..')

    if cv2.waitKey(1) & 0xFF == ord('q'):
        break

cap.release()
cv2.destroyAllWindows()

alan@orin-nano-JP6:~$ python camtest1.py (camera POE connected to PSE port)

Before URL
[tcp @ 0xaaaae4235f40] Connection to tcp://192.168.0.117:554?timeout=0 failed: Connection refused
[ WARN:[email protected]] global cap_gstreamer.cpp:2784 handleMessage OpenCV | GStreamer warning: Embedded video playback halted; module source reported: Could not open resource for reading and writing.
[ WARN:[email protected]] global cap_gstreamer.cpp:1679 open OpenCV | GStreamer warning: unable to start pipeline
[ WARN:[email protected]] global cap_gstreamer.cpp:1164 isPipelinePlaying OpenCV | GStreamer warning: GStreamer: pipeline have not been created
[ERROR:[email protected]] global cap.cpp:164 open VIDEOIO(CV_IMAGES): raised OpenCV exception:

OpenCV(4.8.0) /home/ubuntu/opencv_build/opencv/modules/videoio/src/cap_images.cpp:253: error: (-5:Bad argument) CAP_IMAGES: can’t find starting number (in the name of file): rtsp://admin:[email protected]:554/ in function ‘icvExtractPattern’

After URL
About to start the Read command
About to show frame of Video.
Traceback (most recent call last):
File “/home/alan/camtest1.py”, line 12, in
cv2.imshow(“Capturing”,frame)
cv2.error: OpenCV(4.8.0) /home/ubuntu/opencv_build/opencv/modules/highgui/src/window.cpp:971: error: (-215:Assertion failed) size.width>0 && size.height>0 in function ‘imshow’

alan@orin-nano-JP6:~$ ping 192.168.0.117
PING 192.168.0.117 (192.168.0.117) 56(84) bytes of data.
64 bytes from 192.168.0.117: icmp_seq=1 ttl=64 time=0.056 ms
64 bytes from 192.168.0.117: icmp_seq=2 ttl=64 time=0.086 ms
64 bytes from 192.168.0.117: icmp_seq=3 ttl=64 time=0.090 ms
64 bytes from 192.168.0.117: icmp_seq=4 ttl=64 time=0.072 ms
64 bytes from 192.168.0.117: icmp_seq=5 ttl=64 time=0.067 ms
64 bytes from 192.168.0.117: icmp_seq=6 ttl=64 time=0.083 ms
64 bytes from 192.168.0.117: icmp_seq=7 ttl=64 time=0.087 ms
^C
— 192.168.0.117 ping statistics —
7 packets transmitted, 7 received, 0% packet loss, time 6139ms
rtt min/avg/max/mdev = 0.056/0.077/0.090/0.011 ms

#2

Hi there,
You solid on the syntax of this ? I see only a single ,Hyphen?
HTH
GL :slight_smile: PJ
:v:

#3

Thanks PJ.
The actual code has the correct form, but my copy into this forum somehow lost the (’) single quote.
cap = cv2.VideoCapture(‘rtsp://admin:[email protected]:554/’)
BTW my request now is for the setup that was used by Seeed to verify the PSE port (POE IP Camera model and test programme used).
If you have any ideas about this I would be very grateful.
Best regards,
Alan

#4

Hi there,
Yea that can happen… Just wanted to be sure :+1:
I’ll look into that POE port situ? With the different variants of POE could just be they don’t go all the way to the 48V stuff my bet or even 24v. Wonder if you used an injector would it come to life?
for video at least.
GL :slight_smile: PJ
:v:

I’ll post it up when I find any info.

#5

just saw that , injector?
Hmmm.
GL :slight_smile: PJ :v:

So I looked at my HS log setup with IPcam, and the
String for Rtsp was like this:

‘rtsp:// [USER] : [PASS] @ [ADDRESS] : [RTSP PORT] /media/video[STREAM TYPE]'

I used this guide, for comparison

Live View URL

rtsp://:/Streaming/Channels//
rtsp://:@:/Streaming/Channels//

Where is the IP address of your camera, is the RTSP port of the camera, and and refer to the login credentials of your camera.

Using the first format, you will be asked to login and verify your credentials before being allowed to view the stream.
Using the second format, you will automatically login when requesting the stream

refers to the channel number and stream type of the camera. For example, an of 101 refers to channel #1 (first digit, 1xx) using the main stream (second and third digits, x01).

Typically, you’ll use a program such as VLC Media Player to decode the RTSP stream.

Examples below.

Main Stream
rtsp://192.168.1.100:554/Streaming/Channels/101/
rtsp://admin:examplepass123!@192.168.1.100:554/Streaming/Channels/101/

Sub Stream
rtsp://192.168.1.100:554/Streaming/Channels/102/
rtsp://admin:examplepass123!@192.168.1.100:554/Streaming/Channels/102

Take a snapshot via HTTP URL

http://:@:/Streaming/Channels/1/picture

Where and are the login credentials of the camera in question, and and are the IP address of the camera and its HTTP port (default 80).

The above URL will present a snapshot of the camera’s current live view. Typically, this is used to embed a regular snapshot based on a time interval on a web page, but there are of course many things you can do with the URL.

For example
http://admin:[email protected]:80/Streaming/Channels/1/picture

:v:

#6

Hi again PJ,
I tried to use most of your detailed help on the PSE port, but without immediate success.
However, it seems that this port is associated with apache2 server and so the only response to a simple web browser probing (http://192.168.0.117) brings up the apache2 default page! Briefly tried disabling the server, but seems no direct way to access the camera. Perhaps tech support at Seeed will come forth with some guidance.
Thanks,
Alan

1 Like
#7

My 50 cents are that 192.168.0.117 is the IP of the Ethernet interface of the computer, not the IP of the camera. Sub 0.0 ms ping values are usually from the same device you are pinging from and the apache2 default page is from the reComputer itself.

What is the fixed IP configuration of the camera?

#8

Hi Alberto,
The fixed IP configuration of the camera is 192.168.0.117 and it works in every situation on the LAN.
Alan

#9

And what IP has the PSE interface?

#10

Hi Alberto,
I appreciate your efforts to sort out this issue.
There are at least 3 people at Seeed who I am in contact with.
Basically, the best help would be from a person who is using the same product and has a POE camera working on the PSE port AND can indicate the camera model, the Jetpack version, and the test/evaluation software and its configuration.
Best regards,
Alan