CANopen LabVIEW Library for Compact Rio (cRIO) + 985x ?

Hi
Has anyone made a CANopen LabVIEW library for the cRIO and the 9852 or 9853 modules ?
It should not be build on the NI-CAN API but must use the 985x driver "directly"
The CANopen NI sells does not support cRIO http://sine.ni.com/nips/cds/view/p/lang/en/nid/202614
Thanks
Teddy Roerby
Denmark

Hi Teddy,
I know this is late but you can check this link out:
CANopen Basics for cRIO: http://zone.ni.com/devzone/cda/epd/p/id/5474
Hope this helps,
Vincent Carpentier, Ing./P.Eng.
CLD
Neosoft Technologies
www.neosoft.ca

Similar Messages

Visa Error in MAX for Compact RIO

Hi,
I have a compact rio I haven't used in a few months. In Labview 7.1 and since upgrading to 7.1.1, I can't
connect to the compact rio. In MAX, I can see the crio device. When I open up the device, I get a VISA error
under Devices and Interfaces . 0xBFFF00A7 (VI_ERROR_MACHINE_NAVAIL). I can't ftp or ping to the crio either.
I have NI-RIO 1.2.
I connected to the crio console ....
General Software STPC Embedded BIOS 2000 (tm) Revision 5.2
Copyright (C) 2003 General Software, Inc.
Copyright (C) 2004 National Instruments Corp.
NI cRIO-9002 Controller
00000589K Low Memory Passed
00064512K Ext Memory Passed
Wait.....
PCI Device Table.
Bus Dev Func VendID DevID Class Irq
00 0B 00 104A 0201 Host Bridge
00 0C 00 104A 0210 ISA Bridge
00 0D 00 104A 0229 IDE Controller 11
00 0E 00 104A 0230 Serial Bus 11
00 0F 00 104A 0238 Ethernet 11
00 18 00 1093 70F7 Unknown Device 11
00 1F 00 104A 0981 Ethernet 10
(C) 1996-2003 General Software, Inc.
STPC-5.2-01DE-EB2E
BIOS revision: 1.1.9 (08/10/04)
Firmware revision: 10.1.94
Booting LabVIEW RT from drive...
Fat16
Jumping to 07E0:0000
Checksum: 011BCEEB
LabVIEW RT Boot Loader
(C) Copyright 2002-2003 National Instruments Corporation
STE10/100A Ethernet found.
Initializing network... done. IP address is 152.50.232.157
--------------------- NI-Serial v2.5.4 for LabVIEW RT ---------------------
COM1 - | Built-In Serial Interface
Welcome to LabVIEW Real-Time 7.1
NI-VISA Server started successfully.

Hi, Raltieri,
I noticed from the text that you sent that your cRIO controller has LabVIEW RT 7.1. Since you upgraded your host computer to LabVIEW 7.1.1, you will also need to upgrade the LabVIEW image on your controller to the same version. Try reinstalling the LabVIEW RT component into the cRIO controller (in MAX, under Remote Systems, under your cRIO >> Software), and just make sure that you select 7.1.1 as the version to reinstall. Most likely that is the problem.
Please let me know if that doesn't help.
GValdes
National Instruments

Is there a LabView library for MKS type 1258A controller mass flow ?

I have only found library for 647C and MKSMassFloViaRS-485 . Is it possible to work for the 1258A?
Thanks in advance

Hello SVP1,
Here are the MKS drivers we have:
ni.com: "mks" - 3rd Party Drivers
http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/ssnav:idr/q/mks/
I am sorry to say we do not have one for your device.
What you could do is contact the manufacturer to see if one of the drivers we do have also works with your device. Sometimes this happens with very similar devices, but is not supported by National Instruments.
Regards.
Ernesto

I am looking for Compact RIO system for PID control

