Jump to content

Mikkel

Members
  • Posts

    74
  • Joined

  • Last visited

Posts posted by Mikkel

  1. Ok, nobody answered my post, so I sent the same question to NI support, and here is the response.

    -Mikkel :)

    --

    Here is what R&D had to say:

    1. The 'Container State / Run Mode?' is always True in the XValue

    XControls.

    Container State/Run Mode? reflects the state of the VI that hosts the

    XControl. In this case, because the inner XControl is owned by a Facade VI

    which is always in run mode whenever the outer XControl is in use, the

    state is always TRUE. One way to cleanly handle this situation is for the

    inner XControl to export a property called "Run Mode" which can then be set

    by the outer XControl whenever it reacts to Exec State change. The shortcut

    menu approach is not reliable, especially if LV changes the way it builds

    the shortcut menu in future.

    2. The state for the XValue XControl is not saved - the 'Convert State For

    Save.vi' for this XControl is never called, when inside XCalculation.

    The Convert State For Save is called when the host VI is saved. In this

    case, the host VI for the inner XControl is the Facade VI of the outer

    XControl. The current architecture of XControls does not save the Facade VI

    along with the instance of the XControl due to various reasons (memory

    usage, revisioning etc..). This is something we will address in future. No

    promises of an immediate fix because this requires a major architecural

    change. The short term workaround is as the customer suggested. The outer

    XControl need to extract the states of the inner XControl and save it with

    it s own state.

  2. Hi

    I am making a system, where it makes sense to put one or more XControls (XValue) inside another XControl (XCalculation).

    I am seeing (at least) the following problems in trying to get this to work:

    1. The 'Container State / Run Mode?' is always True in the XValue XControls.

    2. The state for the XValue XControl is not saved - the 'Convert State For Save.vi' for this XControl is never called, when inside XCalculation.

    I have worked my way around point 1 (by checking the contents of the shortcut menu, which changes when running, ugly!) and I'm starting to work around point 2 by having the XCalculation XControl store the states for the embedded XValues, but before I spend too much time getting this to work, I would like to hear if anyone have seen theese problems, and may have a elegant solution?

    It should be mentioned that the project is using LabVIEW 8.0.0, but I am open to using a newer version of LabVIEW, if this solves the above problems.

    -Mikkel :)

    Edit: Just tested it - seems like version 8.2.1 and 8.5 do the same as 8.0.0.

  3. Hi Hakan

    Try moving the "VISA Flush IO Buffer" so it happens before you perform the the "VISA write".

    What might be happening is that you flush the expected result before trying to read it.

    Timing issues could explain the differenence between how the code performs on the internal and external RS232 port.

    -Mikkel :)

  4. QUOTE(Bryan @ May 16 2007, 01:33 PM)

    I just tried using the command line approach and the values returned to me don't match the configuration in device manager. i.e. Device Manager = 9600,8,n,1. command line = 1200,7,e,1.

    I only have one com port on my current machine, so I'm sure I'm accessing the correct one.

    Device Manager shows you the default Windows setup of the port.

    If this is what you want, I'm shure you can find these values in the registry somewhere.

    The command line shows you the current settings of the port ie. what setting were used the last time the port was accessed by an application.

    I just re-read your first post, and I may have misunderstood what you wanted to do - I thought you wanted to see what parameters some other piece of software used for accesing the port.

    -Mikkel :)

  5. QUOTE(crelf @ Apr 23 2007, 02:16 PM)

    Right - www.google.com isn't a webpage - it's a placeholder that will (by default) push you over to www.google.com/index.html, so asking DataSocket for the text of the page at www.google.com won't work.

    Well, not working, as in closing LabVIEW with the message attached below is a bit harsh.

    I would prefer an error in the 'error out' cluster... :shifty:

    http://forums.lavag.org/index.php?act=attach&type=post&id=5603

    -Mikkel :)

  6. Maybe you should try to look at the graph examples that come with LabVIEW :book:

    The Example Finder can be started by clicking 'Find Examples...' in the lower left corner of the 'Getting Started' screen.

    You can also access the Example Finder through the menu 'Help / Find Examples...'.

    -Mikkel

  7. QUOTE(gustav @ Apr 5 2007, 07:59 AM)

    Personally I would be very happy with that solution but unfortunately it is not what the customer requested :) . Thanks anyway.

    The 'simple' hackish way to accomplish what you want is to create two offscreen (won't work if hidden) buttons with the keyboard shortcuts you want, and then increase or decrease the value of the slider (using local variables) if one of the buttons is 'pressed'.

    You can of course also use the event structure, which would be more elegant. There are no pitfalls in doing this, as far as I am aware :)

    -Mikkel

×
×
  • Create New...

Important Information

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