cRIO 9067 to hired 7fh USB RS232

Hello

I have a cRIO 9067 and would like to interface with an instrument that has a converter USB-RS232 from SiLabs.  I can't comminicate with this instrument easily on a Windows PC.  I am able to see the device in MAX when its the cRIO connection.  IT appears under "Devices and Interfaces" as "USB0::0x1FB9:0 x 0100: 121A00A:RAW ' with model number and description of the device.

I followed the description at this link, but I don't get a ttyUSB # devices.

https://decibel.NI.com/content/docs/doc-34827

Is it possible to get this working on the cRIO as a serial port?

Thank you.

After some research, talk with people, NOR google and to talk with people to lakeshore.com (provider of the device) this is what I have reconstitute on how to make this work:

  • Under Linux, usb devices are listed automatically, and by default, will appear as a USB RAW device

  • Once the USB device has been identified, it can then subsequently be linked to a driver

  • Linux determines if and when to link each device USB-based device Vendor ID (VID) and the model identifier (MID). It is usually 3-4 digit hex string.

  • In the case of the Lakeshore 121 power source, VID = MID 1FB9 = 100.       I could see in MAX for the Raw Device USB.

  • There are two levels of USB-serial device drivers. The first pilot: usbserial.ko is a generic driver that handles all USB-serial devices. This should be loaded for any USB-serial converter.

  • The second driver is specific to the chipset for the USB-serial device.       For the cRIO, there are three options which are pre-installed (DFT, 7fh and a few others)

  • The drivers can be found at /lib/modules/3.2.35-rt52-2.0.0f0/kernel/drivers/usb/serial/ (where the kernel version directory may vary)

  • Lakeshore 121 uses the TR labs CP210x chipset, so we chose this one.

  • Records of the device first of all need to be loaded by Linux. Linux can automatically do this by adding files of length zero in the module.autoload.d directory. To do this run the following:

    • CD /etc/modules.autoload.d

    • Touch usbserial

    • Touch cp210x

    • restart cRIO

    • run dmseg. grep usbserial to confirm that usbserial driver is responsible

    • run the dmesg | grep cp201x to confirm that the driver for cp210x is loaded

  • The next step is to associate the cp210x of our device USB device driver. Don't forget that linux associate unit to a pilot from the VID and moy. anyone installed linux cRIO base, I'm sure, knew nothing of the VID 121 Lakeshore and MID.

  • Lakeshore recommended to read the source code for cp210x, adding the VID and MID to the list of recognized devices, recompile the cp210x.ko file and install it on the cRIO. It would work, but it is beyond my current Linux capacity.

  • Linux offers the possibility to dynamically add MID, VID, so that a device can be recognized on the fly

  • When the driver CP210x is loaded, a struchture of the entire directory is created. There is a file because the directory structure called new_id where you can dynamically added VID, mid

  • Create a startup script to run the following command. Be aware of the problems of termination of cr/lf line between operating systems. It is generally easier to create the script on the cRIO with the VI editor to avoid any problems.

    • echo 1FB9 100 > / sys/bus/usb-serial/drivers/cp210x/new_id


  • Now, restart (or running the script), you will get a device/dev/ttyUSB [0-9]

  • Unfortunately, the creation of default of the unit ttyUSB [0-9] does not permission to write, so we have need create a UDEV rule to automatically grant writing

  • Add the following lines of code udef.conf in the folder/etc/udev

#typical devices

ttyUSB [0-9] * root: ATS 666

  • Create a file named 99 - ttyUSB.rules in the /etc/udev/rules.d folder

  • Add this line of code in this file:

KERNEL == "ttyUSB [0-9]" * ", OWNER ="admin", MODE ="0666""

  • Restart the cRIO. This should be it! It worked for me.

Tags: NI Hardware

