J1939 Add-on Feedback

[hfibonaich]

Hey,

Did you edit j1939 database with Ni database editor?  Could you share me the J1939 database?My email is lvzhengmeng_spt@163.com

Thank you for reply.

[Daniel_E]

Hey,

As previously stated, no NI products can be used to edit a J1939 database, including the NI database editor.  I cannot share my database with you as it is customer specific.  You need to get the database from the manufacturer of the ECU you are trying to communicate with.

[hfibonaich]

oh,I know.Could you recommend a software to edit database?

[Daniel_E]

Hey,

I don't know of any free software.  My customers use Vector for designing and debugging the network/database.  Then they use NI for automation.

[mkubo]

Does this 1939 add-on support NI 9862 on cDAQ USB chassis?  I tried this with the configuration VeriStand 2012＋cDAQ9174＋9862, but I received an error 15101 from NI VeriStand.

[Daniel_E]

I have only tested the custom device with the hardware listed in the web document.  I have not tested with Windows or any combination of USB chassis/sleeve/XNET card.  Therefore, I would assume based on your error, it is not supported.  I will look into it a bit further and add it as a feature in the next release if I find it doesn't work.  I would expect it to take three to four weeks for me to get a new release out.

[AGCOJason]

On the topic of compatibility, what would be required to get this Custom Device to work with VeriStand 2013?  I don't know what all has changed in 2013 yet (just installed), but any suggestions would be appreciated. I am in the process of assembling another HIL and it is kind of a test bench for updates that will be pushed back to our older systems.  I just setup VS2013 and DS2013 DS2.

Thanks

[Daniel_E]

You would need LabVIEW 2013.  You essentially have to recompile all the source code in LabVIEW 2013 and then re-build the source distributions.  I will be doing this by the end of the year. 

[AGCOJason]

I am working on rebuilding the project for 2013 (will send back if I get it working) and will give it a test as soon as I can.  I have hit a build error.  It looks like LabView 2013 can't handle the J1939 Host Automation API.lvlibp (I get an error about opening a file with an earlier version).  I don't know if this is a problem with LabView 2013 or with the library.  I can open the library in 2011 with no problem.  Is there a way to save the .vi's out of the packed lib with 2011 and then rebuild the lib in 2013?

Thanks

[Daniel_E]

I did test this on Windows and it throws errors.  I will add this to the feature list for my next version.  As of right now, Windows is not supported.