For our Synchronization solution, some customers are worried that the reaction time of the LCD module will be longer than that under normal conditions in case of re-synchronization since they holds the CPU's sending commands to LCD module can not rely on the fast reaction time of the display (approx. 2 msec per command).
In fact, this situation doesn't exist at all because processing speed of CPU is much faster, compared with communication speed. The other customers think for a save communication path between CPU and LCD module there should be some interaction to let the CPU know what has happened, otherwise the CPU will not know how many frames were lost. Because of the automatic re-synchronization, which takes place within the display, the information of the pointer status will be overwritten. They ask for interaction between CPU and LCD module which can't be realized by automatic re-synchronization.
This problem does exist. The solution is by "checking-response" way. But if this method is applied, the protocol will be very complicated and troublesome. For example, if some response is lost, the command needs to be re-sent. Furthermore, the command re-sent shall be numbered one by one. In this way, it is not meaningful to use our display module, since the biggest feature of our product is its easy operation.
没有评论:
发表评论