Re : automotive diagnostic command set error popup

[bw-dijon]

Hello,

Anyone knows how to prevent automotive diagnostic command set to popup error and/or warning message windows ?

Thanks.

B.W.

[Gibson]

can you give some more details when the error occurs and how the error looks like?

are you using LabVIEW? If so, Automotive Diagnostic Command Set is 99% based on LabVIEW so you may be able to prevent the error popupon your own

[bw-dijon]

Hi Gibson,

My problem is'nt the error by itself but the fact that adcs show an error popup that block my application. ( i.e ISOTP error like time out on flow frame or so ... )

My application is written in Labwindows and is running standalone automaticaly with no one to handle error popup, when an error appear at end of cycle my app is stoppped and the production line stopped too until someone click on 'OK' button.

It's very annoying !!! 🙂

So I want want to handle errors or warning  by software without adcs poping up a error box.

Thank's for your support.

B.W.

[O_Proulx]

Hello Gibson,

I was not able to reproduce your error pop up.  Could you verify that your built configuration is in "release"and not in "debug" mode (go to Build -> Configuration and select release).  I think displays any error in debug mode, but should let you handle the errors in release.  

Have a great day.

[bw-dijon]

Hello O. Proulx,

I've checked my exe , it's a release build, fing here under some screenshots of error messages :

It's not my code wich popup these messages, they come from NIDiagCS.dll.

Any idea ?

Thank's for your support.

B.W.

Nota:

NI Automotive diagnostic command set 1.0.0.f1

NI CAN 2.7.0f0

NI Labwindows CVI 8.5.0

[Gibson · Accepted solution]

Please verify that your CVI application source code does not use similar error code checks like we use in our examples.

The Aut. Diagnostic Command Set CVI Examples contain always this routine to verify the function status.

void CheckError (const char *Routine, long status)

PLease check you code if it contains this technique.

Thanks a lot

[Ceule]

Hello B. W.,

the output in the screenshots that you provided is formatted the same way as the ndStatusToString routine returns. Do you ever call this routine in your code? Maybe that's a hint where these boxes are generated (as Gibson noticed, some of the ADCS examples do this).

Hope this helps,

Christian

[bw-dijon]

Hello Ceule and Gibson,

You were right, there is a remaining "ndStatusToString" and "MessagePopup" from older version deep in my source code.

thank's to you and sorry for my inattention.

 B.W.