Jump to content

mattdl68

Members
  • Posts

    28
  • Joined

  • Last visited

Posts posted by mattdl68

  1. Hi. I am displaying an image from a camera with a frame grabber. The image is displayed in a .NET picture box.

    The frame grabber does not have the capability to zoom in on the image. I want to use a property node of the .NET picture box to manipulate the image.

    You help would be greatly appreciated.

    Thanks,

    Matt

  2. QUOTE (salvai.m @ Jan 9 2008, 03:57 AM)

    Hi,

    I have a problem with my app.exe build.

    I attach a simple code; the Vi open and close a TDM file.

    If I run this Vi in Labview works fine.

    If I build the application.exe on a notebook and I run it I got "Application crash with error ntdll.dll 00018fea".

    I've tried to build the Vi on another Pc Desktop with Labview and here if I run the exe it works fine.

    On the two PC I have LV8.5; the build options are the same.

    On the notebook I've try also to reinstall LV8.5 but I got the same error.

    Can you help me?

    Thanks a lot

    I know this threads a year old.

    I had the same issue.

    When the exe loads a data file it shuts down. (See attached error)

    The exe works fine on other computers.

    I think the ntdll.dll is corrupted, and i don't want to reinstall windows.

    Thanks

  3. QUOTE (rolfk @ Jan 9 2009, 01:56 AM)

    This is in the installed online help of LabVIEW for quite some time at least since 8.0 although with some small modifications in each version to adapt to changes and new features of the Call Library Node configuration.

    LabVIEW Help Menu->Search the LabVIEW Help: Index Tab: enter call library

    This will eventually get you to a topic under: Fundamentals->Calling Code Written in Text Based Languages->Concepts->Calling Shared Libraries (DLLs)

    It is about the meaning of the options in the configuration of the Call Library Node. But it won't help you with your previous question, how to find out in which order and with what parameters to call a particular API. Of course it is actually about calling an API that is typically written in C and the whole shared library concept is based on C too, so understanding at least the basic principles of C datatypes and their handling is really a prerequisite to be able to even understand what all those options and things mean.

    But that is not LabVIEW's fault, other than that it does not require you to know much about those things for programming some simple LabVIEW only VIs. For complexer programming it is even in LabVIEW more or less doomed, if you do not have some good basic programming knowledge, although the more C specific things you don't really need to know unless you want to venture into the Call Library Node or God forbid the Code Interface Node.

    Rolf Kalbermatter

    Hi all jlk posted 62628 post a vi HID_Get_GUID.vi see Post #15.

    I did a little digging into the result .

    I used the guide from the HID get Guid to setup the SetupDiGetClassDevs with no luck see attached.

    Thanks

  4. QUOTE (rolfk @ Jan 8 2009, 02:52 AM)

    No I think you are right. Except the person knowing 20% does not know that percentage :rolleyes: . That person likely thinks to know almost anything he or she would need to do the task only to find out later that there was about 4 to 5 times as much to learn before they could actually succeed. The problem is that some people get discouraged half way through it and then abandon the idea. I have some of those projects too.

    Another quite common thing is that the last 10% of the work require 90% of the time. That is where most people stop.

    Rolf Kalbermatter

    Of course! And except from examples in the SDKs (and DDKs) and sometimes from Open Source projects you can investigate how certain things are done, that is where the creative art of programming starts. With trial and error, combinatorial logic, experience with certain types of APIs (if you have programmed WINAPI application, writing a MacOS X application can seem a really unlogical way of doing things and vice versa) and some sort of magic (I have often tinkered one or more days about how to get something to work, only to wake up one morning and having suddenly an idea that turned out to be the start of a solution), you go step by step about programming something.

    Programming in LabVIEW itself is not that much different but its on a much higher and more abstract level than tinkering with system APIs. And there is really no magic LabVIEW could employ to make working on system API level as easy as working on LabVIEW diagram level besides of having people like the NI elves and other third party developers write impressive intermediate level software such as DAQmx to make the work for the LabVIEW programmer more bearable. It's about the way your brain cells work and have been trained.

    On the same level, I've seen several brilliant system programmers cringe and falter at an attempt to produce a more than trivial LabVIEW application.

    Rolf Kalbermatter

    http://zone.ni.com/reference/en-XX/help/37...g_the_clf_node/

    I think this will help,But its for 8.6

  5. QUOTE (normandinf @ Jan 6 2009, 08:59 AM)

    http://forums.ni.com/ni/board/message?boar...ding&page=1

    Thanks rolfk the link above will give you some history to my nightmare.......lol. What is confusing to me,is how to find the order of the dll's and functions to get what I need.

    There has to be some documentation out there that would give you some idea of the order in which to call functions.........one would think....lol

    I would think when trying to find USB devices using C++ they would need the order as well.

  6. QUOTE (normandinf @ Jan 6 2009, 08:59 AM)

    http://forums.ni.com/ni/board/message?boar...ding&page=1

    Thanks rolfk the link above will give you some history to my nightmare.......lol. What is confusing to me,is how to find the order of the dll's and functions to get what I need.

    There has to be some documentation out there that would give you some idea of the order in which to call functions.........one would think....lol

    I would think when trying to find USB devices using C++ they would need the order as well.

  7. QUOTE (normandinf @ Jan 6 2009, 08:59 AM)

    http://forums.ni.com/ni/board/message?boar...ding&page=1

    Thanks rolfk the link above will give you some history to my nightmare.......lol. What is confusing to me,is how to find the order of the dll's and functions to get what I need.

    There has to be some documentation out there that would give you some idea of the order in which to call functions.........one would think....lol

    I would think when trying to find USB devices using C++ they would need the order as well.

  8. QUOTE (normandinf @ Jan 6 2009, 08:59 AM)

    http://forums.ni.com/ni/board/message?boar...ding&page=1

    Thanks rolfk the link above will give you some history to my nightmare.......lol. What is confusing to me,is how to find the order of the dll's and functions to get what I need.

    There has to be some documentation out there that would give you some idea of the order in which to call functions.........one would think....lol

    I would think when trying to find USB devices using C++ they would need the order as well.

  9. QUOTE (normandinf @ Jan 6 2009, 08:59 AM)

    http://forums.ni.com/ni/board/message?boar...ding&page=1

    Thanks rolfk the link above will give you some history to my nightmare.......lol. What is confusing to me,is how to find the order of the dll's and functions to get what I need.

    There has to be some documentation out there that would give you some idea of the order in which to call functions.........one would think....lol

    I would think when trying to find USB devices using C++ they would need the order as well.

  10. QUOTE (normandinf @ Jan 6 2009, 08:59 AM)

    http://forums.ni.com/ni/board/message?boar...ding&page=1

    Thanks rolfk the link above will give you some history to my nightmare.......lol. What is confusing to me,is how to find the order of the dll's and functions to get what I need.

    There has to be some documentation out there that would give you some idea of the order in which to call functions.........one would think....lol

    I would think when trying to find USB devices using C++ they would need the order as well.

  11. QUOTE (normandinf @ Jan 6 2009, 08:59 AM)

    http://forums.ni.com/ni/board/message?boar...ding&page=1

    Thanks rolfk the link above will give you some history to my nightmare.......lol. What is confusing to me,is how to find the order of the dll's and functions to get what I need.

    There has to be some documentation out there that would give you some idea of the order in which to call functions.........one would think....lol

    I would think when trying to find USB devices using C++ they would need the order as well.

  12. QUOTE (normandinf @ Jan 6 2009, 08:59 AM)

    http://forums.ni.com/ni/board/message?boar...ding&page=1

    Thanks rolfk the link above will give you some history to my nightmare.......lol. What is confusing to me,is how to find the order of the dll's and functions to get what I need.

    There has to be some documentation out there that would give you some idea of the order in which to call functions.........one would think....lol

    I would think when trying to find USB devices using C++ they would need the order as well.

  13. QUOTE (normandinf @ Jan 6 2009, 08:59 AM)

    http://forums.ni.com/ni/board/message?boar...ding&page=1

    Thanks rolfk the link above will give you some history to my nightmare.......lol. What is confusing to me,is how to find the order of the dll's and functions to get what I need.

    There has to be some documentation out there that would give you some idea of the order in which to call functions.........one would think....lol

    I would think when trying to find USB devices using C++ they would need the order as well.

  14. Thank norman. I configured the SetupDiGetClassDevsA as shown in your replay.

    I guest the next step is calling function SetupDiEnumDeviceInterfaces. I think I understand this, but comments would be appriciated.

    [/quote

    I attached a vi. not my final version. needs comments and i will use a state machine.

    I"m not getting imformation of devices on my system. Can some take a look and see what i'm doing wrong.

    Thanks

  15. QUOTE (Irene_he @ Jan 3 2009, 12:20 AM)

    Hello matdl68,

    Not all parameters in C/C++ is easy or visibly callable within LabVIEW, it maybe easy in LabWindow, since it is C. It would be easier if you write a C wrapper function around it, so that it only uses very basic parameter type, like int, string, cluster, array etc. The functions mentioned above still only return the handle (which is an integer) that you need to pass into another function to get device information... I would suggest just write wrapper function in C and return the final information of the device to LabVIEW as cluster. Let me know if you need help.

    Irene

    Hi Irene. Thanks for the info.

    I looked into doing a wrapper. But i don't Know c that well. I was trying also to use the VISA develoment wizzard. The wizzrd had errors trying to setup the setapi.dll.

    Correct me if i"m wrong, even using c++ you need to know thr order in which to call the functions. For example...say i want to find all devices currently connected to the USB?What is the order of doing that? i'm assuming there are some outputs of some functions that feed the inputs of other funtions.

    Is ther some documation for this?

    the SetupDiGetClassDevs asked for a flag, Dword. DIGCF_ALLCLASSES is one of the fags. Is this a string?

    The flag ClassGuid is it a key which looks in the Ini file supplied by manufactuer. To get the device id (number)

    but seeing for know I what all devices connected. This should be set to null. So would I input a string constat(null) or a 0(U32)

    Thanks for your help

  16. Hi all...HAPPY NEW YEAR.

    I've been having alot of problems with calling SDK funtions. Is there any resources that clarifies the funtion parameters and how to configure them in labview.

    found this link These are the some of the dll's I need to call.

    One of the things I'm tring to do is find USB devices. The first thing I need to do;

    -call the SetupDiGetClassDevs which is in the setupapi,dll. see link

    SetupDiGetClassDevs returns a handle to a device information set that contains all installed devices that matched the supplied parameters.

    Depending what I set for parameters i can get imformation on all devices connected to all ports.

    My problem is don't know how the parameters are configured.

    HDEVINFO

    SetupDiGetClassDevs(

    IN LPGUID ClassGuid, OPTIONAL (how do I configure each of the parmteters in labview)

    IN PCTSTR Enumerator, OPTIONAL

    IN HWND hwndParent, OPTIONAL

    IN DWORD Flags

    );

    There are more call I need to make ,but need to get this imformation first.

    Thanks

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.