Jump to content

jgcode

LabVIEW Tools Network
  • Posts

    2,397
  • Joined

  • Last visited

  • Days Won

    66

Posts posted by jgcode

  1. QUOTE (dblk22vball @ Nov 22 2008, 12:15 AM)

    I was thinking that it might have something to do with subpanels, but it did not seem to look the same, and seems somewhat complex to pass the data set on the page to the main UI, while allowing the main ui to handle events when the person is editing the settings. (I know that you can use the get controls, set controls methods, but thought there might be a cleaner option)

    I suppose I could use a tab control as well, but it just didnt look as clean as I wanted.

    I'm with Andrey on this one - I don't like use the tab control as a type def.

    I use the plugin architecture for most GUIs I create, as it is a flexible, scalable design.

    But I don't think it hard at all to pass data.

    I dynamically register all universal controls (hosted by the Main UI - e.g. tree control) to an interface that the plugin vis can access

    Each plugin should handle its own data and have its own UI (no need to pass data to the Main UI)

    Each screen's data is an object(s).

    Each other screen can access another screens data through an interface if needed

  2. QUOTE (GraemeJ @ Nov 21 2008, 02:08 PM)

    Is it possible to use a latching mechanical action front panel switch, and have the switch correctly reset, when it is used in more than one event case?

    Any help would be appreciated.

    Regards,

    GraemeJ

    If you are using the Mechanical Property "latch" the you can not use a local variable or the write to it's value property.

    Using an event structure with the boolean placed in the loop is used to refresh the button when a value change occurs.

    But some more info would help...

  3. QUOTE (crelf @ Nov 11 2008, 09:34 AM)

    Aside: I know a lot of LabVIEW programmers that shy away from VI Logger and Signal Express (and TestStand for that matter) because they think that they can develop their own utilities more quickly and with more appropriate features from scratch in LabVIEW. My answer - that *may* be true, but work to meet the requirements of the project that you're working on (use the right tool for the job :) )

    Yes I was quite surprised when I found out that you can write VI plugins for SignalExpress.

    So it does have a place in application development.

  4. QUOTE (crelf @ Nov 11 2008, 09:25 AM)

    A) 10 V signal with 0-5 V ADC range: Signal is from 0 to 10V, ADC is from 0 to 5V, so a gain of 0.5 is appropriate.

    B) 5 V signal with 0-10 V ADC range: Signal is 0 to 5V, ADC is from 0 to 10V, so a gain of 2 is appropriate.

    C) 10 V signal, with 0-10 V ADC range: Signal is from 0 to 10V, ADC is from 0 to 10V, they match so no gain required.

    D) 1 V signal with 0-10 V ADC range: Signal is from 0 to 1V, ADC is from 0 to 10V, so a gain of 10 is appropriate.

    Ahh.. now i understand the reason behind the question!. I will withdraw my previous lame attempt :unsure:

  5. <edit> I suck </edit>

    QUOTE (Minh Pham @ Nov 11 2008, 08:55 AM)

    I have another one:

    All of the following are components of an error cluster, EXCEPT:

    A Status

    B Code

    C Source

    D All of the above are Error Cluster components.

    I have no idea which one NI wants to EXCEPT here???

    To me they are the three components of an error cluster. Arent they?

    Yes the answer is D, Status, Code & Source are all components of the Error Cluster.

  6. QUOTE (crelf @ Nov 10 2008, 12:40 AM)

    I'll drink to that :beer:

    PS: on my recent trip downunder, I wasn't able to get to my home state (New South Wales), but I was thankfully able to find my favorite beer (Tooheys Old) on draught in Melbourne. The bar chick told me that you can get both Tooheys Old and Extra Dry on tap all over Melbourne now - it's good to see that Victorians are starting to come to their senses...

    Oooo I used to drink Tooheys Old on tap at Uni and always got strange looks from everyone... they were too young to appreciate the quality of ye dark ale.

    So I will drink to that :beer:

  7. QUOTE (crelf @ Nov 10 2008, 12:40 AM)

    I'll drink to that :beer:

    PS: on my recent trip downunder, I wasn't able to get to my home state (New South Wales), but I was thankfully able to find my favorite beer (Tooheys Old) on draught in Melbourne. The bar chick told me that you can get both Tooheys Old and Extra Dry on tap all over Melbourne now - it's good to see that Victorians are starting to come to their senses...

    Oooo I used to drink Tooheys Old on tap at Uni and always got strange looks from everyone... they were too young to appreciate the quality of ye dark ale.

    So I will drink to that :beer:

  8. QUOTE (Vinny @ Nov 9 2008, 02:02 AM)

    From a LV development standpoint I found working with WinXPE was identical to working on standard XP. I did not experience any performance issues either, but the application was not very resource intensive.

    Thanks mate :beer:

    Time to get one methinks.

  9. QUOTE (Vinny @ Nov 8 2008, 11:32 AM)

    I've used WinXPE on a TPC with great success. I used an Advantech panel (TPC-1261) with a pre-configured distribution of WinXPE. We loaded up VISA run time and the LV run time and ran our application with no issues. We did start out using a panel with Windows CE and the TP module, but it was full of bugs and other issues.

    Thanks Vinny.

    I have done some sub-par GUIs on the TPC-2012 due to bugs, issues and general restrictions of using WindowsCE.

    Since you have experience in both, is there a huge improvement over on screen graphics and general performance?

  10. QUOTE (NewUser @ Nov 6 2008, 12:33 PM)

    :beer: Well you have to start somewhere.

    QUOTE (NewUser @ Nov 6 2008, 12:33 PM)

    What is the purpose of the shift register?

    To store the last value (n-1) from the previous iteration

    You can also click on it and drag it down to get n-2, n-3 etc...

    Go to the LabVIEW Help and do a search to find out more about it.

×
×
  • Create New...

Important Information

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