Hi,
I am a developer based in the UK with a test system in France, so debugging isn't easy.
We have encountered an application crash which occurs after about an hour of testing and seems to be related to CAN capture.
I have asked the customer to enable dump file creation and will provide this together with the source code and hardware details when we have it.
In the mean time; having expended a lot of effort in the last 2 weeks trying to locate the source of the crash I am wondering if the following scenario rings alarm bells with anyone?
- We have 3 off PCI NI-DAQ cards + 1 NI-CAN (2 port).
- Load NI-DAQ & NI-CAN tasks.
- Connect RTSI to sync capture. Trigger source is from a DAQ card.
- Start tasks (2nd thread)
- Capture data (2nd thread).
- Stop tasks (2nd Thread).
- Disconnect RTSI.
- Start different CAN tasks.
- Write a CAN message.
- Read CAN times-out before message (or messages) arrive.
- Stop CAN tasks.
- Reconnect RTSI.
- Report status
- Some time passes, don't know how much but probably quite short.
- Crash.
Is it possible that stopping the task and reconnecting the RTSI (11 & 12) while the delayed message(s) arrive may be causing the crash?
I will extend the timeout once I have a dump file.
I have also requested a NI-NAX report so that the software versions can be confirmed.
John C