Dr. Dmitrij Volkov Posted December 29, 2007 Report Share Posted December 29, 2007 I plan to develope embedded software for real-time system using LabVIEW (OS VxWorks). Previous system was developed using C++. For Windows platform I could use dll libraries with old code. What is preferable way to reuse existing C++ code under VxWorks? As I understand dll libraries aren't supported with VxWorks Thanks in advance. Happy New 2008 Year Quote Link to comment
Rolf Kalbermatter Posted December 29, 2007 Report Share Posted December 29, 2007 QUOTE(Dr. Dmitrij Volkov @ Dec 28 2007, 09:07 AM) I plan to develope embedded software for real-time system using LabVIEW (OS VxWorks).Previous system was developed using C++. For Windows platform I could use dll libraries with old code. What is preferable way to reuse existing C++ code under VxWorks? As I understand dll libraries aren't supported with VxWorks Thanks in advance. Happy New 2008 Year The equivalent of DLLs in VxWorks are .out files. They are basically shared libraries created with either the VxWorks development system or the free GCC compiler. I've only created one of them so far using the freely downloadable GCC version for VxWorks to create a shared library for NI's newer real time controllers. But I'm not sure what you are trying to do here. LabVIEW for VxWorks is only available for the NI realtime target systems. For your own VxWorks based systems you would have to go the LabVIEW Embedded route. Not very cheap but maybe you are doing that already. Rolf Kalbermatter Quote Link to comment
psi Posted December 29, 2007 Report Share Posted December 29, 2007 QUOTE(Dr. Dmitrij Volkov @ Dec 28 2007, 04:07 PM) I plan to develope embedded software for real-time system using LabVIEW (OS VxWorks).Previous system was developed using C++. For Windows platform I could use dll libraries with old code. What is preferable way to reuse existing C++ code under VxWorks? As I understand dll libraries aren't supported with VxWorks I think, that it is better to you to use LabVIEW Real-Time Module instead of Embedded. Operational system ETS supports Windows dll. Look http://labview.ilc.edu.ru/forum/showthread.php?t=434' target="_blank">here In more details Quote Link to comment
Rolf Kalbermatter Posted December 30, 2007 Report Share Posted December 30, 2007 QUOTE(psi @ Dec 28 2007, 05:51 PM) I think, that it is better to you to use LabVIEW Real-Time Module instead of Embedded. Operational system ETS supports Windows dll. Look http://labview.ilc.edu.ru/forum/showthread.php?t=434' target="_blank">here In more details But LabVIEW realtime only supports NI hardware targets (some of them use Pharlap OS and other newer ones with PPC CPU use VxWorks) and somewhat specific x86 hardware with Pharlap (ETS). If the OP wants to use NI hardware targets or can live with a more or less standard PC hardware platform then LabVIEW realtime of course would be best. Rolf Kalbermatter Quote Link to comment
psi Posted December 30, 2007 Report Share Posted December 30, 2007 QUOTE(rolfk @ Dec 29 2007, 11:52 AM) But LabVIEW realtime only supports NI hardware targets (some of them use Pharlap OS and other newer ones with PPC CPU use VxWorks) and somewhat specific x86 hardware with Pharlap (ETS). If the OP wants to use NI hardware targets or can live with a more or less standard PC hardware platform then LabVIEW realtime of course would be best. Desktop PC as LabVIEW Real-Time Target is interesting and not expensive solution using OS ETS. Converting a Desktop PC to a LabVIEW Real-Time Target Requirements for a Desktop PC as a Real-Time Target LabVIEW Real-Time supports not only NI hardware device. LabVIEW Real-Time can supports Third Party Device. Can I Use a Third-Party Device with LabVIEW Real-Time (RT)? Third-Party Compatibilit Configuring the NI Real-Time Environment and NI-VISA toRecognize a Third Party Device Porting a Windows Device Driver to the NI Real-Time Platform Quote Link to comment
Rolf Kalbermatter Posted December 31, 2007 Report Share Posted December 31, 2007 QUOTE(psi @ Dec 29 2007, 05:47 PM) Desktop PC as LabVIEW Real-Time Target is interesting and not expensive solution using OS ETS.Converting a Desktop PC to a LabVIEW Real-Time Target Requirements for a Desktop PC as a Real-Time Target Hmm, you will have to buy a runtime license per system, and that is about 500 Euro in single quantities. Interesting yes, not expensive only if you are not planning to make an embedded device, although I'm sure you can negotiate volume license prices. QUOTE LabVIEW Real-Time supports not only NI hardware device. LabVIEW Real-Time can supports Third Party Device. Can I Use a Third-Party Device with LabVIEW Real-Time (RT)? Third-Party Compatibilit Configuring the NI Real-Time Environment and NI-VISA toRecognize a Third Party Device Porting a Windows Device Driver to the NI Real-Time Platform Yes for desktop PCs but not for arbitrary embedded development systems. For some reasons I was assuming that embedded was the route the OP wanted to go. Rolf Kalbermatter Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.