Jump to content

Ton Plomp

Members
  • Posts

    1,991
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by Ton Plomp

  1. QUOTE(crelf @ Feb 2 2008, 09:00 PM) Maybe (or am I?, at least the post count goes up) I thought you wanted to sort your RSS feed info from LAVA in forum folder like style. My RSS reader (Newsfox as mentioned), shows folders under the RSS-feed for ThinkinginG displaying the tags Jim has used. Can you tell me what your reader (thunderbird?) does with the ThinkinG RSS (http://thinkinging.com/feed/)? Ton
  2. QUOTE(crelf @ Feb 1 2008, 03:28 PM) Now while we are thread hi-jacking, do you mean something like this? QUOTE One great feature is exposed by Thinkinging and expressionflow: Where the RSS feed is divided into folders, it would be nice if the LAVA feed can be divided into seperate forums or seperate threads I don't know if IP board provides this but it would be nice! Ton
  3. QUOTE(tiasonpenthe @ Feb 1 2008, 08:56 AM) In MAX (Measurement and Automation Explorer) you can browse your GPIB bus, it will most likely return all devices on the bus with their address. QUOTE - I have downloaded the instrument drivers for the 3458A. But when I connect it via GPIB to the computer and from the DAQ Assistant I choose acquire signals>voltage it says "no supported devices found" The GPIB devices won't show up in DAQ assistant, you will need the device drivers and their LabVIEW VIs. If you can't find them you should be able to contact Agilent they will most likely have drivers. Ton
  4. QUOTE(PatNN @ Feb 1 2008, 03:28 AM) Well that is why you put stuff in one VI, to do unit tests and stuff. Ton
  5. QUOTE(Harvey @ Jan 31 2008, 10:20 AM) The default computer timeformat is '%c', to get the local decimal sign use '%;', but you should be aware that a user on a SQL server can have different settings. So it is quite a challenge to build a data parser that gets all the correct info. Ton
  6. QUOTE(Michael_Aivaliotis @ Oct 15 2007, 08:04 PM) A pop-up, or a logfile Ton
  7. QUOTE(linux120 @ Jan 30 2008, 08:51 AM) Your code will never work, close the references when your done. Look up in the Excel VBA help what you should do. Now you are changing a range not the contents of that range. Ton My tip: Get the NI report generation Toolkit.
  8. QUOTE(Aristos Queue @ Jan 29 2008, 06:33 PM) QUOTE(mrak1 @ Jan 29 2008, 10:34 PM) I am not sure if the question here is whether or not user events can be handled by multiple event structures executing in parallel. If this is the question, then I believe that the answer is that it can be done even if one of the event structures is being held up. I have attached an example that I believe demonstrates this. AQ is wrong (sorry), the code from Mike shows that the top loop is considerably slower. If you add the 'Exit Button\Change Event' to stop the loop you will understand why you need to finish an event handler fast. Ton
  9. QUOTE(Norm Kirchner @ Jan 30 2008, 12:36 AM) Norm, what do you mean? I simply don't understand your problem. Ton
  10. QUOTE(gustav @ Jan 28 2008, 04:48 PM) One question, does test2.vi run in the executable or outside it (from the development environment)? executable: What you could do is add a static VI reference to test1.vi in test2.vi, then you should be able to set properties. Debug this well, so popup a screen when some action succeeded or failed. outside: Use a 'open Application' node to open a reference to the app (use a specific port which is specified in the build specs), then open a reference inside the VI, by only using the filename as a string, debug this in the same way (should be easier since you are in the Development environment. Make sure you allowed the application to export this VI via VI server. Ton
  11. QUOTE(ceties @ Jan 28 2008, 04:53 PM) In the 'Exec state change' you should set the 'State Changed?' boolean in the 'Action' cluster to true: For more info see the XControl wiki. Ton
  12. QUOTE(Justin Goeres @ Jan 26 2008, 06:47 PM) Mmmm, is that new, the returning of the 'user event ref'? I never noticed it. :thumbup: Ton
  13. QUOTE(Dirk J. @ Jan 26 2008, 05:20 AM) Hi Dirk, a user event constist basically of two parts: The user event itself, which functions just like a normal event (window close, key down etc.) The user event registration, which subscribes an event structure to that event. It is possible, just like a normal (dynamic) event, to have multiple event structures subscribe to the same user event, so they all get notified of the event. I have to look at the code of jzafekas because it sounds interesting. EDIT: jazefekas, your case 'Event check, missed any?' is wrong every event structer should have a http://forums.ni.com/ni/board/message?board.id=170&view=by_date_ascending&message.id=247057#M247057' target="_blank">seperate dynamic event registration refnum. Ton So little time :thumbdown: Ton
  14. QUOTE(JoeLabview @ Jan 22 2008, 07:42 PM) The second part should be done with an ActiveX callback, I have implemented such for the NI report generation toolkit, to warn the user NOT to close the workbook, from there you could send user event. Ton
  15. QUOTE(zappa2 @ Jan 23 2008, 10:23 AM) [plug] You could have used the Boolean XControl [/plug] QUOTE When pressing one, the other enabled button should turn off. How to do this? Normally you should use radio buttons I guess, but my buttons have a special design. You can change every button of a radio button (right click on border, select advanced, customize) Ton
  16. QUOTE(silmaril @ Jan 19 2008, 03:34 PM) You should do that manually! So for every element create an additional property. If you want to you can alter my http://forums.lavag.org/downloads-file74.html' target="_blank">XControl Inheritance editor to do that for you. Ton
  17. QUOTE(silmaril @ Jan 19 2008, 03:34 PM) You should do that manually! So for every element create an additional property. If you want to you can alter my http://forums.lavag.org/downloads-file74.html' target="_blank">XControl Inheritance editor to do that for you. Ton
  18. Have a look at the Code Capture Tool. More info is in the wiki Code_Capture_Tool This provides a User Tool in the 'Tools' menu and an API for programmatic access. Ton
  19. QUOTE(Louis Manfredi @ Jan 16 2008, 10:32 PM) A feature? Are you sure about that, there's a feature that allows LabVIEW to crash on a 8.2 VI? What's special about that VI? And the change from constant to hidden control should have happened in 8.2, if it happened in 8.5 the VI would have been prior to 8.0, I don't think the 'constant case' check is applied on a 8.x VI. Could you read the VI version (with the http://zone.ni.com/reference/en-XX/help/371361B-01/lvprop/app_get_vi_version/' target="_blank">app.Get VI Version method)? If you get the message on an 8.2 VI something strange is going on (IMHO). Ton
  20. QUOTE(Tomi Maila @ Jan 16 2008, 07:54 PM) Value signalling. If you sent a property 'Value(Sgnl)' the event will always be triggered. Ton
  21. Now I only have to remember that I don't have to scroll down :headbang: Ton (pavlov)
  22. QUOTE(Tomi Maila @ Jan 16 2008, 07:48 PM) Well first you should make sure it is possible to open an app reference from two computers to the same app (port) on a third computer, I doubt it. The A-app can read the from the B.app.instance the port it is listening to, and by loading a VI into B memory that reas the current IP address (ipconfig?) it should be able to sent those info to C. Most likely you have to take your resort to an UDP listener in B that listens to broadcasts from A or C (I know this does not fit your current requirements). Ton
  23. QUOTE(Aitor Solar @ Jan 16 2008, 11:59 AM) Wonderful! Thanks a lot, it works like a charm. And I added it to the wiki Tips_and_tricks Ton
  24. I have written an installer VI in LabVIEW 7.0, and set it to auto-run. Now if I run the VI in another LabVIEW version I always get the 'Save changes?' pop-up from LabVIEW. Does anyone know how to handle this, I don't want to save the VI because that would mean that I first have to run it in 7.0 than in 7.1 and up. Ton
×
×
  • Create New...

Important Information

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