XNET error

Similar Questions

• XNET error-1074384886 when receiving a frame ID 29bits

  I use XNET to send and receive several chassis with 11 - or 29-bit ID. In the attached vi you can see, I have send the 1st frame "Veutexprimer1" on the bus and I had received a plot of ID 11bits, and then I send two executives Write '2' and 'Write3"one by one, then I also receive a frame 11bits as answer. So far, all things work well.

  Then comes a problem: after the read "2" when I send a "Write4" frame, which would have an answer (read3) with the ID of 29bits, the vi can operate correctly only once, so I have to shut down the power supply of my camera until I run this vi for the second time, otherwise I'll get an error (see the attatched file). But if I send a frame which has a response with the ID 11bits, this vi still work fine. Would you pls help me for this? Thx a lot.

  

  Why do you think it is a problem XNET?

  Are you sure that your device can receive your order Write4 twice?

  If you need for your device to repower in order to receive a response from a command, then an internal condition/problem of your unit.

  Have you tried with other programs CAN?

  Have your tried to use the XNET monitor to send commands and see the answers?

• Wired OR XNET session with TestStand causes Hex 0xBFF6309C error

  Hello

  I'm trying to access a Controller LIN via code (2012) PXI-8516, OR XNET and of LabView, TestStand (2012).

  To the point where "XNET session creation", I created two sessions (one for writing, for reading), everything works in LabView and without errors. Then I put these sessions to an indicator in TestStand. It sessions are stored in the premises and put them in the next call where I ty to send a frame.

  The result is always a 0xBFF6309C aka 1074384740.

  A test program that keeps everything in a States Labview machine behaves as expected and sends the frame without problems.

  The error for me text sounds me a bit as if sessions are not particularly be crossed TestStand.

  Everyone has experienced similar problems?

  Best regards

  Søren

  Solved!

  Obviously XNET him quite like if the screw using XNET not stored in the reserved State. It is a setting of the adapter of LabView in TestStand.

  To avoid unpleasant surprises and days of searching for error when porting software to an another machine-TS, you can also set the setting of the card by a line of code:

  RunState.Engine.GetAdapterByKeyName (FlexLVAdapterKeyName). AsAdapter.ReserveVIs = True

  I always consider this behavior if it is a bug, then at least a problem. If keeping the session in respect of these circumstances is not possible at least that TestStand should provide a better error message pointing out what happened.

• Error 0xBFF62133 with NI-CAN on NOR-XNET

  My C application was written with the NI-CAN Channel API and works very well on the old cards PCI - CAN. Now he runs on a PCI-8512 OR XNET 1.3.0 with the NI-CAN 2.7.2 compatibility library and falsely, it gives this error: "NI-CAN: (Hex 0xBFF62133) you set an attribute that is not supported when Virtual Bus Timing is off." Refer to the section of frame channel Conversion of the NI-CAN manual for a list of the attributes that return an error when Virtual Bus Timing is false. Solutions: 1) Set Virtual Bus Timing true (or leave as default). "(2)"do not set the attribute not supported."

  My application does not frame channel Conversion or the virtual Bus to use directly, it turns to speak directly on the bus hardware CAN0 via the channel API. Use the compatibility library the virtual Bus?

  How can I avoid this error?

  Thank you.

  So the actual error you see is 0xBFF63133, not 0xBFF62133 (starting with 0xBFF63 - error codes are errors OR XNET). This is due to a bug in the way the database is imported (several threads all try to create a cluster with the same name, where the error "name of the cluster in double").

  While the bug will be fixed in the future, in the meantime, you need to make calls to sequential nctInitStart. I recommend a small function that catches a global mutex and then calls nctInitStart. Sorry for the inconvenience.

• What are the causes of error - OR-XNET: the NOR-XNET driver is no longer can communicate with the device.

  Hello

  I use X-NET-PCI8512, OS: Windows 7, C++ (middle of the QT interval).

  I'm pooling of card data (StreamIn member function) to ~ 100 Hz. card reading time (ReadStatus) to ~ 100 Hz.

  After about 40 min (depends on the amount of data in) I get this error:

  (Hex 0xBFF630B2) The NOR-XNET driver cannot communicate with the device. Solution: Make sure that the device was not removed from the computer.

  What are the causes of this error?

  Thanks in advance,

  Aviad

  Hello aviadCielo,

  When you get this error, what does do to make it work again? If you restart your program, start all this work?

  Secondly, what version of NOR-XNET do you use? It's maybe a software problem that could be resolved by upgrading to NOR-XNET 1.6.

  Finally, can you reproduce this problem with a simple program? If so, you can join the program you use?

