ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

Automotive and Embedded Networks

cancel
Showing results for 
Search instead for 
Did you mean: 

Possible to Set Default Termination on NI-XNET Device?

Is there a way to change termination for an interface to be enabled by default?  I would prefer to change this once for the device rather than having to add the property node for every VI that creates a NI-XNET session.

CLA, CTA
0 Kudos
Message 1 of 6
(8,089 Views)

Hi LVB,

 

Unfortunately, the only way to change the termination is to use the property node and there is no way to default for a certain device. You could wire a control to the property node and set the control to have a default value but this still requires you to place a property node.

Patrick H | National Instruments | Software Engineer
0 Kudos
Message 2 of 6
(8,062 Views)

@Haagen-Dazs wrote:

Hi LVB,

 

Unfortunately, the only way to change the termination is to use the property node and there is no way to default for a certain device. You could wire a control to the property node and set the control to have a default value but this still requires you to place a property node.


How does the physical termination operate relative to stopping and releasing the XNET session?  am aware that the termination is applied upon starting the XNETsession.  If start then stop Frame Input Stream session, will the termination resistance persist upon stopping?  What about clearing the XNET Frame Input Session?

 

It would be nice to set a default termination for the card in MAX.  I'll add a feature request to the idea exchange.

 

Thanks,

Brian

CLA, CTA
0 Kudos
Message 3 of 6
(8,055 Views)

When you clear the last session, termination is disabled.

0 Kudos
Message 4 of 6
(8,049 Views)

@GPIB_Guru wrote:

When you clear the last session, termination is disabled.


So it seems I can "simulate" a default termination by first opening a Frame Input Stream Session with the desired termination.  I can then start and immediately stop that session (but not clear) to apply the termination.  Then the termination will be applied to all subsequent sessions until I clear ALL sessions...

 

This seems like a better option than adding the property to every XNET session.  However, it still does not address the limitation of default termination when NI-XNET sessions are not running.

 

Is there any way to have termination persist when an NI-XNET session is not running?

CLA, CTA
0 Kudos
Message 5 of 6
(8,045 Views)

Does any body know how to enable or  disable this property from a c# aplication using the Nican.h  a don't know how to do it I can see only these properties :

 

could you help me?

 

/* Configure the CAN Network Interface Object */
AttrIdList[0] = NC_ATTR_BAUD_RATE;
AttrValueList[0] = Baudrate;
AttrIdList[1] = NC_ATTR_START_ON_OPEN;
AttrValueList[1] = NC_TRUE;
AttrIdList[2] = NC_ATTR_READ_Q_LEN;
AttrValueList[2] = 150;
AttrIdList[3] = NC_ATTR_WRITE_Q_LEN;
AttrValueList[3] = 0;
AttrIdList[4] = NC_ATTR_CAN_COMP_STD;
AttrValueList[4] = 0;
AttrIdList[5] = NC_ATTR_CAN_MASK_STD;
AttrValueList[5] = NC_CAN_MASK_STD_DONTCARE;
AttrIdList[6] = NC_ATTR_CAN_COMP_XTD;
AttrValueList[6] = 0;
AttrIdList[7] = NC_ATTR_CAN_MASK_XTD;
AttrValueList[7] = NC_CAN_MASK_XTD_DONTCARE;

 

 

0 Kudos
Message 6 of 6
(7,461 Views)