- Encoder is not functional
- NET53XXT/mced service fails to initialize
Pelco Transmission & Power
- Pelco NET53XXT Series Encoder(s)
- Pelco Endura Utilities Software
User restored inappropriate backup configuration files to NET53XXT
note: Pelco recommends that these steps only be attempted with direct supervision from a Pelco Product Support Technician on the phone or Remote Desktop Session.
note: Exactly typed command syntax or selections are given in blue.
note: Except where directed, proceed through the steps of this article from top to bottom, in order they are presented.
Section 1. Verify the issue
1. Launch Endura Utilities, log in and press Search.
note: The default login credentials for Endura Utilities version 2.2 and below is [Username: Administrator and Password: configapp], however version 2.3 and greater removed that unique login credential requirement, and instead authenticates against the standard Endura Credentials used for WS5XXX and VCD5200. The default login in that case is [Username: admin and Password: admin].
2. In the System Attributes tab, right-click the Encoder in question and select SSH Into.
note: The default Linux Administrative login credentials for Endura devices is [Username: root and Password: pel2899100 ]
note: If you have never SSH'd into the unit before, you will likely receive the following warning prompt...
...simply click Yes to proceed.
3. Next, re-start the Encoder video capture service by issuing the command service mced restart from the [root@PELCO root]# prompt...
note: It may take quite some time for the service to stop and re-start. You may also receive some errors, simply proceed to the next step regardless of outcome, once returned to the [root@PELCO root]# prompt.
4. Attach your ssh console to the screen session of the NET53XXT service by issuing the command screen -r NET from the [root@PELCO root]# prompt, and observe the results returned to the screen...
Case 1: Your unit does not have the issue described in this article -
If the resulting output on the NET53XXT device does not closely match the above screenshot by specifically containing the text "Do not support this PELCO_PRODUCT!!", it means that your unit does not have the issue described in this article. You have no further use of this article, and may now search elsewhere for a solution to your specific issue. Do not proceed any further with the steps in this article.
Case 2: Your unit may have the issue described in this article -
If the resulting output on the NET53XXT device does closely match the above screenshot by specifically containing the text "Do not support this PELCO_PRODUCT!!", proceed to step 5. below.
5. Open a script file that is involved in unit startup by issuing the command vi /etc/pelcorc from the [root@PELCO root]# prompt, and observe the results returned to the screen...
note: In the above screenshot, the highlighted line shows us that this script is invalid for a NET53XXT Encoder. A user had incorrectly restored Backup Configuration Files which were originally taken from an EnduraXpress Integrated Recording and Management Platform model EE500. The highlighted area should read "export PELCO_PRODUCT=NET53XXT".
Section 2. Correct contents of corrupt startup script
1. Use the keyboard arrow keys to position your cursor just after the header hash-tags (#####).
2. Press insert to enter editing mode, and the press and hold the delete key until all file contents below that cursor position have been emptied...
3. Finally, manually enter the proper file contents (below), pressing enter/return at the end of each line to move to the next. Once complete, press escape.
Your file should now look as follows...
4. Save the file changes by entering a colon (hold shift and the : key simultaneously), and then release shift and type wq and press enter/return.
5. Reboot the unit by issuing the reboot command from the [root@PELCO root]# prompt...