Difference between revisions of "ConfigInfo"
(→Config info is mismatched with real situation after IPC working for a while.) |
|||
| Line 1: | Line 1: | ||
==Config info is mismatched with real situation after IPC working for a while.== | ==Config info is mismatched with real situation after IPC working for a while.== | ||
| − | + | * Refresh the interface. | |
| − | + | * It is caused due to the modification of IPC config; it doesn’t belong to the IPC problem. Users can check what platform manages IPC or which device that the rear end is connected to. They can use check the exact reason by adopting separated checking method. Currently the PSS client and soft decoder can modify the Baud rate of some IPC, which leads to a situation where the IPC is out of control. | |
[[Category:Troubleshoot]] | [[Category:Troubleshoot]] | ||
Latest revision as of 15:20, 8 September 2016
Config info is mismatched with real situation after IPC working for a while.
- Refresh the interface.
- It is caused due to the modification of IPC config; it doesn’t belong to the IPC problem. Users can check what platform manages IPC or which device that the rear end is connected to. They can use check the exact reason by adopting separated checking method. Currently the PSS client and soft decoder can modify the Baud rate of some IPC, which leads to a situation where the IPC is out of control.
