04-29-2011 03:05 AM
Hello Wilbur,
I would like to reproduce the error. Which hardware do you use? The file you use is the example file you linked to?
Best regards,
Stefan
---
Stefan Egeler
Applications Engineer
National Instruments Germany
04-29-2011 03:34 AM
Hi Stefan,
I'm using the NI USB LIN 8476 for LIN bus.
Thanks for the help,
Wilbur
05-03-2011 10:13 AM - edited 05-03-2011 10:14 AM
Hello Wilbur,
I'm very sorry that it took so long.
I now was able to reproduce the error. I had a fresh and clean Windows XP SP 3 target system with only the LabVIEW 2010 SP1 Runtime and the NI-CAN 2.7.2 Drivers running on it. The executable you attached produced the same error you made a screenshot of.
I then built an executable from the VI you linked to, and it worked fine, even on the target system. Did you change anything within the VI? Please attach your whole project file from the VI including also your build specifications!
Best regards,
Stefan
---
Stefan Egeler
Applications Engineer
National Instruments Germany
05-03-2011 11:04 AM
Hi Stefan,
thanks for the try! I didn't change anything in the project. In fact I just wanted to show you that the NI-CAN in the execution is not working properly so I've used the universal VIs for instance.
The problem is possibly on the LIN bus kit. I've found that one VI in the LIN starter kit doesn't work well with LV 2010. However, I didn't change any thing in the user.lib.
It is also possible that the the execution builder doesn't make it right.Is there a function, which repairs the execution builder?
Wilbur
05-04-2011 02:16 AM
Hello Wilbur!
I am afraid I did not fully understand your argument. You built an installer with the example file Put master in sleep mode and remotely wakeup, is that correct? And this example file did not work either, did it?
There is one simple way to find out if your installer is the error factor: Build an executable for this file (not an installer!) and run this executable on your target system. As the system already has the runtime environment and the NI-CAN drivers, you do not need an installer any more. Please try it and tell me if it works.
To help you further, I would like to see and one on one compare settings of your project and mine. An error often seems to be an error of the programme and after some time you find out it was just a small setting that made the difference. So please attach your project file from the VI. Please attach it completely, so that it also includes your build specifications!
Thanks in advance!
Best regards,
Stefan
---
Stefan Egeler
Applications Engineer
National Instruments Germany
05-04-2011 09:34 AM
Hi Stefan,
in fact I've only built the execution and it always causes Error as you saw.
I've download the project from the website, maked no changes and built the execution. The execution is already posted in the first post.
As you wish, I post once again the project+execution.
05-04-2011 10:52 AM
Hi Wilbur!
Thank you for your answer. In the project there is not the same executable as you made the screenshot of.
The one in the project is
USB-LIN Sleep Control_LV80.vi
while the screenshot one was
LIN Master Send Header Frame and Receive_LV80.vi
But I compiled the executable of USB-LIN Sleep Control_LV80.vi without changing any settings and, voilà, there was no error again. So, as it seems, the execution builder on your development system ist not working correctly - as you assumed.
Now please try and repair your LabVIEW 2010SP1 via system control --> uninstall or change programs --> National Instruments Software --> choose "LabVIEW 2010 Service Pack 1" and press "repair". Afterwards please rebuild the LIN application, try it again and tell me if it works.
Have a nice day,
Stefan
---
Stefan Egeler
Applications Engineer
National Instruments Germany
05-05-2011 07:55 AM
Hi Stefan,
I tried the repair funtion and build a new execution. But the same error appears.
Assumed is the service pack OK but there's something wrong with my CAN (LIN) plug-in.
Best Regards,
Wilbur
05-05-2011 10:32 AM - edited 05-05-2011 10:33 AM
Hi Wilbur,
please do the following:
1. Build the executable again, but activate the following settings in your built in the category "advanced":
a, activate error search
b, error search bevore begin
c, create build protocol file
2. Post the executable and the build protocol file
I will debug the executable on the target system, hopefully we will get more information about the error this way.
Have a nice day!
Best regards,
Stefan
---
Stefan Egeler
Applications Engineer
National Instruments Germany
05-06-2011 06:58 AM
Hi Stefan,
here is the execution with the log file!