Category: Logs

Categories
Plugin Knowledge Support Support exacqVision Server Products Logs SamsungPI

Hanwha PNM-C32083RVQ Connection to Server and Motion Stops Working

Description 

Hanwha will not allow motion to work properly with Exacq Server 24.09.4.0 as long as the camera is on fw 23.01.04-20240417-R929 due to a NTP issue found. Another issue reported is the connection status will throw errors to indicate it is not connected properly.

NOTE:
FW 23.01.01 obtained from Hanwha (which will be the official release 23.01.5) will allow Hanwha vision plugin to be used to connect and records on motion if SV/CV is 24.09.04.0 and above.

Product 

  • Hanwha PNM-C32083RVQ fw 23.01.04-20240417-R929
  • exacqVision Server 24.09.4.0

Steps to Reproduce 

Update server to 24.06.2.0.
Connection to camera will display an error and not connect properly.
Motion will stop working.

Expected Results 

Camera should connect and Motion should work.

Actual Results 

Camera will show a connection status error and Motion does not work.

Solution

Exacq has provided a resolution with a work around but updating Server to 24.09.4.0 or higher will need to be performed. Additionally you will need to apply the NTP workaround seen below until Hanwha updates the firmware.

Hanwha has a new issue with setting the NTP server on some newer firmwares that crashes the server and displays a Bad Gateway 502 error in exacq. We make that call on Add or Enable.

Workaround:

If before adding the camera, we go into the date/time page in the camera Web Page and put the IP address of the Exacq Server in the first NTP server blank. Then the plugin determines it is already set and continues on to next cgi and connects video. This is resolved in Server 24.09.4.0.

FW 23.01.5 Will be release by Hanhwa that will house the NTP fix. Until that time of release please use the proper work around or contact Hanwha for appropriate FW.

<br>

Categories
Plugin Knowledge Support Support exacqVision Server Products SamsungPI

Samsung PNM-C34404RQPZ Connection Issues

Description 

There have been several reports of connection issues with the Samsung PNM-C34404RQPZ. Reports of the units rebooting upon connecting it to the client and which plugin to utilize.


Product 

Exacq Server 24.03.7.0
Camera Info: Samsung PNM-C34404RQPZ
FW used: 23.01.04_20240417_R650

https://www.exacq.com/integration/ipcams/#getCameraRecord=901b747e-fcbf-5464-7543-5aeb7ae3afe8~nstep_id=step-3

Steps to Reproduce 

In the Client go to Add IP Cameras under the configuration. Add the first set of fixed camera’s as you would normally do for any camera.
Add the PTZ camera using the method seen below with the override.

Expected Results 

Camera should connect and work as designed.

Actual Results 

Some reports experience the camera rebooting during connection due to the none use of the power supply that is shipped with the unit. The Power supply must be used.

When connecting the camera as Hanwha or Samsung Plugin on older FW 23.01.03_20240119_R528 will connect but it was reported that motion was not working.

Solution

Update Exacq Server to 24.03.7.0 or above.
Use FirmWare 23.01.04_20240417_R650.
Add PTZ sensor manually using ipaddress#bank=2
Add the camera as Hanwha or Samsung device type.
Make sure the power adapter is of correct specification for proper functioning of the camera. Refer to the camera data sheet.


NOTE:
We have noticed Hanwha has started changing the gov size down to the framerate when users lower the framerate, but not the other way around.

If a user attempts to change a setting while the HTTPS connection is still being attempted, the camera has trouble sending data.

To check this, Log Into the camera web page and verify the GOV size is set to frame rate or higher. Out of the box they are set to 2x framerate. For example- 30fps 60GOV.

AES-878

Categories
exacqVision Server Windows Knowledge Support Support exacqVision Server Products PanasonicPI

H265 Motion Detection Fails on Panasonic WV-S8531N

Description 

The Panasonic WV-S8531N fails to detect motion when using H265 option.

Product 

ExacqVision Server

  • Server 22.09

Steps to Reproduce 

  • Connect the Camera to Server 22.09 using camera FW 1.03 and set the schedule to record motion.
  • Set Camera to Motion recording schedule and use H265 Format.

Expected Results 

Motion is detected and video records.

Actual Results 

Motion is not detected and video is not recorded.

Solution

Updating firmware to S8531_202ES allowed the camera use Motion with H265 format on Server 22.09.

AES-146

<br>

