TI USB-to-GPIO interface EVM adapter. Dll for Labview driver

I am looking for way to send commands via Texas Instrument USB-to-GPIO using Labview. TI support only .dll file. No .h or .c file. So when I configure "Call Library Function Node" then .DLL is not enough. All nodes are closed.
Solved!
Go to Solution.

You need to open (instantiate) the .Net object before you can attempt to do anything on it. As it is now you try to operate on a NULL object meaning there is nothing to perform your methods on. Look at the .Net Constructor node.
Message Edited by rolfk on 05-11-2010 05:10 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions
Attachments:
Net Constructor.PNG ‏20 KB

Similar Messages

  • Building Dll for labVIEW RT gives errors

    Hi All
    Does building dll for labVIEW RT using CVI require labview runtime engine to be installed?
    becuase i get some errors of unsatisfied referances to some library while building the dll with target selceted to "labVIEW real time only".
    Regards
    Arun

    Hello Arun,
    You don't need to have LabVIEW Run Time installed on your machine. Please check the link below to see the function that are supported by exporting the LabWindows/CVI LabVIEW RT Engine
    http://digital.ni.com/public.nsf/websearch/D3EFE7C6F073384886256FDD005FBCDA?OpenDocument
    Ame G.
    National Instruments

  • Call a dll for Labview: Function not found in library

    Hello,
    I am trying to call a very simple .dll form Labview. I compiled the .dll for x64 using Visual Studio 2010, because I am using Labview(64-bit). I did everything exactly the way I read it in several Tutorials. But the "Call Library Function Node" doesn't create a popup menu with the avalible functions like it is supposed to do. The Import Wizard doesn't find any functions neither. What is wrong with my .dll?
    I added a block marked 'extern "C" ' into my source file, but it still won't work.
    Thanks
    Matthias
    Solved!
    Go to Solution.
    Attachments:
    DynamicLibrary.zip ‏2452 KB

    You need to define an entry point to the DLL
    BOOL APIENTRY DllMain( HANDLE hModule,
                            DWORD  ul_reason_for_call,
                            LPVOID lpReserved )
        return TRUE;
    Also add extern "C" __declspec(dllexport) to your functions
    More details here: http://www.ni.com/white-paper/3056/en
    Beginner? Try LabVIEW Basics
    Sharing bits of code? Try Snippets or LAVA Code Capture Tool
    Have you tried Quick Drop?, Visit QD Community.

  • How to build a dll for labview pda, which uses the intel ipp primitives in it

    Hi all,
    For my application, I need to call a c dll from Labview PDA, and in the c function i need to use intel IPP function. When i call my dll, i get an error saying the ippfunction i use, say "ippsCopy_16s missing c or vi file". Can someone tell  me what I might be doing wrong?

    Hi Vani,
    When using a DLL in a PDA there are some special considerations you have to take. Please take a look at the following knowledgebase describing the process.
    Eli S.
    National Instruments
    Applications Engineer

  • How to create a DLL for LabVIEW in MatLab

    I want to use MatLab-Code from an M-file in LabView without MatLab. So i decide to use external code in a DLL. Can anybody give me some hints - how to do? (How to create, how to use?)
    Used System Windows 98, LabVIEW 6.1, MatLab 6.1 R12.1
    Thanks

    Hi,
    I use Matlab-Code in Labview and it's don't need create a dll. The LV was a tool, matlab script, you can write your code Matlab here. see the examples of LV.I think the lV 6.1 have.
    Dll it's very complicated

  • Receiving a COM event from a DLL in LabView

    We are access an inproc server windows DLL from LabView. The COM interface is derived from IDispatch and has many methods and 2 events. The methods work great but we can't see the events or create event queues. Do we need to move the DLL interface more towards ActiveX? What classes or methods does the COM interface have to support for LabView to handle COM events?

    I am working with a COM expert who has done this. I have interfaced to his
    DLL based server via LV Activex event vi's. Write back with your email
    address and I will see if I can connect you up with him.
    "Craig_2002" wrote in message
    news:[email protected]..
    > We are access an inproc server windows DLL from LabView. The COM
    > interface is derived from IDispatch and has many methods and 2 events.
    > The methods work great but we can't see the events or create event
    > queues. Do we need to move the DLL interface more towards ActiveX?
    > What classes or methods does the COM interface have to support for
    > LabView to handle COM events?

  • Calling 64-bit dll from labview 8.2 on Windows7

    Hello,
    I have tried the LABview driver from the OMNIDRIVER (OceanOptics) package. But when calling functions from the “OmniDriver32.dll” , LABView is crashing and  says that the memory is corrupted.
    I am using LABVIEW 8.2 (32-bit) running on Windows 7 (64-bit).  I have tried some LABView code examples given for LABview 7.1 and 8.0. These example are using the OmniDriver32.dll (not the OmniDriver64.dll).
    But maybe these example are assuming that you are on a 32-bit operating system, which is not my case.
    So I have tried calling the OmniDriver64.dll. but LABView seems not to recognised the dll and can’t read the included functions.
    Is there a way to call some 64-bit dll from LABview 8.2 ?
    Or do I need to buy a new license for LABVIEW 64-bit ?
    Thanks,
    Pierre

    There is no virtualization support for DLL bitness issues outside of the Windows standard directories. The Windows and System directories that an application "sees" depends on its bitness. All other directories are not mapped depending on the calling process' bitness.
    So if you have installed 32 Bit LabVIEW and are not calling one of the system DLLs, you have to point the path of the DLL to the real 32 bit DLL. Pointing it to a 64 bit DLL should not even be able to get the VI compilable, since Windows will refuse to load the DLL into the 32 bit process as being an unknown file format, and that should make the VI broken.
    If you need to call a system DLL you simply enter the DLL name without path and Windows will find the according DLL for LabVIEW.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Dll for sciencetech spectrometer 9050

    hello everybody
    I have a sciencetech spectrometer 9050, controled by the scispec sofware, and I like to controle it with labview. Please where can I find its dll for labview
    Thanks in advance
    yours

    fredj2015 wrote:
    hello everybody
    I have a sciencetech spectrometer 9050, controled by the scispec sofware, and I like to controle it with labview. Please where can I find its dll for labview
    Thanks in advance
    yours
    From the manufacturer. Where else?

  • Will a USB 3.0 to FireWire adapter make my transfer rates faster?

    I have a MBP 2010 15 inch that only has a measly UB 2.0 and a (less measly) FireWire port. I have an external sea gate 3tb backup plus desktop hard drive that had a USB 3.0 cable. However, as stated earlier, my MBP only has a USB 2.0 port. But it seems the FireWire port might have better transfer rates. If I used a USB 3.0 to FireWire would it have greater transfer speeds, and by how much? If there is an even better way to connect my hard drive to my aforementioned MBP, please tell me. And if anybody has a good adapter recommendation, please tell me.

    There is no such thing as a USB-FireWire adapter/converter.  USB and FireWire are electrically and protocol incompatible.
    Seagate does make an accessory unit called the STAE 123 that works with the following drives to provide a FW800 interface:
    Backup Plus Desktop Drive for Mac V1
    Backup Plus Desktop Drive V1
    GoFlex Desk for Mac drive with Thunderbolt
    If your drive is one of those models, the STAE123 may be the answer to your needs.

  • USB or Firewire to MIDI adapter

    I just bought an IMac and am looking for a USB or Firewire to MIDI adapter, couldn't find one in the Apple Store. COuld anyone recommend one? If they make them with multipe MIDI inputs that would be great.
    Thanks

    I just bought an IMac and am looking for a USB or
    Firewire to MIDI adapter, couldn't find one in the
    Apple Store. COuld anyone recommend one? If they make
    them with multipe MIDI inputs that would be great.
    Hi, Sashasdad. Lots of great adapters out there; which one is best for you depends on your circumstances.
    First suggestion: I would suggest going with one that has enough ins/outs plus one or two spares. If you get more gear, you can always add on another MIDI interface and your Mac shouldn't have any trouble handling it.
    Second suggestion: don't even look for a Firewire MIDI interface. You'll find audio interfaces with some MIDI ports that run on Firewire, but for straight MIDI data a USB port is going to handle a ton of I/O before it even thinks about breaking a sweat. (MIDI runs at 32 KILObits per second, while even pokey old USB 1.0 theoretically runs at 10 MEGAbits per second.)
    I've used the M-Audio MIDISport interfaces (2 in; 2 out) as well as "micro lite" from Mark of The Unicorn (MoTU). Both are absolutely easy to install and use. One small benefit of the MIDISport series is that there's a switch that allows you to use the device as a 'thru' box even if the computer isn't running or processing MIDI -- this is useful when you have a controller addressing one or two modules and you don't want to turn on your computer just to play around. The MoTU Ultra Lite is a 5*5 device, and it's served perfectly well for a few years now. Because my configuration has changed, I don't miss the 'thru' feature of the MIDISport interfaces.
    I would suggest checking online prices at M-Audio, Sweetwater Sound, and Musician's Friend -- then go to your local shop and expect a decent markup.
    Cheers,
    Michael
    WARNING: OLD FOGEY ALERT!!: Just to show my age here, I sorely miss the Opcode Studio-4 that I used to have: 8*8, with tons of patching and processing available in the box. Couple that with a Roland A-880 MIDI patchbay (also 8*8) and you've got oodles of power. Then there was the funny little Akai ME-25S and the wildly potent Yamaha MEP-4. Yummy, yummy, yummy.
    Back in the early 90s, I spent a huge amount of time with UltraMIDI and TweakIt on the wonderful Atari ST, at one point designing a pretty nifty two-player, four-controller, eight-module setup for a recital at Berklee.
    For what it's worth, you can do a whole lot more with much less money using today's gear (put Cycling 74's Max onto a cheap laptop and !!!!!), but there was a certain beautiful adventurousness to those weird old devices. The MEP-4 was particularly nifty. Mine is probably still working in my brother's home studio years away and far ago. And UltraMIDI was a variant on Max -- anything could be mapped to anything else!
    eMac 800mHz, MacBook 2gHz   Mac OS X (10.4.7)  

  • Using USB 2.0 Network Ethernet Adapter for sharing printer with 3 computers

    Hi all,
    Opposed to using a print server, can I use a USB 2.0 Network Ethernet Adapter to connect my Epson printer over my ethernet DSL router?
    Thanks
    Web dude

    Yea, I thought about an adapter for the USB 2.0 port, but for a few bucks more, get the USB 3.0 adapter and be able to connect to Ethernet at Gigabit speeds!
    Since Lenovo has not commented on the absence of an Ethernet port, I'm guessing that the slim height of the Yoga prevents it, unless you go to some funky slide-out module and connect at a 90 degree angle (which would be a worse design).  I had an old Thinkpad (or Dell?) with that design, and they are intermittent and subject to being broken off.
    Bundling in the Ethernet Adapter would have been a nice touch.  Perhaps they were trying not to increase the Yoga's "above market" price further.

  • How to add iPhone USB to Network Interface on iMac? Please help.

    Hi,
    I've been trying to find a solution of the past few days to no avail. I've accidentaly deleted iPhone USB from network interface (by pressing minus sign) and now my iMac won't see it. I wanted to tether via USB, but it was red before, and then I deleted it at all iTunes sees it and syncing is working, but I can't tether now. I've got iTunes 11.1.2 and newest iOS for iPhone 5S.
    Thank you in advance!

    Anyone?

  • Using code interface node with dll crashes LV 2011 but not LV 8.6... using max error handling does nothing

    Hi all,
    I'm having a peculiar problem.
    I inherited a project saved in LabVIEW 8.6. The project must use of particular dll that was built a few years ago. The original developer and source code for this .dll are long gone. The very core logic exists, in the form of embedded C code, and that's it. The .dll is called through a Code Interface Node in LV 8.6 and this setup manages to "work". Howver, running the VI that calls this .dll in LV 2011 causes an "insta crash", as in, no "program has stopped responding".  Error message pops up, then all LV windows close.
    It's very similar to that described in here:
    http://digital.ni.com/public.nsf/allkb/D84C9775ABD921CF8625772A005CA50C
    but this KB says to try putting the amount of error handling to maximum. I tried that, but it didn't help. 
    Using the "Debug" option allows me to run the just-in-time debugger with CVI 2010, which then proceeds to say this:
    Finally, I manage to get this out of it: 
    FATAL RUN-TIME ERROR:   Unknown source position, thread id 0x000012D4:   A non-debuggable thread caused a 'General Protection' fault at address 0x00000000.
    I don't think that really helps at all, but it's there.
    Here is the function prototype of the .dll:
    void  _inputPM@224(uint8_t arg1, uint16_t arg2, uint8_t arg3, float arg4, float arg5, float arg6, float arg7, float arg8, float arg9, float arg10, float arg11, float arg12, float arg13, float arg14, float arg15, float arg16, float arg17, uint16_t arg18, uint16_t arg19, uint16_t arg20, uint16_t arg21, uint16_t arg22, uint16_t arg23, uint16_t arg24, uint16_t arg25, uint16_t arg26, float arg27, float arg28, float arg29, float arg30, float arg31, float arg32, float arg33, float arg34, float arg35, float arg36, float arg37, float arg38, float arg39, float arg40, float arg41, float arg42, float arg43, float arg44, float arg45, float arg46, float arg47, uint16_t arg48, uint16_t arg49, uint16_t arg50, uint16_t arg51, uint16_t arg52, float arg53, float arg54, float arg55, float arg56);
    (never seen a function take 50 input params like that (wouldn't you use a struct? array? something? But I digress, and I don't know anything about .dlls...))  
    I do have a ".lib" and a ".cdb" file with the same name as the .dll, but those also looks like some kind of compiled file. 
    I'm sure the answer I'm going to get is that there is no way of telling what's really going on without .dll source code. I'm hoping against hope that there may be another way or hack.
    Any ideas? Thank you for you help. 
    Regards,
    Mark G 
    Solved!
    Go to Solution.

    MarkCG wrote:
    Changing the call library node to stdcall (WINAPI) did the trick! No more crash. Thank you very much!
    I haven't run LV2011 on windows XP, only on windows 7, so I don't know if that makes a dfference. But  The call type makes no difference when using LV 8.6 on the same machine, however.
    Now I've got to make the .DLL run corretly on a compact fieldpoint....  and avoid crashing IT. 
    Thank you for the help all!
    Well, the DLL did work fine in LabVIEW 8.6 because earlier versions of LabVIEW automatically proceeded to change the calling convention to stdcall, if they noticed a function name decoration of @# (# = number of bytes passed on the stack) appended to the name. This is the default naming decoration for stdcall functions used by VisualC. However this decoration can be overwritten with linker switches, other compilers don't use them always in the same way, and most likely there are in the mean time compilers out there that can produce such decorations also for non stdcall calling convention. So this automagic trickery was removed from newer LabVIEW versions.
    I do think it could be considered a bug in the code that upgrades LabVIEW VIs, that it uses the calling convention that is configuerd in the dialog, instead of the calling convention earlier LabVIEW versions used automagically, but it is an esoteric corner case.
    What Compact Fieldpoint controller do you have? If it's anything newer than 20xx or 21xx forget it. The 22xx controllers use a PPC CPU and VxWorks operating system and can never get a Windows DLL to operate properly. If it is a 20xx controller it's still highly likely that DLL can not even get loaded into LabVIEW as it likely relies on other runtime libraries and possibly Win32 APIs not present in the Pharlap ETS runtime kernel used on those controllers.
    There is a tool to check a DLL for incompatible imports that are not present on specific ETS RT systems. And this list summarizes the RT system used on the various NI controllers.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Battery charging by usb port on PC and adapter which is better

    Please help me
    Battery charging by usb port on PC and adapter (enclosed with IPHONE box )which is better?
    Regards

    Adapter is probably quicker as you have slightly better power than from a USB socket

  • Does a usb cab to 60 Watt L-Tip Power Adapter charger for Apple MacBook Pro Laptop Charger exist

    does a usb cable
    does a Usb cable to60 Watt L-Tip Power Adapter charger for Apple MacBook Pro Laptop Charger exist? i have an external battery pack i would like to use to charge my iphone and macbook pro.

    Not that I am aware of.  An Internet search on your part will be required.  If you should find something to that effect, note it will not be endorsed by Apple and the magnetic connector will probably be in violation of Apple patents.
    Ciao.

Maybe you are looking for