Other Parts Discussed in Thread: LDC1314, LDC3114
Hi Guys,
Good day. I'm posting this in behalf of the customer. Could you help us.
I am trying to migrate from LDC1314 to LDC3114 due to performance and cost reasons. With the LDC1314, I had four different coils connected to the four channels and I was able to trigger each of them separately for a specific amount of time (say 1ms). This was possible without having to go to the config mode -> on the fly. This enabled me to synchronize this measurement with my microcontroller, where I have other measurements running -> 5ms cycle.
I tried to synchronize the scan cycle to a 5ms cycle, using the CONFIG mode of the LDC. I made the LDC to go to config mode so that I can "stop" the measurement and start it again, whenever I want. This seemed to work, but then for the next measurement cycle that followed, I did not get any Interrupt at all. It means, once the LDC is back from config mode, it requires two complete measurement cycle to provide interrupt and valid data.
According to the datasheet, the new scan cycle will start within 1ms, after the LDC is brought back to normal operation.
My question -> why does the LDC takes two scan cycle to provide the interrupt, when it comes back from the config mode?
Please see attached documents below
Manual Trigger of Scan Cycle issue.zip
Thank you in advance for the support.
Best regards,
Jonathan