Categories
Knowledge Support Plugin Support ArecontPI exacqVision Server Products Logs

Arecont Camera 12176DN on firmware 65216 is Causing the Video Stream to Timeout

Description 

Arecont Camera 12176DN on fw 65200 is causing the video stream to time out and the stream is reconnecting. CGI access to the camera is fine.

Product 

  • Client Version: “22.03.1.0”
  • Server Version: “23.06.1.0”
  • Arecont Camera 12276DN on fw 65200

Steps to Reproduce 

Connect to the camera and let it record.
The video stream is timing out and the stream is reconnecting. CGI access to the camera is fine.

Expected Results 

Motion / Free run should not attempt to reconnect.

Actual Results 

There are constant gaps in recording when searching.

Solution

Roll back the FW to version 65129 on the camera.

Per Arecont-
According to our internal documentation, the only change from 65192 to 65200 was to properly provide a handshake response for digest authentication.  

AES-662

Waiting on PM to decide how to appropriately resolve this.
According to one customer they rolled back the FW on the camera and all the behavior seen prior resolved.

OPTIONS:

  1. Arecont write fw to support onvif —> impossible, never happen.
  2. Schedule a task to bring native plugin into spec with rest of plugins as a final step for legacy support as they themselves are moving to all onvif.
    Big lift. Proper thing to do.
  3. Try a hack in the plugin to allow increasing the buffer size with an override. –> small lift (< 1 week) with understanding this may unnecessarily increase memory usage on a system with a lot of arecont native. An override to make this a per camera impact.

 4)Give them some gratis licenses –> problematic, no way to specify what licenses are used for and they lose all motion recording functionality.

Categories
Plugin Exclude from Global Search Log Level Error exacqVision Server Categories Logs Illustra3PI

Camera did not send valid quality for codec H264

Camera did not send valid quality for codec H264

Description

exacqVision Client connection status for camera shows “unable to create video stream” status.

Notes

Often this is a firmware compatibility issue. There are some cases that this has been resolved by factory defaulting the camera and/or removing and recreating illustra3pi.xml file in server folder.



Categories
Plugin Exclude from Global Search Error exacqVision Server Products Logs Core

Failed to load plugin analyticpi.so: load code -1

Failed to load plugin analyticpi.so: load code -1

Description

This is expected behavior from exacqVision systems without integrations from supported analytic appliances.%BR%%BR%

Refer to article: analyticpi plugin fails to load

Categories
Plugin Exclude from Global Search Log Level Error exacqVision Server Categories Products Logs Core

Failed to load plugin analyticpi.dll: load code -1

Failed to load plugin analyticpi.dll: load code -1

Description

This is expected behavior from exacqVision systems without integrations from supported analytic appliances.%BR%%BR%

Refer to article: analyticpi plugin fails to load

Categories
Plugin Exclude from Global Search Log Level Warning exacqVision Server Categories Logs PsfPI

FFNI on stream %1 – %2

FFNI on stream %1 – %2

Description

FFNI indicates First Frame Not I-frame. The psfpi plugin cannot start recording on a P/B-frame since these cannot be decoded. The FFNI metrics/logging is accounting for the fact that frames were dropped. Possible symptom is “smearing” of video occasionally “snapping” back to clear image. The stream ID will determine if it is video, audio, primary, or secondary. This may occur normally on initial connection upon starting the server service, startup, or when re-enabling a stream. If it is persistent during normal system operation it indicates a problem.%BR%%BR%

%1 – Stream ID%BR%

%2 – Device Name%BR%

Notes

  • Enabling debugging logs on core may reveal further details.%BR%
  • In the case where huge key frames may be dropped, this may be examined by exporting the video in PS format then examining in psexplorer.
Categories
Exclude from Global Search Plugin Log Level Error Categories Logs GenericCameraPI

%1 Network error 102 in the metadata stream using scheme http

%1 Network error 102 in the metadata stream using scheme http

Description

Indicates a libcurl error where the status is OutOfRequest. Requires a packet capture for further investigation.%BR%%BR%

%1 – Device IP Address %BR%

Categories
Plugin Exclude from Global Search Log Level Error Categories Logs GenericCameraPI

%1 Network error 101 in the metadata stream using scheme http

%1 Network error 101 in the metadata stream using scheme http

Description

Indicates a libcurl error where the status is AlreadySending. Requires a packet capture for further investigation.%BR%%BR%

%1 – Device IP Address %BR%