Hi all,
I am looking for the CompactRIO system for PID control.
My system acquires two input data (0-10V) from two displacement sensors and sends one output signal (0-10V) to piezo-actuator at every step. And my target is the short settling time and the low overshoot.
I think that I need fast control system. So I am interested in CompactRIO. But I am not familiar with this sytem. Could you recommend the good control system for me?
The one important thing is that the time limiting step of my system is Piezo actuator (it's natural freq is 20kHz.) CompactRIO is much faster than the Piezo-actuator. I am not sure whether CompactRIO is good to my system or not.
Here is the CompactRIO system which I am interested in:
i) CompactRIO Reconfigurable Embedded System: cRIO-9004
ii) CompactRIO Reconfigurable Chassis: cRIO-9101
iii) I/O Module : AI : cRIO-9215 AO: cRIO-9263
Thank you so much,
Sungjin

Hello Sungjin,
CompactRIO should work great for your PID control system. Those I/O modules are the correct voltage range and the 1M gate FPGA backplane will be plenty for a single PID controller. You'll probably be able to get loop rates around 100kHz for analog PID control.
Keep in mind that the LabVIEW FPGA module includes PID examples that will cut down your development time considerably.
Regards,
Vineet

How to store data into a file from a host VI developed for Compact RIO

Hi,
I am new to the CompactRIo.I have developed a VI which runs on the FPGA(CompactRIO) which continuously monitors tha data from a system and i have developed a host VI to read the data and i am successfully getting the data into my computer and i want that data to store into a file.When i use the write to spreadsheet VI for writing into a file.The data is not written into file can anybody tell me why this is happening?

Hi,
The last one you said is working when i conected through it is working, whatever files i have used earlier are there.Thanks for that but i have few queries please answer me so that i acn proceed in my project.
1.As you said to connect to ftp://xx.xx.xx.xx i have seen some extra files along with my files waht are they? waether my data files are stored in flash memory of RT controller?if so, how to clear those files?
2.Suppose i want to clean up the flash memory of RT contrller i.e suppose i have deployed some file earlier , now i want to cleanup those i dumped into the memory how to do that?
3.How to disable the Application running on the RT controller when it powers on? i.e. when i switch on the power it should be connected but nothing hould be running on.
4.I mean at the end of the experiment when i stopped the host VI by pressing stop button weather application running on the RT controller will stop and weather FPGA VI runnibg on that also stop if not how to stop?
5.Suppose next time when i connect to ftp://xx.xx.xx.xx i dont want to keep earlier files there how to delete them?Because my doubt is if i am using the file name which is same as the prevoius one there is aproblem of appending the new data to the old file.?
Regards,
Vishnu

Referenced Parameters in C library not working on Compact RIO

