NI-XNET Custom Device for NI VeriStand

[h_yong]

Thanks, O_Proulx, this is working for me so far!

[StephenB]

It should probably be pointed out that NI VeriStand 2010 has released and is available for download at www.ni.com/veristand

It has native support for NI-XNET and a greater set of features than the NIVS 2009 custom device. I highly recommend upgrading.

[h_yong]

Hi O_Proulx,

Your 1.5beta custom device has been working well for me so far. I have been able to update to new DBC files by managing/remapping my aliases.

However, when I tried to start a new system definition today and added CAN, I get the following error during deployment:

The target encountered an error and reset. Verify that the system definition file and the target resources are valid. You must deploy a new system definition file or reboot the controller to correct this problem.

Error -1074384538 occurred at _RT Engine v6.vi >> HP Loop.lvlib:HP Loop Main.vi >> Custom Devices Storage.lvlib:Get Device Outputs (HW Interface).vi:1 >> Custom Devices Storage.lvlib:Call Device by Reference (HW Interface).vi:4

Possible reason(s):

NI-XNET:  (Hex 0xBFF63166) You used an empty name for the XNET Session. Empty name is not supported. Solution: Use a valid XNET session name from your LabVIEW project.

To be clear, this also happens with 1.5 (without the software termination control), and this is with the same database that was working before in an existing system definition. I am wondering if I am forgetting something basic in the creation of my new system definition. I am giving a name, database and cluster for my add so I'm not sure why I'm getting this error.

Thanks.

[h_yong]

Hi, is there a way to indicate in the workspace that there is actually CAN activity on the CAN bus? It seems that all CAN signals default to displaying zero in VeriStand when there is no data received. Thanks.

[Schnoob]

Hi I want to manipulate the CAN Payload from the Workspace, so I try to set an DataChannel to change the Payload values at runtime. But now I get an Error 1074384541. An idea what the Error mean. Is it general possible to change the Payload at runtime?

[O_Proulx]

Hi Hyog,

I don't think you can detect if there are any CAN frames on the bus.  You could open the bus monitor and see if you are receiving frames, but adding an indicator on the workspace to say "activity" is not supported. 

Hi Schnoob,

The Custom Device only supports signals IO.  The reason for this is that VeriStand is mainly made for channel (double) data, and not array data (array of u8 like CAN).  The new VeriStand 2010 implementation has a feature where you can map the raw u8 payload to channels (for example, one channel for each byte).  That may help if you are trying to modify the payload directly.

I hope that helps.

[Schnoob]

Ok but is it possible to change this custom device to Frame IO and implement an CAN manipulation without an release change? I try to make for each Byte one channel and the Set Item Property.vi supportet U16 i think ?!? Thanks for quick help

[O_Proulx]

Ah, I guess you can setup a signal for each byte directly in your database.  You should not need to set any propery after that.  You can just add each signal to the transmitted section and then control that veristand channel from the workspace, or from your model.

[Schnoob]

I try to setup a Signal for each byte in the frame_section like the enable channel but as an U16 x 8. In the next step I want to read each signal from the workspace and change the payload. But I get an error when I deploy the configuration. How do you mean directly in database? In the Database are the Frames, signals and not enough space to store more information in the frame. I need this for a HiL simulation (ECU) and there are a lot of frames and signals. Can you show me an example how do you mean this.

[StephenB]

NI VeriStand 2010 has the feature you're requesting and should be provided to you for free with an active service contract. Since you get 1 year of service with the purchase of NI VeriStand 2009, you should have received NI VeriStand 2010.

Also, NIVS 2010 can mutate your code from NIVS 2009 so you can still use all your files.

Is there any reason you do not want to upgrade?