03-14-2023 05:48 PM
Hi everyone,
In the XNET example for diagnostic frames, the diagnostic schedule is switched back and forth between master request and slave response using LIN Diagnostic Change VI.
I'm trying to define database in memory and while I created schedules for Frame Out Queued and Frame In Stream sessions with corresponding schedule entries containing master request and slave response messages, when running XNET Write (LIN Diagnostic Change), I get the following error:
NI-XNET: (Hex 0xBFF6318F) A LIN diagnostic schedule change requires the diagnostic schedule to be defined in the database. Solution: Define the diagnostic schedule in the database.
My question is: what makes the schedule a "diagnostic" schedule? More specifically: how do I define the diagnostic schedule in the memory?
Since my program runs well when using the database file, and it contains a bunch of schedules, how does it know which one is "diagnostic" schedule?
Thank you in advance.
Solved! Go to Solution.
03-14-2023 06:48 PM
Your question is best to be posted at Automotive and Embedded Networks board.
what makes the schedule a "diagnostic" schedule? More specifically: how do I define the diagnostic schedule in the memory?
Reference: Error -1074384497 (Hex 0xBFF6318F) Occurred at XNET Write (State LIN Diagnostic Schedule Change).vi
03-15-2023 07:36 AM - edited 03-15-2023 07:37 AM
ZYOng more or less already explained it. While the LDF file format allows for explicit Diagnostic message definitions under the section Diagnostic_frames, the NI XNET software does not seem to make use of that part of the LDF file automatically. Instead you have to explicitly add two extra schedules called MasterReq and SlaveResp (or whatever your frames in the Diagnostic_frames section are called).