High level
I want to use Google Protobuf on my Compact RIO. I have it 90% of the way there and running into issues.
Details
I'm a long time C++ developer who's newish to LabVIEW. I'm using C to create a cross-compiled library to use on a Compact RIO (9025) with LabVIEW code. I'm using Linux (Ubuntu 14.04.1) with a VxWorks toolchain and CMake to create the library. I copy it over manually (looking for a better solution to that here), call it from LabVIEW via a Call Library Function, and assuming I'm doing simple things it works great! Here's a quick sample of what I have that works:
My C code
extern "C" double addNums(double in1, double in2)
return in1 + in2;
extern "C" double multNums(double in1, double in2)
return in1 * in2;
Which I cross compile to a VxWorks binary and copy over to the cRIO.
Then on the LabVIEW side, I have this.
I run it on the target cRIO and all works great.
I mentioned protobuf. Cross compiling the full blown protobuf library for VxWorks proved to be a near (if not 100%) impossible task. So I found and am using Nanopb. I'm able to cross compile and get the following code using Nanopb to actually run on the cRIO and spit out the expected response:
extern "C" double testPbuf()
uint8_t buffer[128];
size_t message_length;
bool status;
std::ofstream file;
file.open("testOutput.bin", std::ios::out | std::ios::binary);
//! Create a message
ExampleMsg message;
message.value = 13;
pb_ostream_t stream = pb_ostream_from_buffer(buffer, sizeof(buffer));
status = pb_encode(&stream, ExampleMsg_fields, &message);
//! Decode the message
ExampleMsg message;
pb_istream_t stream = pb_istream_from_buffer(buffer, message_length);
status = pb_decode(&stream, ExampleMsg_fields, &message);
return message.value;
return 0;
Not terribly important, but if you know protobuf, here's the proto message I'm using
message ExampleMsg {
required int32 value = 1;
So then I call this function from LabVIEW very simply:
I run this and it works! I see my 13 as expected. Jump for joy, protobuf works on the Compact RIO! Ok no jumping yet...
Now what I want to do is get the C library to generate and output the actual serialized protobuf message because I need to send it over UDP from the Compact RIO. So here's my attempt so far:
extern "C" const void getPacket(uint8_t* packet)
uint8_t buffer[128];
uint16_t packetSize;
bool status;
ExampleMsg msg;
pb_ostream_t stream = pb_ostream_from_buffer(buffer, sizeof(buffer));
msg.value = 14;
status = pb_encode(&stream, ExampleMsg_fields, &msg);
packetSize = stream.bytes_written;
//! If something failed we should see an 'X' in the first byte
if (!status)
buffer[0] = 'X';
memcpy(packet, buffer, packetSize);
And on the LabVIEW side, I'm initializing an array of unsigned int 8s to the proper size and feeding it into the function, and reading the packet parameter as output.
When I run this I never get any output on packet except whatever I set the initializer to. I have also changed the code to try to output a string as a parameter argument, with this declaration:
extern "C" const void getPacket(char* packet)
And memcpy() appropriately and can't seem to get the output properly in LabVIEW using strings in place of the U8s. I need to figure out how to get this serialized protobuf data into LabVIEW so I can send it over UDP as a message.
I have seen several examples in the LabVIEW installation directory, but they're referring to objects and libraries which are meant for Windows DLLs and not easily used in a cross compiled environment. I also have seen many threads on here relating to this but none have helped so far. Any help would be greatly appreciated!

I would hate to do a file write to solve this as it would add a whole new lag to the system. I did end up with a solution, which is essentially what I posted above. It seems like the real issue I was having was that the dll was not being reloaded on subsequent rebuilds/tests. So I would make changes to the DLL to test and they wouldn't be reflected even when I copied the DLL to the Compact RIO. Turns out I have to completely close the project and re-open it if I change the dll file. This is really strange behaviour. I could even *delete* the DLL from the Compact RIO and the VI would still run with the previous "copy" somehow.
Anyhow it looks like I have protobuf working from the Compact RIO, though still have a few issues with encoding certain data types. If anyone is interested in the full solution I may do a write up.

Compact RIO and LabVIEW run time

Dear All,
Good Morning.
We are developing a new experimental setup which will have different components, such as mass spectrometer, pressure transducers, valves and thermocouples, RTDs. We are currently having LabVIEW 8.6 Run time. We would like to control different components and acquire data using CompactRIO. I am not clear if compact RIO works with 8.5 run time. In the developers guide NI, mention about the real-time LabVIEW.
Thank you very much for help,
Zach

You need the Real-Time Toolkit (and possibly the FPGA toolkit, depending on your needs) to work with the cRIO. The version of LabVIEW installed on the cRIO must match the version you're using for programming on the PC (so you can't have LabVIEW 8.5 on the cRIO and 8.6 on your computer). The LabVIEW Real-Time is not the same as the LabVIEW Run-Time engine. The Run-Time engine lets you run compiled applications on your computer. The Real-Time toolkit lets you program real-time targets such as the CompactRIO.

Reference Library for Converting Between LabVIEW and XML Data (GXML)

Please provide feedback, comments and questions on the Reference Library for Converting Between LabVIEW and XML Data (GXML) in this thread.
The latest version of the NI GXML Library is availble in VIPM on the NI LabVIEW Tools Network repository.

