Synchronisation issues with TestDrive chassis

Let's say you are using a model with TestDrive modules inside and you have the following error message at loading :

"ERROR:    Register_CB_WaitForTimer: more than one synchronisation block (or internal software clock) detected"

It means that the model have a synchronization problem that could be due to two options

• "more than one synchronisation block" : it means that you have at least one OpSync master in your model, but you did not add the OpConfigSync block (8.2.x or later). This block specifies that the OP5110 is the master, if you do not add it the model has two "master" symchronization blocks (the Opsync and the last TD module), therefore the error. This case could happen only in the case of a TestDrive synchronized by a HIL.
  Possible Workarounds :
  • remove the block OpSync (if you are running a stand-alone TD chassis, this block must not be in the model)
  • add a  OpConfigSync block and set it to "OP5110" (application TestDrive synchronized by HIL)
• "internal software clock" : you are running in software synchronized instead of Hardware Synchronized
  Workaround:
  • switch to Hardware Synchronized mode

NOTE : this error could also occur if you have two OP5110 set in master mode in your model.

keywords : WaitForTimer, synchronisation, software clock, OP5110