j1939 error

[jonathanupr]

I've got the J1939 protocol up and running on Labview 8.5... though when I create an executable it gives me these following errors upon start-up...see jpg.

Help???

[jonathanupr]

bump...goes bump...

is this a result of my programming or a flaw in the J1939 example?

[jonathanupr]

bump...

come on ... Anybody???

[Bill_in_Detroit]

Jonathon:  I guess I will have to do if no one else has time to answer.  I am assuming you are doing this on LabVIEW realtime.  Have you seen the NI paper at http://digital.ni.com/public.nsf/allkb/B3E498508BED720986256F7B006C0950 ?

It may be that all the necesary files you need are not on the real time chassis.

If you are not using realtime, make sure the files (mentioned in the article) are located in the same directory with your executable or its data file subdirectory (whichever way you have it setup, these need to be able to be found).

I hope this is helpful to you.

Bill 

[pflores]

Searching my system, I find this nirvicomm.vi file at

C:\Program Files\National Instruments\LabVIEW 2009\vi.lib\express\rvi\timingcommon\nirviCommon.vi

and

C:\Program Files\National Instruments\LabVIEW 2009\Targets\NI\FPGA\vi.lib\express\rvi\timingcommon\nirviCommon.vi

 Both places seem related to Real-Time applications. Are you using LabVIEW RT?

 Also, where are those J1939 Vi's from? Did you create them? Did you download a library from somewhere?

Thanks!

[Bill_in_Detroit]

Peter:  The J1939 files Jonathon is using can be found at http://zone.ni.com/devzone/cda/epd/p/id/6215 .  I recognize the names in the jpg he posted as from that library.

Bill

[jonathanupr]

thanks for the info guys... I'm using the 8473 CAN to USB converter.  Just from taking a look at the performance of my application...there really doesn't seem to be a legitmate reason for using an RT target for J1939 unless one is looking to do something such as a constant TSC1 control. 

The J1939 update rate for all the PGNs is quick, but the channels being updated are only getting posted once per second.

I'll take a look at getting those lower level VIs from 9.0 and converting them to 8.5...that is if they aren't already there on 8.5

[jonathanupr]

ah, and the VI code for the J1939 transport protocol works pretty damn well for reading in PGNs...a little modification needed but really not much.  As for writing to the ECU, haven't tried that one yet. 

[jonathanupr]

Yeah I'm a bit confounded on the library situations...I'm not using an RT target...

though when running the deployed executable/installer.... upon start it asks for these 2 dlls:  lvuste.dll & lvalarms.dll.   ????  how do I get around this?

I'm using 8.5.

[Bill_in_Detroit]

Jonathon:  Both of those dlls are loaded when you install the RT Event Based Sequencer Reference Example (search for 6084 on ni.com), which requires LabVIEW 8.6 or later.  However, it may be that these files may be installed by the Simple Messaging Reference Library (STM) (search for 2739 on ni.com), which is required by the RT EBS.  The STM only requires LabVIEW 8.5.  I have both installed and it is difficult to tell which one installed those files.

Hope this is helpful to you.  I understand the frustration of installing something downloaded from NI only to find the documentation was incomplete and the origins of necessary (or missing) components are less than obvious.  I have been working with LabVIEW for almost 16 years (it will be 16 years this coming June) and I still experience an occasional WTH? moment when working with new libraries and LabVIEW.  Fortunately they are fewer and farther between now.

Bill