Francesco, Thank you for the feedback. With this component it was my intention to make a more "terse" version of the LabVIEW Flatten to XML VI that was also supported on RT and that gave the user more flexbility regarding the structure of the parsing type definition. I think you are right that the XML parser is not compliant to section 2.11 of the XML spec. The parser does specifically looking for a #D#A and this appears to be an oversight on my part. Please confirm for me, the specifcation is saying that the XML parser should be able to recognize three possibilities as an "end of line" character: #D#A, #D, or #A. Am I reading this right?There are more efficient (and in some cases much more efficient) ways of sharing data between LabVIEW and LabVIEW: some examples are flattened binary strings and the datalog binary format. XML is slower than these optons but the upside is that it is human readable. Furthermore XML is inherently hierarchical which is convenient for complex data structures like clusters of arrays of clusters, etc. If you don't care about human readability then you are correct XML doesn't make as much sense.I will return to the GXML source code and try to fix this in the near future but I would hope that instead of creating yet another custom VI from scratch that you could reuse what I have provided for you. I included enough documentation in the source code so that users could make some modificiations themselves. The target application for this reference library was LabVIEW to LabVIEW communication. As such I documented the schema on the dev zone document from a LabVIEW perspective. It includes all the supported datatypes and all the supported data structures (cluters, arrays, multidimensional arrays, clusters of multidimensional arrays, etc.) I do see some value in making a more conventional XML spec but the time investment required didn't really line up with my intended use case. Were there any other downsides to GXML that I have missed? Best Regards, Jeff TippsSystems Engineer - Sound and VibrationMessage Edited by Jeff T. on 04-21-2010 10:09 AM

I need HP4280 GPIB library for LabView 6i. Help.

Hi.
I am researching about reducing insulating material's capacitance with HP 4280.
Recently I got a GPIB card, but I have no idea about it.
I need help, so far I have read the manual and etc., but I understand nothing.
Our lab has a LabView program (6i), a friend of mine said "If you have a HP4280 library, you will use it without difficulty."
So I am posting this.
If someone has a library about HP 4280 for LabView 6i, please let me get it.
Thank you.
P.s. : The CD has library for many other machines but don't have for HP 4280, the nearest library was HP 4284.

I performed a quick search, but I could not find an exact driver for the HP 4280. There are some drivers on www.ni.com/idnet that are close and may work with your instrument. Just search for HP and meters. All drivers can be downloaded on our site for free.
In addition, HP seems to sell a driver that covers a range of instruments, including the 4280. Here's the link I found: http://eesof.tm.agilent.com/products/85190a_ordering.html. I would recommend contacting HP for more information.
Good luck with your application!

DI(cRIO-9411) automatically generate ture signal in compact RIO.

Hi all,
I have compact RIO system (9101, DI (9411), DO (9472), AI(9215), AO(9263))
My crio system is
DI is monitoring the input signal. When input signal is Ture, DI triggers AI and AO module.
I tested this system, but the input signal which DI recorded are always TURE signal (1)even if I gave F signal(0)to the input signal.
The more weird thing is when I turned the button(highlight execution)on, DI recorded F signal(0) when I gave F signal(0), but if I turned the button off, DI recorded T signal(T).
I guess that Real time system and DI input module generates the wrong signal.
Do you have any idea or any suggestion?
Thank you,

Hi Ricardo,
I am using Digital Input VI.
Actually, I connected the digital output port of DAQ card (6036E) to DI(cRIO-9411) of compact RIO. I used single-ended devices to CRIO-9411 because I used 5V signal of output of DAQ Card(digital output). So I connected the DI port of 6036E to DIa port of CRIO-9411 and digital ground of 6036E to common of CRIO-9411. I did not connect any signal to the DIb port of CRIO-9411, +5 Vout port, and external power supply.
In addition, I attached my files. (testtrigger2 -> FPGA, testtrigger2(RT)-> real-time)
More weird thing is
If I ran the only FPGA program in the FPGA, the DI recorded the signal properly.
But if I ran the real time program and FPGA program, the DI recorded TURE signal even if I gave False signal to port. I think that it seems that DI module (9411) is dead when I ran the real-time programs because crio-9411 does not response any signals properly (always TURE signal).
So I think that there is some problem of communication between Real-time system and FPGA system.
Do you have any idea about it?
Thank you,
Sungjin
Attachments:
testtrigger(RT)2.zip ‏62 KB

Looking for labview library

