After reboot of server or restarting the service the camera will exhibit a invalid credential along with a 401 Error.
This was seen on a system that required restarting the system after every Windows Update.
Product
Server 23.06.1.0
Windows Server 2016
Camera: Samsung QNV-C8083R FW 2.21.10.20230908_R
Steps to Reproduce
Restart system and the camera would be locked out of the user attempt to log into the camera and would need to power cycle the camera to enable it to connect. You can confirm this by logging into the cameras gui and finding the following error:
In our client we will show the following logs:
2/25/2024 10:11:25.925 AM (GMT-5:00) SamsungPI Error 7.230.122.80 - Initial discovery failed with error 401. The connection will NOT be retried.
2/25/2024 10:11:25.925 AM (GMT-5:00) SamsungPI Verbose 7.230.122.80 Network error 401 from request https://7.230.122.80/stw-cgi/system.cgi?msubmenu=deviceinfo&action=view using scheme https.
Expected Results
We should be able to reconnect to the camera with no log in failures after a system / server restart.
Actual Results
Camera will fail to connect to Exacq until you power cycle the camera.
Solution
Update the fw to FW version 2.21.10b_20240227-R6 by contacting Samsung to get this fw. AES- 758 is still being investigated and requested that the IP Camera Integration page Be Updated with new test Records form FirmWare Version 2.21.10b_20240227-R6.
Hanwha cameras may be configured with the Road AI license plate recognition application. The data from license plate captures can be viewed in the ExacqVision Client as text, sent as serial data over IP. The Road AI application is pre-installed and licensed from the factory on select camera models. This document will step through setting up the application integration with ExacqVision.
<br>
Tested Versions
ExacqVision 22.12 and higher
Camera models PNO-A9081RLP – firmware 1.41.02 PNV-A9081RLP – firmware 2.21.00
Road AI application Version 7.2.7.6
<br>
Installation
Mount the camera according to the manufacturer’s installation manual. LPR applications typically provide specific guidelines on positioning camera distance and angle to the target. <br>
If needed, download the Road AI User Manual to help with configuration from the manufacturer’s website.<br>
Open a web browser and navigate to the camera’s IP address.<br>
Log in with the username and password<br>
Navigate to the Open Platform settings page.<br>
Once the application is running, you may configure how it sends data to ExacqVision.
<br>
Road AI Application Configuration
Open the camera’s web interface. Navigate to Setup > Open Platform > Go App
<br>
Refer to the Road AI user manual for greater detail on the best way to install and position your camera. Once you have completed this, you may configure the camera for license plate capture.
Select the Settings tab from the top of the application. <br>
By default there is a single zone bounding box, which you may manipulate. A second zone may be configured using the + button under Zones Management. Drag the corners of the bounding box to your desired size, shape, and location in the field of view.<br>
Set the Region field to select your country of interest.<br>
Select the Plate Capture Mode setting.
Low speed mode with 4K resolution
High Performance mode with Full HD resolution<br>
Enabling the Wizard button displays a statistic of the latest 1000 plate sizes detected to help you increase detection rates. See the Road AI user manual for more details.<br>
The Plate Size Measurement feature also aids in increasing the detection rate. Recommended plate width is 130-350 pixels in the camera image.<br>
Scroll down to Recognition Setup to enable/disable Model Recognition and Color Recognition.<br>
Scroll to the Integration Options section.<br>
Select the check box for NVR Integration.<br>
Beneath this check box, enter the IP address of the ExacqVision Server on your network in the field on the left.<br>
Choose a port number that will be used to communicate with ExacqVision. This must be a port number that is not used by any another devices on your network. This port number will also be configured in the ExacqVision Client. Enter the port number in the field to the right of the Server IP address. In the example above, the ExacqVision Server is located at 192.168.0.6, and the port number selected is 9393.
IMPORTANT: When using multiple Hanwha cameras running Road AI on the same network, each device MUST be assigned a unique port number.<br><br>
Click the Save Settings button at the bottom when these steps have been completed.<br>
Before continuing with ExacqVision configuration, ensure that license plates are being captured by navigating back to the Events tab. If you are experiencing trouble successfully detecting license plates refer back to the guides on camera positioning and placement.<br>
NOTE: In our testing, it took some time for the application to complete saving changes when pressing the Save Settings button. You may also need to be patient for the Road AI application to display the camera image.<br>
NOTE: If a red banner appears when navigating back to the Events tab, this may delay events being sent to ExacqVision.
<br>
ExacqVision Serial Port Configuration
Within the ExacqVision Desktop Client, select the Configuration icon from the top-left toolbar.<br>
Select the Serial Ports node from the left-hand navigation tree, nested beneath your server name.<br>
Under the IP section, click the New button<br>
Enter a Name for the Serial Port.<br>
Under the Use column, select POS from the menu.<br>
From the Type column, select TCP Listener.<br>
In the Address field, enter the IP address of the Hanwha LPR camera.<br>
In the Port field, enter the port number you selected and entered into the Road AI application earlier. Recall in our earlier example we entered 9393.<br>
Under the Profile column you will select New, unless you had previously configured a Serial Profile, in which case you would select that profile name.<br>
Click the Apply button to save your changes. If you selected New in Step 8, this will automatically take you to Serial Profiles to continue setup.
<br>
ExacqVision Serial Profile Configuration
If you selected New during setup of the Serial Port, you will begin by naming your Serial Profile. If you did not do this, then you will begin by selecting the New button, then enter a Name for the profile. Example: Hanwha LPR
Choose one of the following options for the Marker Type. Your choice will depend on how you’d like the data to appear in live and search.<br>
For records in this format: LPR LPR = ZTD904 Dodge RAM SUV
Select XML as the Marker Type
Enter <LPR in the SOT Marker field This is not a typo, do not enter a closing >
Uncheck the Case Sensitive box
Click the Apply button to save your changes.<br>
For records in this format: ZTD904 Dodge RAM SUV
Select Standard as the Marker Type
Enter <LPR> in the SOT Marker field
Enter </LPR> in the EOT Marker field
Uncheck the Case Sensitive box
Navigate to the String Replacements tab.
Click the New button.<br>
Enter <LPR> in the String field, then enter a single space character in the Replace field. This field cannot be left empty.<br>
Click the New button again, to add a new row.
Enter </LPR> in the String field, then enter a single space character in the Replace field.
Click the Apply button to save your changes.<br>
Use the Live Display tab to preview how your data will appear in the Live View overlay. Enable Line Removal if you wish to periodically clear the text. <br>
Optional – If you wish to trigger events from ExacqVision’s Event Linking or Event Monitoring features based on specific words, you will need to configure this on the Event Keywords tab within your Serial Profile. Example keyword: LPR
<br>
Event Linking
ExacqVision can use the analytic events from Road AI to trigger various actions, such as recording video from a specific camera.
Select the Event Linking node from the navigation tree on the left side of the ExacqVision Client window.<br>
Click the New button.<br>
Within the Event Type list, select Serial Profile.<br>
In the Event Source list, select the serial profile name to trigger this event on all keywords you configured. Select the profile name with ‘Keyword’ to trigger this event only when that keyword is encountered.<br>
From the Action Type list, select the action you intend to take when triggered.<br>
Select the Action Target.<br>
Some Action Types, such as Record Video, provide the ability to set a Pre and Post Trigger settings.
Click Apply to save your changes.
<br>
Related Materials
Find more details on topics mentioned in this article at the following links:
After making changes to the network settings within the Road AI application, it may be necessary to Stop, then Start, the Road AI application from the camera’s Open Platform page.<br><br>
As noted above, during configuration of the Road AI port numbers; When using multiple Hanwha cameras running Road AI on the same network, each device MUST be assigned a unique port number.<br><br>
The camera is detecting license plates in the Road AI application and the port numbers are correctly set in both the camera application as well as in ExacqVision’s Serial Ports page but no data is being received. You may need to add an incoming port exception to the firewall of the system running your ExacqVision Server application.
H.264 (MPEG-4 AVC) and H.265 (MPEG-4 HEVC) are MPEG video standards. H.265 is the newer of these standards.<br><br>
What is Motion JPEG?
Motion JPEG is a compression format that is older than H.264/H.265 and was created as a version of the still image JPEG format for video use. It is often shortened to just JPEG in video applications.<br><br>
Why choose H.264/H.265 over Motion JPEG?
Motion JPEG ignores frame-to-frame data redundancy. When using Motion JPEG, each video frame is compressed using JPEG. The Motion JPEG video stream is then presented by displaying each frame in order.
H.264/H.265 improved upon this by using compression algorithms that compare frame-to-frame data to help eliminate the transmission of redundant data.
Both provide video compression far greater than Motion JPEG without sacrificing image quality.
Greater compression means big savings in terms of your network’s bandwidth consumption and the amount of space required to store recorded video on an NVR over Motion JPEG. Decreasing the amount of storage space needed will lead to longer retention times without increasing storage capacity. This aspect is even more important when considering use cases that require high numbers of cameras, high frame rates, and long retention times.
The following graph shows a comparison of three identical model 2MP cameras set to 15 frames per second, running the same firmware version. However, each camera is set to a different recording format. The camera set to Motion JPEG is shown at the top, in red. Below, the H.264 stream is shown in blue, and the H.265 stream just under that in green. The changes in data correspond with a person walking through the scene.
ExacqVision records files in 5 minute increments. Examining the files created from these 2MP cameras recording continuously for 5 minutes and then extrapolating their file sizes over the course of 24 hours, and 1 year, the amount of storage space saved is considerable.
5 minutes (KB)
24 hours (GB)
1 year (TB)
Motion JPEG
705,453
203.17
74.2
H.264
32,132
9.25
3.4
H.265
21,966
6.3
2.3
<br><br>
How does H.264 work?
As mentioned Motion JPEG compresses each frame individually and all frames are essentially equal. H.264 and provides for multiple types of frames.
I-frames are somewhat similar to a Motion JPEG frame. An I-frame contains all the data needed and can be decoded without reference to any other frames. H.264 always begins with an I-frame, and you’ll learn why in a moment. These I-frames occur at regular intervals in the video. A camera’s GOV, or GOP, rate sets the distance between each I-frame.<br><br>
P-frames lie between the I-frames. P-frames reference the previous I-frames and are smaller because they only include the regions which have changed. This provides a huge benefit over Motion JPEG because you are not retransmitting data that hasn’t changed.
Imagine a scene in which a building is in the background and a person enters the field of view. The camera is not moving, nor is the building, so the pixels making up the part of the image where the building stands do not need to be sent again. Instead, only those pixels representing the person that entered the scene are sent and these replace the pixels in the image displayed to you.<br><br>
B-frames are not provided by all applications or video devices. B-frames occur in between I-frames and P-frames, or between multiple P-frames. B-frames are predictive in nature. They refer not only to previous frames but to future frames as well. For this reason implementing B-frames is not always used in live video applications since there is a slight delay introduced due to the need to wait for additional frames to arrive before the B-frame can be created. When only I-frames and P-frames are used, it is referred to as an H.264 baseline stream.
H.264 compression is performed by processing and compressing the frames in regularly sized ‘macroblocks’ of 4 to 16 pixels, which are further broken down into smaller blocks for compression. The main takeaway is that the image frame is divided up in very regularly sizes areas.<br><br>
How does H.265 work?
H.265 includes the same types of frames as mentioned above, but it improves over H.264 by providing the ability to dynamically size the regions the frame is broken up into. Rather than the macroblocks, transform blocks, and prediction blocks of H.264, these dynamically sized areas are named Coding Tree Units (CTUs). This usually translates into more efficient compression than H.264 because the frame can be compressed more heavily in some areas than others when needed.
Illustrated below, H.264 on the left breaks up the image into equal blocks for compression. Whereas, on the right, H.265 divides the image into dynamically sized regions to better compress those regions based on what is in them.
After selecting a PTZ preset motion appears to stop working in the camera’s web interface. If you edit the motion settings in the client, the motion will events will start to work in the camera again.
Product
Camera models:
QNP-6230 PTZ
QNP-6230H PTZ
Firmware:
fw 1.40.02_20191031
fw 1.40.03_20201203_R410
Steps to Reproduce
Have the camera setting on the home preset.
Select a second PTZ preset for the camera to move to. In the photo below you can see that the camera’s web interface indicates motion has stopped in the graph to the right of the camera’s image.
Motion stops working in the cameras gui.
Go to client and edit any motion window settings.
Motion will resume in the cameras gui.
Note if on a tour- this will also be affected by the movement of the presets.
Expected Results
PTZ tours or presets should work after the camera moves to the new preset location.
Actual Results
The camera stops detecting motion events after a preset is selected and the camera has moved.
Solution
Testing has shown that firmware 2.10.02_20220324_R614 has corrected this behavior on the camera.
There is an issue reported for Hanwha cameras that it stops recording on motion after a day or two unless disabled the cameras and re-enabled again to make it works and start to record on motion
Fix
The issue was solved on ExacqVision Server version 22.03 or higher
