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:
Arecont write fw to support onvif —> impossible, never happen.
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.
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.
Some Exacq NVRs built with Microsoft Windows Server 2022 only acknowledge one network interface, rather than two, when being configured out-of-box.
<br>
Product
Issue has been noted on BBE systems ASRock Industrial IMB-X1313 system boards, listed below.
Z-Series systems
Some A-Series systems, depending on the system options ordered
NOTE: Windows Server OS is an optional upgrade for many systems, so this will not apply to all systems listed above.
<br>
Steps to Reproduce
Power on unit<br><br>
Check Windows Device Manager for listed network interfaces<br><br>
Check exacqVision Client Network Settings
<br>
Expected Results
All network cards are recognized and appear listed.
<br>
Actual Results
Only one interface is listed.
<br>
Solution
Attempt solution starting with Step 9 first. If this still fails, repeat steps beginning with Step 1, which requires opening the system chassis.
Power the system down gracefully using the shutdown option from the OS.<br><br>
Unplug system and press the power button to drain any residual power off the board.<br><br>
Open the system, locate and remove the CMOS battery from the system board. Wait 5 to 10 minutes before continuing.<br><br>
Replace the CMOS battery.<br><br>
Reconnect power to the system.<br><br>
Power on the system.<br><br>
Enter the system BIOS or Boot Option menu and boot to the UEFI partition.<br><br>
Check for changes in recognition of the additional network interface(s). If no change, continue with next steps.<br><br>
Restart the system and enter BIOS.<br><br>
Open to the Exit menu and select Load Defaults.<br><br>
Reboot and enter BIOS again, select the UEFI partition as the boot option.<br><br>
Check Windows Device Manager and Network Settings to validate that the additional interface(s) are detected.
<br>
AES-842 Has been created to investigate this.
<br>
Additional Steps
Pull the logs from the UEFI
Open CMD.<br><br>
Enter the following: mountvol z: /S<br><br>
Type cd z: and press Enter.<br><br>
Type dir and press Enter.<br><br>
Type cd EXACQ and press Enter.<br><br>
Open File Explorer and locate the logs in the Z partition. This is hidden by default. If you make them visible using File Explorer options, be sure to set to hidden again after you are done collecting logs.<br><br>
Collect the txt and xml files from the logs and add them to a newly created ZIP file to copy from the system.<br><br>
When done collecting logs, return to CMD and enter mountvol z: /d to remove the temporarily mounted volume.
Beginning with Enterprise Manager version 24.03.0.0 (or 23.09.124), downgrading will fail due the update of an underlying resource. We now utilize Django v3.2.23, which necessitated a change to the database schema. This will cause downgrade database migrations to fail.
Prior to upgrading from 23.09 or lower, it is recommended to complete a Backup. Instructions for scheduling a backup can be found in the exacqVision Enterprise Manager User Manual HERE.
NOTE: If you are using Postgres DB, you will only need the backup file. If using MS SQL, you will also need to create a DB backup utilizing Microsoft utilities. More information can be found HERE.
On occasion, Exacq Support is asked about using a USB network interface (NIC) on their system. This is more frequently asked by those with smaller units which may have only one network interface and a user is attempting to add additional network interfaces to span networks or attempt to increase network throughput by bonding/teaming multiple NICs.
Regardless of the system model or size, Exacq does not support or test USB NICs.
Exacq Support will also not recommend any specific NICs for this usage. Even NICs connected externally using USB 3.0 or USB-C may encounter issues, therefore Exacq only supports internally connected network interface cards and does not troubleshoot issues with third-party devices added by users.
An event, such as OS failure, requiring a reimage of your Exacq NVR may leave you with unlicensed exacqVision Server software. If you cannot locate a copy of the emailed license key from the time of purchase, or an exported copy of the .KEY file to use, what should you do?
<br>
Import from Exacq.com
Perhaps the simplest method is to follow the steps below.
Provide an internet connection to the system.<br><br>
Open the exacqVision Client.<br><br>
Select the cog wheel icon in the upper-left to enter the Configuration screen.<br><br>
From the navigation tree along the left side, locate the server name and expand this option.<br><br>
Beneath the server name, select Configure System.<br><br>
On the System tab, locate the License area. Press the Import button and select ‘From exacq.com‘.<br><br>
This method will automatically import the most recent license from Exacq. Note, that if the license key is expired you may need to change your installed exacqVision Server version to one released prior to the license’s expiration date.
<br>
If the import fails or you are in need of other licensing information, contact Orders as directed below.
<br>
Contact Orders
Orders may be contacted by phone or email. Please be prepared to offer the system’s serial number or licensed MAC address.
+1-317-845-5710 select option 3 for Orders when prompted.
This document will guide you through step-by-step procedures for keyboard use and suggested button mappings.
Product
Axis TU9001 Control Board
TU9002 Joystick
TU9003 Keypad
The Axis TU9001 Control Board consists of the combination of the TU9002 Joystick and the TU9003 Keypad.
IMPORTANT: The TU9002 and TU9003 appear to the operating system as separate devices. As of Client version 24.03 only one Joystick device may be enabled on a workstation at a time. This article will be updated in the case of further enhancements.
<br>
Setup
Follow the Installation Guide from Axis for the steps to attach the two devices and connect the corresponding USB cables.<br><br>
Plug the keyboard’s USB cable into the USB port on the Client viewing machine, where the keyboard will be operated from.<br><br>
Navigate to the Joystick configuration page within the exacqVision Client.
Select the cog wheel icon in the top left-hand corner of the Client window to enter Configuration settings.
Expand Client from the navigation tree on the left-hand side.
Select Joystick from the tree to load the Joystick configuration page.<br><br>
Select the joystick that appears from the drop-down menu. If the device fails to appear, close and re-open the exacqVision Client instance. <br><br>
Select the Calibrate button to zero out the joystick positioning.<br><br>
Adjust the sensitivity to your liking.
X/Y Axis controls camera Pan/Tilt, while Z Axis controls zoom.
Suggested settings include increasing the sensitivity on the X/Y Axis and Z Axis.
<br><br>
Pressing any of the buttons on the keyboard will highlight that number in the button menu to help you find the corresponding mapping. You may need to scroll the window if you do not see the button highlighted when pressed. <br><br>
Once you have located the button, you may use the drop-down menu to select the action you wish to assign to the button.<br><br>
After applying changes to the keyboard configuration, return to the Live camera view and the controls will be available for use.
<br>
Buttons on the TU9002 Joystick
The TU9002 features 7 buttons across the top of the device and 2 buttons on top of the joystick. The center Toggle button along the top acts as a Function Key. When pressed this will highlight button 17 in the button map, but you should notice the illuminated LEDs shift on the device. This toggles the ability to assign additional actions to each of the other buttons on the device.
For example, when the buttons are illuminated above, pressing J1 will highlight button 1 in exacqVision. If the center button is pressed, the illumination shifts below the buttons. Pressing the same button now highlights button 9 in exacqVision. The actions available in exacqVision Joystick settings do not align with the rewind, play/pause, forward symbols indicated on the device.
The TU9002 Joystick also features the ability to switch between joystick and mouse modes. The default mode is set to act as a joystick. Switch to mouse mode by pressing and holding the center Toggle button then press the J1 button. Moving the joystick now moves the mouse cursor. While in mouse mode the J1, J5, and left joystick button act as a left-click. The J2, J6, and right joystick button act as a right-click. Press and hold the Toggle button then press the J1 button again to revert back to joystick mode.<br><br>
<br>
Troubleshooting
Check that the device is recognized by the operating system.
Windows – Navigate to Start > Control Panel > Game Controllers
Ubuntu/Linux – Open Terminal and run ‘lsusb’ to see if the devices are listed
A valid power source is connected to the PSU and the PSU is operational.
Amber (Blinking)
Indicates an issue with the PSU.
Not Lit
Power is not connected to the PSU.
Green (Blinking)
PSU firmware is being updated.
WARNING: Do not disconnect power or unplug the PSU while firmware is updating. Interruption of this process could lead to PSUs ceasing to function.
Green (Blinking and powers off)
When hot-plugging a PSU, it will blink 5 times at a rate of 4Hz then power off. This indicates a mismatch due to efficiency, features, health status, or supported voltage.
WARNING: If two PSUs are installed, both PSUs must have the same type of label. Mixing PSUs is not supported, even if they have the same power rating.
WARNING: If two identical PSUs receive different input voltages, this can cause different output wattage and trigger a mismatch.
CORRECTION: When correcting a PSU mismatch, remove all power from the system then replace the PSU with the blinking indicator.
<br>
System Health and ID Indicators
The left control panel on the front of the system acts a button and provides an LED indicator. System ID mode, activated by pressing the control panel on the front of the system, or the ID button on the rear of the system will flash these LEDs to make identification in a server rack, from either side, easier.
LED Indicator
Description
Blue (Solid)
The system is powered on, healthy, and system ID mode is not active. Press the system ID button to switch to system ID mode.
Blue (Blinking)
System ID mode is active. Press the system ID button to switch to system health mode.
Amber (Solid)
The system is in fail-safe mode and should be inspected for issues or troubleshooting.
Amber (Blinking)
The system is experiencing a fault. Check the System Event Log for error messages. Look up specific error codes using Quick Resource Locator.
<br>
Drive Indicators
The LEDs on the drive carrier indicate the state of each drive. Each drive carrier has two LEDs: an activity LED (green) and a status LED (bicolor green/amber). The activity LED blinks whenever the drive is accessed.
Drive status LED indicator
Drive activity LED indicator
Drive capacity label
LED Indicator
Description
Green (Solid)
Indicates the drive is online.
Green (Blinks twice per second)
Indicates the drive is being identified, or preparing for removal.
Off
Indicates the drive is ready for removal.
NOTE: Drive status indicator remains off until all drives are initialized after the system is powered on. Drives are not ready for removal during this period.
Green/Amber (Blinks green, ambers, then powers off)
Indicates that there is an unexpected drive failure.
Amber (Blinking 4 times per second)
Indicates the drive has failed.
Green (Blinking slowly)
Indicates the drive is rebuilding.
Green/Amber (Blinks green 3 seconds, amber 3 seconds, then powers off after 6 seconds)
Indicates that the rebuild has stopped.
<br>
iDRAC Direct (micro USB) Indicators
LED Indicator
Description
Solid green for 2 seconds
Laptop or tablet is connected.
Blinking green (on for 2 seconds, off for 2 seconds)
Illustra Flex4 Indoor PTZ with bubble showing distorated images on zoom.
Product
Illustra Flex 4 PTZ all firmware
Steps to Reproduce
Turn off the Tilt Limit in the camera PTZ settings
Expected Results
Camera zoom shows in focus and sharp
Actual Results
Camera zoom is slightly disorted and out of focus
Solution
This is working as designed.
The camera datasheet indicate the tilt range is -15 to -90.
When you disable the tilt limit and move above -15 degree, you will see image distortion at zoon due to the camera looking through the ‘transition region’ of the bubble.
<br><br>
<br><br>
<br><br>