Like in the subject
regards
Kris

KZ;
You can find information about the National Instruments OCR library for LabVIEW here:
NI OCR Software
There are other OCR libraries for LabVIEW developed by third parties. I am aware of the following:
EconoCR for LabVIEW
Regards;
Enrique
www.vartortech.com

NI report and Compact RIO

I can't save my report in the path that I want. The VI is running in
the Compact RIO y this is the path that it shows c:\ni-rt\startup\.
What
I think is if the VI is running in the RIO, so it is triyin to save the
report in the RIO and I don't accept paths from my laptop.
How can I save the report in my computer??
Regards

You are absolutely right. The file I/O is happening on the cRIO since the application is running on the cRIO. You have two options over here. The first would be to save the data on the RIO and then transfer the file over to the host. The second, the recommended one, would be to transfer the data to the host where the data can be logged. There are seven network communication methods outlined by LabVIEW 2009 Real-Time Module Help: Exploring Remote Communication Methods (RT). There are also APIs based on the above methods that may simplify the transfer overhead. An example is the Simple Messaging Reference Library (STM). If you have any follow up questions, post back!
This might be helpful to you:
Best Practices for Target File IO with LabVIEW Real-Time
Message Edited by Adnan Z on 01-29-2010 07:29 AM
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Error 1335 When Installing Compact RIO Module Software 2.1.4 From Hard Drive

I’m having issues with the installation of the CompactRIO Module Software 2.1.4.
Initially, problems were occurring when trying to communicate with the device, as it was denying access to it from the Development PC. Various things were tried such as adding a ‘*’ to the fields and making sure 'Allow' was selected in the communication properties on LabView RT. This didn't seem to work. A post relating to our problem is here: http://forums.ni.com/ni/board/message?board.id=170&message.id=269809&query.id=18752#M269809
As none of this was working, we decided to format the disk on the Compact RIO and reinstall the software to it. The software downloaded from Ni.com was the CompactRIO Module Software version 2.1.4 (dated May 2007). This file was unzipped using WinZIP 9.0 (on a PC running Windows XP Pro SP2 5.1.2600) and then transferred with a USB stick to the Development PC.
We attempted to install the file on the Development PC (running Windows 2000 SP3 5.00.2195) by running setup.exe. This started normally, but then proceeded to come up with an error message saying: ‘Error 1335. The cabinet file ‘Cabs.w1.cab’ required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.’
Attached are screen shots of the error message that appears.
As a result of this error, the installation could not be continued and the module software was not installed.
What is going wrong with the installation and how can I go about sorting it out?
Thanks very much,
Moses
RT target cRIO-9012, NI-RIO 2.1.3, LV 8.2, RT 8.2, FPGA 8.2, host ip 150.150.10.15, cRIO IP 150.150.10.4
Message Edited by Mohoyt on 09-10-2007 04:03 AM
Attachments:
Error Message CRIO Module 2.1.4.JPG ‏36 KB

Way,
Thanks for the help overall, I finally worked it out. The problem was initially present in the unzipping of the original archive that had been downloaded from the NI.com website. When I had previously unzipped it, I had done so to a network drive which for some reason stopped autorun.inf and autorun.exe from functioning properly and so when I tried to install it on the Dev PC I got the aforementioned error. To overcome this problem I unzipped it to a local drive and (surprise!) there were no faults, so when installing the actual software, no errors appeared and it was installed correctly.
This however was not the only problem, the version that had now been installed did not want to co-operate with the RIO at all, and came up with various software errors in addition to not having all of the available software modules for the RIO available to install. The solution was then to install the newest RIO software, which is very badly labelled on the NI.com website by the way (its packaged as RIO software, so if you're looking explicitly for CRIO software you've got no chance of finding it). The newest version, 2.3 (Aug 07) as opposed to the 2.1.4 (May 07) that I was previously trying, worked fine and I was able to get all the software modules installed. So for now the problem is solved!
Thanks again for all the help.
Cheers,
Moses

Build real-time application with Compact RIO

