From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-XNET (Hex 0xBFF6309A) Different Cluster Settings

Solved!
Go to solution

I updated NI-XNET on my system and the rt target and now i get this error:

 

Pible reason(s):

NI-XNET:  (Hex 0xBFF6309A) The interface has already been opened with different cluster settings than the ones specified for this session. Solution: make sure that the cluster settings agree for the interface, or use a different interface.

0 Kudos
Message 1 of 5
(8,484 Views)

I tried removing and re-adding my XNET databases as well as re-deploying with veristand.

0 Kudos
Message 2 of 5
(8,483 Views)
Solution
Accepted by topic author MPCC

MPCC,

 

Can you click on the CAN Port in the System Definition and make sure the Cluster settings were maintained?  I've seen this option get reset before.

 

System Explorer - CAN.png

Message 3 of 5
(8,475 Views)

OK So I tried that. The X-NET Database section was empty. So I corrected it with the proper X-NET Database.

I verified that the CAN Cluster is accurate to the CAN Cluster in the databases. Then, I tried to redeploy with no luck. I am still getting the same error.

 

Now that I am heading down this path, I just updated to NI-XNET 1.4. Is it possible that a setting somewhere else got hosed when I updated?

 

0 Kudos
Message 4 of 5
(8,469 Views)

It was a baud rate issue.

I had the wrong rate set up.It must have gotten reset with the other settings.

 

Thank you!

0 Kudos
Message 5 of 5
(8,456 Views)