Problem of ECU MC PXI-8513

Hello

I created a LabVIEW tool that implements XCP on CAN. I have a SHIELD, and my tool works very well with a NI 9862.

Now, I transferred my software to another system with the PXI-8513. A normal CAN communication with XNET is working (rest bus simulation), but the command of 'CONNECT' XNET goes to timeout error-301096, and after that, I see only the frames of error in the bus monitor.

What is the difference about the ECU MC between 8513 PXI and cDAQ 9862? Any idea?

Madottati

Please check the termination can:

Physical layer CAN and termination Guide - National Instruments
http://www.NI.com/white-paper/9759/en/

Tags: NI Products

Similar Questions

  • PXI-8513 appearing does not in MAX

    I have a chassis NI SMU-1071, with embedded controller SMU-8100, DAQ, PXI-6229 and PXI 8513 CAN / XS.

    Today I tried to receive SOME messages by using the XNET Read.vi and Session.vi to create XNET but when I wanted to specify an interface, he couldn't find all the interfaces, while the VI is located on the remote system and the PXI card appear in MAX I have checked my drivers and noticed that I was running NOR-XNET 1.4 I decided to update to 1.5, hoping that would solve the problem, which he did not.

    When I opened MAX after the update, it detects the chassis, but it no longer detects the card PXI8513... He appears on a tab separated from XNET devices, but it has now disappeared. When I open the tab "Display Slot" of the chassis, he said slot 3 is unknown/Emty, although it houses the XNET card.

    The software running on the remote system is the "NI XNET 1.1.1", this could be the problem and if so, how can I change this?

    After reflection and reading this guide of errors (http://zone.ni.com/devzone/cda/tut/p/id/5403) I figured out I don't update the drivers on the target distance.

    After that I updated the drivers through the software tab of 1.1.1 and 1.5 everything works fine now.

  • Problem of delay time PXI-5105

    Hello

    I'm running the PXI-5105 (@ 60Msa/s/ch 12 bit 8Ch) using the attached VI. I put it to trigger off channel 0 to 1V.  When I put in a sinusoidal waveform of cycle 5, it seems that the scope triggers too late and I only see 4 of 5 cycles.  I confirmed this by generating a sinisoid of increasing amplitude across a PXI-5412 and again once the waveform has been truncated, as if there is a delay after that relaxation hit.  (btw, I have an oscilloscope running in parallel and the waveforms appear perfectly here)

    Why this is happening any help would be really appreciated.

    Thank you!

    Actually - problem solved.

    When I played with him I had inadvertently set it to DC coupling.  Coupling AC fixed.

  • OR PXI-8513/2 custom baud rate

    Hello

    I need a 667 k baud rate.  XNET database editor and Bus monitor only give options of 500 k and 800 k.

    Is there a way to specify baud rate 667000?

    Thank you

    Rates has worked?

    I have attached the VI that I used. It was something that I wrote for my own use, so he was not really polite to consumption. I had a few versions of this over the years, and I have no readily available material, so I can't guarantee that it produces the correct results. You must post probably travel to match the manual.

    To use it, you want to watch sample Max/Min points to fit your bus needs. For the CAN, this number is generally in the 1980s, but it could vary based on the length of the cable, etc.

    You can also watch the allowed error constant. He is currently 0.6, you can increase to be a little more tolerant. There are not many options at higher baud rates, 666667's about this for rates around here. You might consider making it a control to make it more accessible.

    If you find something like this useful, you can add a suggestion to the team to incorporate it, or something like that.

  • PXI-8196 connection problem: plugin not installed

    Hello OR:

    The PC in interaction with our NI PXI-8196 (1052 chassis) has recently had a hard drive failure, and I had to reinstall all our LabVIEW software and live custom on a new host. The software is running, but I have problems with connectivity to PXI. PXI is recognized to the MAX, and everything is accessible (ladders for our load cells, etc.). But when I open my project to a labview VI, I can not connect for PXI. It has a yellow triangle with an exclamation mark next to it, and when I right click, the error message indicates that the plug-in is not installed. I have a CD that seems to have the PXI drivers on it, but after the installation, I got the same problem.

    I wasn't the one who originally this system connected to the network, and I cannot find documentation to get back up and running. Any help would be greatly appreciated!

    Eric

    So I solved my problem with the help of my local applications engineer. He pointed to me and made sure that the software on the PXI system synchronized with the host computer via the MAX add/remove software menu. I noticed that the version of the RT software on my host was older than the version on the PXI system. Not sure why this happened, as I had already installed the most updated version. Maybe he got more written in my flurry of facilities. So I reinstalled the RT 8.2 module on the host, and now everything works. Thanks for your time, Robert.

  • PXI-8431, without going into fashion with VB6 reception

    I use a PXI-1045 chassis with a PXI-8431 RS422/485 card and communicating via a VB6 program

    Send the output of the PXI-8431 RS485 module works well when it is in mode, the signal levels are approximately 1v and 3v for high and low, but when it is in fashion, that the outputs remain to 1v and 3v instead of going in passive mode and the two floating lines at approximately 2v with approximately 300mV differential as it should receive. This means that when remote devices send, the amplitude of the signal is about half as they compete with the PXI module and the center point of the two signals are 1v and 3v respectively. Our software does not receive the signals of the PXI module that is compatible with my theory, that it is always in the mode of sending and taking control lines, or maybe he's changed 4-wire.

    I swapped the PXI card and cards remotely with our good system and the problem will not move.

    I have eliminated ALL the material on the new ring by replacing it with a 67 on the way pin 9 connector plugged D directly Ohm resistor on the PXI card. With a scope, I can see that the new system will not in passive mode, but with the same connector the old system works OK.

    The only difference I can see between the 6 platforms old we who work and the new 2 that don't work is the new ones use the the NOR-XNET-PXI-8513 and the 'old' use the card CAN PXI_8464. This software would be in conflict? Are there any other updates to the software OR which could be causing it?

    Philip,

    3.5.1 series had some issues related to the read/write mode series 2 wires, I would recommend corresponding versions of driver with your working system or upgrade to the latest driver of series.

    Kind regards

  • 8430 PXI cannot open serial ports

    Hi all

    I have problems using the NI PXI-8430/8 map serial ports.

    After installing the driver, the device works very well and the troubleshooter MAX serial shows all 8 ports as adopted and I can access ports.

    After a restart of the system, I can not access the ports of 8430. This utility lists all the ports 'Impossible' with the message "cannot open port.

    In the Device Manager configuration seems correct. Also, I find no error in the Windows registry (COMDB,...). Everythings seems good enough.

    I think that theres might be no other application that could take control of all ports, especially not after a reboot.

    I tried to reinstall the drivers, reorganize the com-numbers and I have already changed the material 8430. Nothing solved the problem...

    Does anyone have a solution or any ideas?

    My configuration:

    Rack of 1078 / controller: PXI-8135 / Serial Ports: PXI-8430/8

    Windows XP

    I have another system that works pretty well in the same configuration.

    Hello

    I found the solution. It was a conflict situations with the MT7 3 m touch screen driver.

    Special thanks to french colleagues, their position causes an appeal me the right way.

    Here is the link: http://forums.ni.com/t5/Discussions-au-sujet-des-autres/Ports-COM-des-cartes-NI-bloqu%C3%A9s-par-le-...

    You must disable the service "Search MT7 Service series" (configuration/Administration/Services Board). After I did that it worked well...

  • Try to install the software on target RT PXI 1082

    Hello

    I try to run a chassis PXI-1082 (recovered with factory settings), but I have some problems when I try to install softawre through NOR-MAX on it from another PC connected with the ethernet cable.

    First of all, I saw a PXI chassis BIOS problem when I started PXI chassis in RT mode: "ph_exec.exe is missing". PXI chassis started in SafeMode to RT.

    Secondly, I detected correctly chassis with MAX on PC with the correct IP address but when I tried to install the software on it, an error message resembles what occurred: ' no more space in the hard disk or input output error occurred. " I think that there is a consequence to the previous "ph_exec.exe is missing" message

    Could you please help me for this disorder?

    Thank you.

    ARM

    Hi Alexis,.

    Thanks for your reply. I am not able to open your link, but I found a solution on site OR: «Dual-boot Windows and Labview RT on a PXI controller»

    My problem is that my hard drive on the PXI controller is configured in NTFS mode and no partition in FAT32 mode existed. The reason why my PC says "no more space available" because it seemed to drive FAT32 partition. I am surprised that NEITHER do not included the partition FAT32 for RT. I've probably missed something. In any case, it seems to work fine now with disc FAT32 partition.

    I install the software on my lens PXI know.

    Thank you

    BR

    Vincent.

  • 5600 PXI runs do not self

    Hi, I have NI PXI-5600 on chasis 1045 PXI and PXI-5620, PXI-5610, PXI-5421, PXI-4461(from left to right in the pic)... Apparently, I have installed all the drivers correctly and the wiring... Screenshots of my connections and MAX windows are attached. I don't understand where is the problem.

    I have reset the device, but it does not work. think I understood the problem. It seems that the problem is not in PXI-5600. The problem is with the PXI-5620 because

    Or Pxi-1) 5600 showing "working properly" in the VISA properties.   Photo #1

    (2) PXI-5620 self test not available due to his inconsistency.   Photo #2

    (3) in goods NI PXI-5600, it cannot be linked to 5620.   Photo #3

    Now a similar solution is given here http://digital.ni.com/public.nsf/allkb/ABBB55946EB39A02862571FD0052024C

    My question now is that I HAVE IDENTIFIED THE PROBLEM CORRECTLY do I ignore the 'self test failure of the PXI-5600' and try to link that the way in which it is mentioned in the solution in the link above and my VNA PXI-5660 in labview will work well with it... Or y at - there a way to fix this incompatibility of the PXI-5620 with DAQ - mx...

    Thanks for your time...

  • 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.

  • wiring diagram for GM LAN

    Can I connect a PXI-8513/XS to a GM LAN using the pin 3 to GND, pin 9 to 12 VDC and PIN 7 CAN_H to the GM LAN?

    Need to connect pin 5 COM to GND? I use an unfinished Conect my interface cable for my camera

    Hello

    It is not necessary to connect pin 5 because this PIN match a shield in option. Here's the manual CAN where you can check the information (Single Wire CAN)

    http://www.NI.com/PDF/manuals/370289j.PDF

    According to the baud rate you use, you might have problems if not using a complete cable (low speed may operate, but at higher speeds, you may experience some problems).

    I hope it's useful!

    Concerning

  • Sending messages from CAN database-> error

    LabVIEQ Version 2014

    OR PXI-8115

    OR PXI-8513

    1. Version:

    I tried to select messages in a BOX (format .dbc) databases and direct it to a port CAN. But when I run the program I get an error regarding baud rate.

    Photos: Version1

    1. Version:

    After that, I tried to select the database directly, photo: Version2. Here, I get the error that the database cannot be opened. Another problem with this version

    is that so, I want to send several messages at once.

    I noticed that under Remote-> OR PXI systems 8115-> district data is no CAN of available channels, Max, who is the problem?

    I found the option in the channel of CAN-> Bus Monitor-> Interface and database settings.

    The error is resolved.

    Thank you!

  • [XNET] [CVI2013] Search for the periodic signal CAN

    Hello

    I use CVI 2013 and the toolkit NOR automobile 1.1 command the diagnostic value.

    OR PXI-8513 to edge (2 CAN bus)

    I want to know how to check if a periodic signal is currently subject to be sent?

    Best regards

    Blue

    I couldn't find an example of CVI that illustrates the use of the nxGetProperty function to get the calendar type and pass the time of a framework. If I have time Monday I'll try to create a.

    In the meantime, I can provide a quick snippet of LabVIEW to illustrate the general idea of how to get these properties of a session reference:

  • NOR-XNET and CAN - FD

    Hello

    The OR Web site mentioned the XNET interfaces are compatible CAN - FD. Could you tell me which are the XNET interfaces with FD CAN 11898 - standard 2:2015?

    Kind regards

    Hello SmileBoB,

    Supported devices:

    In general, the family of NOR-XNET CAN interfaces of is designed to be high performance modules that are easily adaptable to new standards and protocols. Since the physical layer CAN FD is very similar to that of high-throughput CAN, all interfaces CAN of NOR-XNET that support high-speed CAN communication also support FD CAN with bit rates up to 8 Mbit/s.

    The list of NOR-XNET interfaces that support communication CAN FD is below:

    PXI


    • OR PXI-8513/2

    • OR PXI-8513

    • OR PXI-8512/2

    • OR PXI-8512

    PCI


    • OR PCI-8513/2

    • OR PCI-8513

    • OR PCI-8512/2

    • OR PCI-8512

    CompactDAQ or CompactRIO


    • NEITHER 9862

    • OR high-speed/FD CAN cable transceiver for us with the NI CompactDAQ and NI 9860 compatible controllers

    For X-NET 15.0 OR > http://digital.ni.com/public.nsf/allkb/588B7A1E9F2419B086257F1D00667F8D?OpenDocument

    For NOR-XNET 15.5 and 16.0 > allows customers to choose between ISO CAN FD and non - ISO CAN FD in the software.

    Understanding CAN with data Flexible rate (CAN FD) > http://www.ni.com/white-paper/52288/en/

    I hope this helps!

    Best regards

  • Using the same interface CAN read and write

    Hello.

    Can I use the same CAN interface to read and write?

    For example:

    I send you CAN frame using CAN1 to my MCU.

    IF MCU confirmed the order of receiver it immediately sends the echo return command and there different ID to send the command.

    I tried to use CAN1 output framework and then reconfigures CAN1 to frame in queue and retrieve the frame of the echo.

    But it seems that I was always missing. The 'framework of CAN' kept vi expire.

    When I used the separator on the outlet BOX in my configured MCU CAN1 for frame and CAN2 for chassis in and I managed to catch the echo framework.

    I think about 100 ms for the frame in response that will be sent after the order has been received. It takes longer for the NI PXI-8513 reconfigure? Can I still do it, or I have to use the separator?

    I wad jump to use an interface to read and write.

    Thank you

    Ok. I misread your notion of echo. I understand now. I'm sorry.  The code you posted seems reasonable.

    (1) did you notice on or off for the session?

    (2) what baud rate? You can add a parameter of baud rates for the property to be explicit node.

    (3) I don't remember the name of VI, but you can add a status of Comm Get after reading. This will give you some information about the bus - if errors were detected, etc. Which can be useful to help debug.

Maybe you are looking for