Good afternoon,
I am currently trying to run a VI on compact RIO and would like to control it through remote front panel. I followed steps on this link http://digital.ni.com/public.nsf/allkb/AB6C6841486E84EA862576C8005A0C26 and successfully done everything with a simple example.
However when I moved on and did the same thing to a more complicated VI (my purpose is to make this VI work), everything was fine until I reboot the compact RIO. After a few seconds connection lost between the host computer and cRIO, and I had to shut it down and delete the startup file (with extension .rtexe).
I am not sure what happened since everthing works fine with simple VI but not the complicated one. It could because the second VI has many sub VIs as well as objective functions loaded in it, it could also because the VI takes too much memories of the CRIO and stop it from connecting to the host computer.
If anyone have any ideas of how to make it work please let me know.
Thanks very much
Carl

Hello zzzfreedom,
There are a number of potential issues I can see with the VI you're trying to deploy as a startup executable. How do you intend to interact with this VI? Are you running the front panel as a remote panel or connecting to the VI using debug tools? A few points:
- Your VI will run immediately when the RIO boots unless you're using debugging tools to prevent this from happening, keep that in mind. It looks like you've accounted for this and required an initialize or network trigger of some sort for some of your loops, but the AI loop will start quickly and appears that it may require user input.
- You have several "user prompt" style express VIs. These will not work (or will not work as expected) on a standalone RT target. There is usually no front panel to interact with!
- Like dialogs, event structures watching for user interaction probably aren't going to do what you want.
- You are writing quite a bit of data to the VI's front panel, and there is at least one chart indicator. Again, how will the user interact with this VI? It looks like you need a host VI that will run on a machine the user will interact with.
- You're using quite a few local variables. It looks like you've taken a lot of care to protect against race conditions, but this causes a lot of data copies and tends to be error prone.
- I've not analyzed all cases, but it looks like you have a number of places where the execution of a timed loop may be blocked under certain conditions. This will likely rail the CPU due to the much higher priority of the timed loops.
- What will happen if you lose connection with the server in your TCP command loop? it doesn't look like there is any way for the user to reconnect without restarting the RIO.
If you do intend to run this as a remotely accessible VI on your RT target, another point to note is that when running from the development environment, the front panel of your VI executes on the host machine. Once you deploy it as a remote front panel or debuggable RTEXE, everything is hosted on the RIO, and this has the potential to bog things down quickly.
Here are a few references I think you might find helpful:
LabVIEW Help: Real-Time Operating Systems - see considerations for Express VIs and Front Panel interaction
http://zone.ni.com/reference/en-XX/help/370622L-01/lvrtconcepts/rt_osnotes/
LabVIEW Help: Real-Time Module on VxWorks Targets - see unsupported features
http://zone.ni.com/reference/en-XX/help/370622L-01/lvrtconcepts/rt_vxworks/
NI LabVIEW for CompactRIO Developer's Guide -lots of good general information on architecting RT applications, network communication and hosts, etc. It looks like you're using the RIO Scan Engine, so the FPGA portion might not be relevant at this time.
http://www.ni.com/compactriodevguide/
Best Regards,
Tom L.

IMAQ FFT multiplication and MATLAB Script Nodes/Compact Rio

I would like to automatically generate a frequency kernel to multiply with the FFT of my IMAQ image. I was wondering if there was a way for LabVIEW to automatically set up 2D arrays (with a lower bound, a step size and a higher bound) like what is done in MATLAB.
I was wondering also, if someone could give me some insight as to what restrictions I face, when uploading code from MATLAB script nodes into the Compact RiO (I have a cRiO-9025).

Hi Bilaln,
I think you confused about a MATLAB script node and a Mathscript node.
A MATLAB script nodes uses ActiveX to call into MATLAB, where as a Mathscript node runs in a NI built environment. The MATLAB script node requires both that MATLAB be installed and the host supports ActiveX. Since cRIO does not do either, you should use the MATHSCRIPT RT module.
Joe Daily
National Instruments
Applications Engineer
may the G be with you ....

CANopen LabVIEW Library for Compact Rio (cRIO) + 985x ?

Similar Messages

Maybe you are looking for