• PXI-8512/2 XNET CAN stops when bus errors occur on Spadina

  Hello, I use the PXI-8512/2 in a noisy electrical environment so I often get errors on the CAN bus. I noticed that often 8512 stops communicate. In my dual port 8512/2, 4, # LED that flashes normally will eventually turn off. However, I have other devices listening on the same bus; report errors, they continue to stay alive. Is there anyway that I can get the 8512 continue to work in the presence of errors? I use the custom device XNET for VeriStand 2009 and do not see the error handling options. In fact, I don't get any notification of errors at all. I just noticed that my incoming CAN stop signals and my leavers have no effect. Thank you.

  Hello

  You shouldn't have to remove from your devices.  Just update the configuration and engine llbs and restart the Explorer system, save your configuration and redeployment.  Let me know if you see problems.

  (There are new files also copied into the directory of device custom if you want to use the bus monitor function... so you can replace the entire record of the NOR-XNET if it's easier).

• CAN grasp the material master Timebase rate returns an error with new hardware OR XNET

  Hi all

  I have a project that communicates on a CAN bus. It has always worked well with a PCI-CAN/2 card, but when I tried to use it in combination with an NI PCI-8512 (NOR-XNET) newly purchased card, it returns the following error:

  "1074388560 error has occurred CAN set material master Timebase Rate.vi

  NI-CAN: (Hex0xBFF621B0) the specified feature has a drawing or model under the NI_CAN which can be made compatible with the hardware, NI - XNET CAN. »

  Yes, I have installed the NOR-XNET for NI-CAN compatibility library.

  The error occurs during the initialization of the RTSI connections for synchronization, that VI is attached.

  I guess that this code is based on an example found in LabView.

  When I remove the BOX: block Set (material master time base rate) property, there is no error and the rest of the application seems to work very well.

  Can someone explain what is / was some timebase setting the internal clock of 10 MHz before connecting a RTSI line for her?

  Are there side effects caused by the elimination of this step?

  Should I still include if I run the application in combination with the old card PCI-CAN/2?

  Thanks in advance.

  Hello Pianne,

  Based on our discussion in class, it seems indeed as part of your existing code is written in a very specific way which is not entirely compatible with the XNET approach.

  Indeed, it would be useful to have 2 separate versions of this init VI (and other CAN-code) of your code and allow you to decide which one to run your top-level application, depending on the setting used.
  A HAL as approach could still be used in this case.

• XNET - activation of the RPC Server - error

  Hello

  I am trying to load XNet database on my RT goal and now I get the error using the Xnet API. Running multiple remote database manager XNet vi doesn't help not either as it is still stuck with the error and no waiting period.

  I can connect to my goal of RT so this isn't a firewall problem and I can even speak using the NI-Xnet database default value, it's just that when I try to load my database on the remote control it gives me these errors

  I tried to go to MAX > tools > NI CAN > RT Configuration and I got this error as shown in Capture.PNG.

  I use cRIO 9067 and Xnet, I use NI9860 on my 8th slot.

  Has anyone encountered this problem, enable RPC server, how can I do? and is it possible to directly pass the file of database on the target of RT.

  Thank you

  Well, I have done what I wanted, except for the problem to be solved "RPC error not found" issue.

  I don't know, but in my case database deployment worked when I changed the password authentication, initially I had a configuration password for my RT goal, but when I removed the password empty, all the screws, Manager NI-XNET database example started working.

  I know, there was a suggestion in some links to enter ' [usernameassword]@IP address] "but it did not work for me, even in the database manager Xnet is mentioned anywhere that the IP address must be entered in this format, what they ask is the IP address in my case it did not work with IP address.

  In addition, one thing to note here is that, by default when you receive product OR there is no password protection, usually the password is empty, then most of the user would have never encountered this problem.

  So I would say the resolution as "Remove password of target RT.

  Thank you

  Lakhvir

• XNet 16.0 Database Alias Change?

  Has there been a change of 16.0 XNet that put additional restrictions on alias names can be a database?  A user of my software is to see a strange error saying they don't have anything in their name of the alias other than superior or letters, lowercase letters, numbers, underscore, and dash.  Software I wrote takes a DBC and adds and assigns an alias, which is the name of the CAD file, but this does not seem to work.  I'm fine with my software update to replace characters with underscores, since it is simply an alias internal that the user does not need to know, but I did not see this listed in the change log.

  Change restricted the acceptable characters for:

  • Uppercase (A - Z)
  
  
  • Lowercase letters (a - z)
  
  
  • Numbers (0-9)
  
  
  • Line of underscores (_)
  
  
  • Hyphen (-)

  For the most part, who reflects C variable naming rules. I will pass your comments on the restrictive nature of the team.

• Need help for reading in parallel on the same interface and writing XNET

  Hello. I need help to configure CAN interface to write and read from the same interface.

  I use NI PXI-8513/2. I use CAN1 as interface.

  My had TO send status messages CAN every 100ms. I have to read in order to return akntoowlege to keep DUT CAN interface happy and not make mistakes.

  So, I want to open Strim Session and readall frames in the loop. At the same time, I need to be able to write in a frame HAD at the time...

  I only need to read one picture at a time too, but since I know the ID, I can pull it from the stream.

  What I'm confusing all is how to put in place the same CAN1 interface to be able to write and read in parallel.

  I think I would get errors that interface is already in use.

  Since I'm new to CAN, I was read and write only when necessary. But, sometimes I was getting errors on my messages. Sometimes I get message, sometimes miss me. But, when I run CAN test criminal as sniffer he sends and written every time. I was told it's because it recognizes all messages.

  I opened to suggestions of how best to implement the interface.

  I guess I can use CAN2 and separator to work around this problem, but I would use an interface if possible.

  Thank you

  Hi Rus,

  The XNET hadrware takes care of most of the low level of detials for you. The reading and writing of the circuits are both connected to the bus at any time. When you write to the hardware it will try to put a frame on the bus at the first opportunity he can. If the frame loses arbitration material re - will attempt to send the frame up is successful. Reception equipment monitor activity on the bus, regardless of what it conveys. The material received will usually throw a framework that was sent by communication equipment, but there is an Echo property pass to circumvent this behavior too.

  Take a look at the example of the expedition: MAY-> NI - XNET-> Sessions-> multiple Sessions Intro-> CAN even exit entry framework Port unique Point.vi. Keep in mind that this example you will need to use a second CAN interface to recognize frames, it transmits. I would recoment against the example CAN output Frame Single Point which would mimic your ECU if you choose a type of cyclic frame running this example.

• Impossible to deploy the database of NOR-XNET to target RT PC

  Hello

  I am trying to deploy a XNET database to a target RT PC simply by following the tutorial here: http://digital.ni.com/public.nsf/allkb/9847EF6F2D867BC186257DCE00626236

  However, when I click on deploy nothing happens; I get no error message and the database alias does not appear as present in the aim of RT (the entire list is empty for the RT target). If I run my code, he complains about the database not being is not present, so I don't know that it isn't here.

  I checked with Max OR and target a NI-XNET 1.6.0 installed. I'm using LabVIEW 2015. I have no problem connecting to the target. I tried an another new database created with LabVIEW 2015, without going. I tried to disable the Windows Firewall as suggested in a similar position (http://forums.ni.com/t5/Automotive-and-Embedded-Networks/Unable-to-deploy-NI-XNET-Database-to-RT-Tar...), but that no longer works.

  Help!

  Thank you

  Hello

  It seems that I have the latest version of XNET on my target and the crowd at the beginning, but just to try something I did the following:

  • I have reinstalled XNET on the target using NOR-MAX. I had to uninstall dependency package "nor-xnet for NI-CAN compatibility library", before doing this.
  • I have uninstalled and installed the last XNET on target as well.

  After that, things worked!

  Thank you

• CAN the c series modules and drivers XNET and Ethernet expansion chassis cRIO compatibility issues

  Hello

  I encountered a problem with my current setup which was not picked up by the tool advise cRIO or by the engineer of applications OR that we used to check our configuration before starting the project.  It turns out that the NI 9853 CAN modules require a XNET driver that is not compatible with the NI 9149 expansion chassis.

  We currently have a system with a cRIO NI 9068 with general IO and some CAN controller and CAN open modules in a carrycot and an Ethernet NI9149 with more general IO expansion chassis and more CAN and CAN open an another pod remote modules and all of this should work under water, so I can not move the modules of the expansion chassis to the chassis controller without a lot of overhaul of the system and equip and a team of angry engineers and technicians.

  I have developed the FPGA code for the 9068 OR and have CAN and CAN open networks works with happiness.  Then I tried to copy the same FPGA code on the expansion chassis and it compiles, but when I try to launch it I get the error-63184 code.  After long calls OR support, and tries to install the missing drivers on the expansion chassis, we discovered that XNET is not compatible with this chassis.

  Can anyone suggest the best course of action?  Is there an expansion chassis Ethernet that will support XNET?  I have here no information online about this compatibility issue that I can't find?

  I'll be communication with DIRECTLY, but from previous experience of the "odd" questions, I know the community often hold the key.  Any suggestions gratefully received.

  Thank you, Ed

  It's official.  CAN open modules are not compatible with the expansion chassis.  I have them moved to RIO and will get the upgraded pods.

  Thank you

  Ed

• Definition of FD CAN baud rate gives the error (using samples of C)

  I use C for XNET "FD CAN Frame Input Stream" samples where I put the valid values of "nxPropSession_IntfCanFdBaudRate" between 1000000-8000000. (according to http://www.ni.com/pdf/manuals/372840k.pdf#page=983)

  I am getting following error

  NOR-XNET status: NOR-XNET: baud rate (Hex 0x3FF63040) The FD CAN you provided is beyond the capability of the manufacturer of the specified transmitter/receiver. In our internal testing, we found this baud rate to run, but bus errors may be detected or generated during communication. See the Presentation of the material NOR-XNET CAN section in the software and manual equipment OR XNET for more information.

  I have a loop back configuration with a PCI card with 2 ports.

  It is a warning and not an error to inform you that you may be exceeding the capacity of the physical hardware. While the FD CAN protocol supports very fast transfer speeds, none of the manufacturers transcevier still created talkies that they ensure that all transfer speeds. Talk to them, the number one problem was do an EMC low enough to run in the vehicles. They tend to be actually able to follow the signaling rate.

  Therefore, we allow you to use NOR-XNET to communicate to a wide range of transmission speeds, but sound you the alarm if you are exceeding the rates allowed by the manufacturer. For most use cases, this can be ignored safetly.

  FYI, what baud rate you try to run to?

• Problem with sending of master header with XNET API instead of CAN frame API

  Hi nice guys.

  I am using the XNET API to switch Master slave with LIN Protocol task. Since I have no prior experience, there is something problem as the Interface of the NI USB-8476 s cannot be detected. Gifts of windows prompted the following information:

  Error-1074384758 is produced in .vi:1 XNET create Session (single-point output Signal)

  Possible reasons:

  NOR-XNET: (Hex 0xBFF6308A) the name of the interface does not specify a valid and existing interface. Solution: Use a valid and existing interface. These can be obtained by using MAX, XNET properties of the system, or the name of LabVIEW XNET Interface IO. If you use CompactRIO, see the topic "Getting started with CompactRIO" in aid of software and hardware OR XNET.

  but in the MAX of NOR, the device is detected as "LIN0. Even control interface entry in the examples NOR displays the error. But if I take the CAN API of frame, it works well.

  Does anyone have an idea. I'm so appreciate. Tanks in advance.

  Best regards

  Melo

  Dummy me, know that the XNET API still do not support the NI USB-8476 s, which I am applying.

  Kind of hard to use the API NEITHER of MAY to get the feature I need, that seems easy to get with the XNET API.

  Problem solved!

• NOR-XNET - invalid CAN interface

  Hello

  Main problem:

  I have problem to get CAN interface in my PXI rack up to-and-operational. The interface name is not valid

  Material:

  SMU-1078, with SMU-8820 and CAN controller module NI PXI 8512

  Software:

  LabVIEW 2015

  Driver OR XNET 15.5 (both portable and PXI)

  Description of the problem:

  When we look in MAX, OR XNET interface says I have two interfaces CAN named 'CAN1' and 'CAN2.

  It is also possible to use the funtion "blink port" successfully, CAN1 and CAN2.

  BUT, when you use the bus monitor feature, I got error saying that "given the Interface name does not specify a valid interface and existign"

  See pictures attached below.

  Also, when you try to use the code example, CAN Test.vi of closure, the same error occurs.

  Someone knows how to fix this?

  Other ulfjon

  

  

  

  Hello
  Thanks for the support.
  I found the problem
  When you use MAX first, to set up a session n xnet, MAX does close properly the session.
  So, when using the BOX of the labviewcode channel, will result in this error code.
  No, an explanation of very good code, but I would say.
  It is perhaps difficult for labview to know if the channel is busy or does not exist.