Similar Questions

  • error when trying ot read more large block memory on cRIO 9067 LVRT 2014

    I get error "-2147220623" when you run the following code on a cRIO 9067. It works on the cRIO 9074


  • Support for LabVIEW 2014 and CanOPEN cRIO-9067

    Hello

    We have NEITHER 9881 CANOpen communication module and cRIO-9067.

    According to the NI 9881 product description page the module should work with cRIO-9067. However, does not support the latest NOR-Industrial Communications for CANopen 1.0.3 2014 LabVIEW and NI RIO 14.0. This means that we cannot use cRIO-9067, can we? If so, when the next version of the pilot will be available? It will work with the cRIO-9030?

    Thank you in advance,

    Nikita.

    Hi Nikita,

    I wanted to let you know that support for the cRIO-9067 is available: http://www.ni.com/download/ni-industrial-communications-for-canopen-14.5/5234/en/

    Thank you!

  • install software failures on cRIO 9067

    OK, I got a new cRIO 9067 and I noticed, while installing software on it well as MAX, everything works as long as I CHOOSE NEITHER WATCHDOG 14.0.0.  If I do, I get the following error. It's very repetitive.

    This is another so that I installed, otherwise:

    Hi Mark,

    The driver OR Watchdog is part of LabVIEW Real-time, sounds like something might be wrong with your installation of the Module LabVIEW Real-time on your computer.

    Can you uninstall and reinstall the Module LabVIEW Real-time and see if that fixes the problem?

  • Same code compiled for the cRIO-9074, but reports no diagram component calendar violation for cRIO-9067

    Hi, just got my new cRIO-9067. I have converted my project over the cRIO-9067 since the cRIO 9074. Same layout module, same engine, same scan code custom fpga, (hybrid mode).  I have no problem of compilation for the 9074, which is a lower performance FPGA architecting the 9067 FPGA.

    The final timetable for windows compilation shows that the timing is respected for all clocks - 40, 80 and 120 MHz (I use a clock derived for some code sctl). During the end of compilation, during the phase of gen bitfile, I get the dreaded time violation. Investigation of the breach indicates that it is not the custom code, it is not schema components. One of them seems to be linked to the card series OR 9870 I in the chassis.

    Why? Is there anything I can try with the compiler directives for this problem? You would think that it would be easier to compile for the highest performance FPGAS...

    OK, don't ask me how I thought this output - to run I changed nothing else than this: feed the I/O node a reference FPGA of e/s instead of configure the node via the menu "link to. It makes no sense, but the compilation succeeded when I did this.

    I know it is because I created a very simple test VI in my project and made sure it does not compile without it.

  • USB-RS232 Modbus

    Hello world

    I am a beginner in LabVIEW and I am trying to acquire data from a microcontroller with Modbus Protocol in series. I use a converter USB-RS232 to prolific technology and Windows 7 as operating system.

    I can't communicate with the card that contains the microphone. I get an error 1073807246 ("the resource is valid, but VISA cannot gain access to it").

    I can't even set it up on VISA test Panel.

    Someone at - he never tackled this problem and knows how to solve? Maybe it's because the USB-RS232 converter?

    Thanks to all the advice for any advice.

    Andrea.

    If you had searched the error, you would have found the most common reasons for it. Make sure that no other program is using the same port. Windows allows more than one process to access the same port.

  • With LabVIEW how to control an instrument with a RS232 output, using a USB RS232 converter cable.

    With LabVIEW how to control an instrument with a RS232 output, using a USB RS232 converter cable, since I do not have rs232 ports. I have two instruments I want for the control in this way. One is a guarantee of strength Imada SPAS with RS232 output. The other is a micrometer Panasonic HL-G103-S-J laser sensor which is RS422. I have done significant programming LabVIEW using GPIB, but I have no experience with devices such as these. No matter what tutorial or examples would be greatly appreciated.

    Thank you.

    When you plug the USB-RS-232 converter, it installs a driver under Windows which makes it look like any other RS-232 port.  You may need to install the driver of everything that came on the CD with the converter.  It will get a Com as Com5 port number according to what is the next available number.

  • acquisition of images to remote USB vision cRIO 9067

    I have a 9067 linked to a camera USB from Basler.  I am able to correctly display images via MAX and the example of Grab until I run the Grab sample on the target of RT.  However, I need not to images processed on the RT or FPGA in this application.  Is it possible to open a connection to distance from the camera to my computer using IMAQdx host?

    I was hoping I could use something like "[cRIO IP address]: cam0 ' in-camera address, but that doesn't seem to work.

    Is this possible or do I pipeline manually the images of the RT target?

    Thank you

    Omar

    Hello Omar.

    You can access the camera image directly addressing it through the cRIO. You will need to implement the transfer of images between the host PC and the cRIO. Fortunately, you can do this quite easily by using a variable flow or shared network image.

  • USB RS232 "is connected Port" "invalid property value".

    I'm quite new to this so if all the below is not clear or needs more explanation Let me know and I will try to provide information.

    I'm trying to integrate a device in my LabView program. Of its guides, that I could find on the site OR mentioned most NI MAX goes first and then working them down. My camera is an RS232 port, so I connected via a USB converter, and I know that I'm looking at the right port (COM5) to look at the section "manage devices" on the control panel.

    All series settings are set up properly, I would say (the user manual ishere, with 17 being the party and my setup herepage). I tried to test commands, he gave me on the input/output section, but constantly came up with the error "VISA: (Hex 0xBFFF0015) timeout expired before the operation is complete." Initially, I thought I entered orders incorrectly, I find instructions in the manual that is confused, especially compared to the things other users have posted on orders ('\r' and '\n' instead of what I am told to write, but I agree that mine are not always literal characters).

    But when I went back to "Display attributes" connected "East Port" final attribute has an error with the "invalid property value" and the warning Hex 0xBFFF001Derror. Because of my inexperience with all this, I don't know where to start really trying to solve this problem, or what measures are in place, I need to do to start working properly.

    All advice is appreciated. Thank you

    The property "is connected" is only for devices of NOR so if you have another brand of converter, you would ignore the error.

  • cRIO 9067 problem of chassis

    I tried to configure a target 9067 cRIO. I have properly configured unit (last RIO drivers and firmware 2015...).

    My problem is when I create a project, I can see and connect to the target, but I see the chassis without any number or modules.

    I can see the modules in Distributed System Manager and they give the eigenvalues, but nothing on my project.

    I appreciate all the help with this isse confusion.

    [Note: when I add a target to my project I don't get FPGA/Scan mode selection window]

    Sounds like something was wrong with your installation of LabVIEW 2015 - have you installed LV2015 after the drivers? If so, support for the development of the LV2015 would not be installed - I would try to repair/reinstall the drivers.

  • How to send data to a usb RS232 port 6009?

    Hello world

    The converter that I intend to order has a RS232 port (terminals 71 and 72 according to the schema; RXD and TXD) and the use of this I can set and read parameters and control commands. I want to use the DAQ USB 6009 therefor. The format of data will take place as follows: -.

    A logical bit - 0 start

    Eight data bits

    A stop bit - 1 logic

    There are only 3 acceptable speeds which are 300, 600 and 1200, because the converter is very old.

    This makes my head completely, because I can't imagine a solution. Is it possible for the acquisition of data USB 6009 card?

    Any help will be appreciated

    Kind regards

    Sandeep

    If you want to control the converter RS232 commands, you must use a RS232 device. If your PC is not a COM port (free), you can use a good USB2RS232 converter market. The driver accompanying will provide a COM port for the OS and with the driver NI-VISA you can use in LabVIEW. Perhaps it is a LV-driver for the controller, just check the network OR Web driver.

    Will need you a cable custom at least three sons of the COM port (usually a DB9 connector) to the converter. GND (DB) - PIN5 at 55, PIN 2 to 71, PIN 3 to 72 (maybe you need to Exchange 71 and 72, if you can't get a connection, more details should be in the converter manual).

    You can start with hyperterminal for a first check, or use the RS232 interface - simple to write and read vi found in the examples of LabVIEW-help-find (don't forget the stop here character ;-)

  • H6510BD home automation projector (usb, rs232, ir)

    Hello

    Y at - it no availble documentation for controlling the projector with one of these options.

    (1) usb driver

    (2) rs232 codes

    (3) ir codes

    Kind regards

    SAL1

    I enclose the RS232 codes for this model of projector. I hope it's useful.

  • Unable to communicate with the host computer using the network University compactRIO

    Please move this topic to the appropriate section if it is not the right section. I can't locate a Council called the compactRIO. Thank you very much.

    I encounter this problem of network communication with my cRIO 9067. the linklocal or USB connection is fine but not static IP connection on the network. I contacted the it Department to assign me a static IP address for my MAC address of cRIO. In our University, they block only unknown MAC address access and the cRIO is in the whitelist. Here are the details

    cRIO attributed to IP address: 129.12.54.xxx, tried both netmask 255.255.255.0 and 255.255.0.0, no luck

    the host computer's static IP address: 129.12.50.xxx, subnet mask 255.255.255.0 (information of cmd - ipconfig)

    First question would be: they are on the same subnet? I need to make sure that even if scientists confirm that.

    Secondly, I followed https://www.ni.com/getting-started/set-up-hardware/compactrio/static-ip by using the IP address assigned, but not luck. I've noticed that I configure same address type cRIO static IPv4 using the USB connection or for local link mode, she went in DHCP mode or Local link once I unplug the USB and restart it.

    Whenever I restart MAX, connect the cRIO and my host to Ethernet jack on the wall, it shows the DHCP mode or link with assigned Local 129.12.54.xxx IP and the subnet mask 255.255.255.248. In addition, I am not able to change it in a drop-down list even after removing it and restart MAX indicated by tutorials OR.

    If you need more information, please let me know.

    Help, please!

    Jinyu

    Dear Mikko,

    I am pleased to tell you that the problem has been resolved. The cRIO works very well.

    The reason why it does not work is in first place because they are in the other subnet. For my school, my host is 12x.1x.54.130 and the IP assigned to my cRIO is 12x.1x.54.131. the subnet mask is 255.255.255.0 number marked in red must be the same for the cRIO is connected correctly.

    Kind regards

    Jinyu

  • USB to RS232 (adapter OR or not)

    Hello:

    I have to use a USB-RS232 adapter to connect my laptop to a device for the control.
    The control will be through LabView library VISA.

    However, I found that the price for the USB-RS232 adapter varies a lot.
    NOR has one (http://sine.ni.com/nips/cds/view/p/lang/en/nid/12844), more than 100 books, whilte there are many other USB-RS232 adapter costs only 10-30 pounds in other locations.

    What I wonder if do USB-RS232 adapter or this price?
    Is there a compatibility issue (single adapter of NOR is compatibile to LabView?) or other conduct issues I should be aware of?

    I just want to understand the difference between adapter OR other less expensive adapter before making the purchase (but I will not avoid the issue of compatibility)

    Thank you very much
    Best regards, Jhensi

    Jhensi,

    There are many companies making USB-RS232 adapters that work with LabVIEW using NI-VISA.  The problem is that some cards drivers are not fully compliant with the RS232 specification.

    Another thing to consider is the isolation.  If you are in an industrial environment you wish to an isolated USB-serial adapter.  Personally, I use adapters of NOR and electronics of B and B.  If you search the forums you will find other manufacturers mentioned as well.

  • USB to RS232

    I WAS using a NI USB-to-RS232/4 hub and communicate successfully with an external device for a few days.  He decided to vacation elsewhere, and I found myself in extremis.  In the Discussion, looking for help (I think) "USB to RS232", I came across a post from someone with the same problem.  After trying the solutions proposed by OR, which I did as well after a long discussion with the support of NEITHER, the guy with the same problem solved by buying a USB hub to RS232 CommFront.

    I cannot find the thread now and can't get MAX to recognize the hub of CommFront, so I can't be a VISA resource. I uninstalled and reinstalled the driver NI-VISA and NOR-Serial 3.9.1 the hub appears in the device as Manager "usb > rs232.»  I would like to contact the person who started the thread I negelcted to record to learn how they have solved the problem, or am desperate for suggestions on how to get stuff NOR recognize an alien species, as the hub of CommFront.

    Thanks to you two.  I was able to change the name of "COM" after searching a bit in the Device Manager.   In series with the external instrument communication is now possible. I learned a lot of things.

    NOR should have a third option in the trade of these messages.  In addition to 'Reply' and 'Accept as Solution', the third option would be ' response and accept as a Solution. "  In this way, the thread can be closed while still giving the opportunity to thank those who provided solutions.

    Thanks again.

Maybe you are looking for