An IPC Fails to Go Online After Being Upgraded

Step 1 View the message.dbg log file of an IPC.

Step 2 Check whether the log file contains the following information:

ERR:|ptz_business.c:2458|serial port set parameter enStopbit: 2 error 
ERR:|ptz_business.c:614|PTZ SerialPortPara error!
ERR:|copra.c:757|Control thread exit, Now Release Driver Lib Begin.

• If yes, go to Step2.
• If no, contact your service provider for assistance.

Step 3 Use SSH to log in to the IPC as the admin user, copy the default.xml file in /usr/app/bin to the local computer, and delete the default.xml file from /usr/app/bin.

NOTE:
For details about the default password of the admin user, see the user guide for the device.

Step 4 Change the network parameter values in the local default.xml file to the values planned for the live network and save the file as a new default.xml file.

Set MeshType to 0, DhcpEnable to 0, and MeshDoubleSpeed to 3. Set IPAddress, Netmask, Gateway, and FirstDNSAddress based on the data plan of the IPC.

Step 5 Place the new default.xml file to /usr/app/bin of the IPC.

Step 6 Run the cd /usr/setting command.

Step 7 Run the rm config* command.

The system deletes all files whose file names start with config from /usr/setting.

Step 8 Run the reboot -f command.

The IPC restarts.

Step 9 Access the web page of the IPC again and set platform connection parameters.

Step 10 Log in to the IPC through SSH, delete the new default.xml file from /usr/app/bin, and copy the original default.xml file back to the directory.

Step 11 Check whether the fault is rectified.

• If yes, no further operation is required.
• If no, contact your service provider for assistance.

----End

The stop bit ranges of the PTZs of the two versions are different so that the IPC software fails to be started after being upgraded.