Jump to content

Ton Plomp

Members
  • Posts

    1,991
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by Ton Plomp

  1. Nice implementation. Were you aware that Jim Kring had already done something similar?

    Hi Mike,

    No didn't know, it looks like you had a different approach. And the old OpenG content is hard to get...

    Only one question when I want to probe a non-variant data type I get this error:

    post-2399-1165993925.png?width=400

    Has the probe engine changed?

    Sounds like an update with a resizable window is in order.

    Here you go! And you used another screenshot (mine was too big I assume?)?

    Have fun

    Ton

  2. post-2399-0-43332100-1345817232.png

    File Name: VariantProbe

    File Submitter: tcplomp

    File Submitted: 4 Dec 2006

    File Updated: 24 august 2012

    File Category: Custom Probes

    This Custrom probe is useful for browsing the contents of a variant.

    It will try to parse all the fields in the variant (notify me if you have a fail).

    It will track the history of the variant and allow you to pause on a change.

    It will present the data in a tree structure, allowing you to browse through the history.

    Be warned, the tree structure is great for viewing, but tracking a lot of history (>50 or so) will slow down the update of the tree.

    Version History:

    • 2.4: Immediate updating after changing of attributes
      Rebuild in LabVIEW 2011
    • 2.3: Fixed a bug that caused attributes not to be traversed on certain data-types
    • 2.2: Fixed a relinking bug
    • 2.1: Fixes a bug where unnamed cluster elements where used (http://lavag.org/topic/10269-discuss-variantprobe/page__view__findpost__p__67677)
    • 2.0: Added an XControl
      Show XControl in palette (under user.lib controls)
      Add coloring
      Add 'user permissions' on XControl
      Add Reset on XControl
      Add optionally traversing attributes on XControl
      Add optionally colorizing on XControl
      Add optionally resetting on XControl
    • 1.2.0: Upgraded to LabVIEW 8.5 to use Inheritance
      Support for Waveforms, timestamps and dynamic datatypes (thanks to Osvaldo)
      Added probe for an array of Variants
      Distributed as one .llb and added OGP installer
      If a Variant hasn't changed it's not decomposed (optimization)
    • 1.1.0: Support for attributes of variants
    • 1.0.1: Controls placed on a seperate pane
      Resize tree to upper pane
      Hide unused columns
      Limited maximum history length (default 10)
      Window resizable
    • 1.0.0: Initial release of the code.

    Uses the following OpenG packages:

    oglib_comparison-2.0-1

    oglib_lvdata-2.7-1

    oglib_file-2.7-1

    oglib_string-2.5-1

    oglib_error-2.3-1

    To get these OpenG packages use VIPM

    Ton

    Click here to download this file

  3. Nicholas,

    why do you mix two timing types?

    You have a timed sequence, which is the correct item for your application. And you use the wait function based on the OS time.

    I suggest you use the timing of the timed sequence (I have never used it, but think this is what you need):

    post-2399-1165671687.png?width=400

    In the first frame, I read the start time of the frame, add the wait time and then set the start time of the next frame. You should do this for the third frame as well

    I think you can limit your sequence to two frames, one where you make the output high, and one where you make the output low. The timing of the frame will set the speed correct.

    Ton

  4. Oh, OK. So I guess I should just send an email to NI and ask for a Licence? Great, I'll do that. Gee, I didn't think it would be so easy.

    Or as my friends say when we see a good looking girl in a bar:

    'No, do you have a smack in the face is what you can get'

    (which is similar to a saying: 'No, do you have, yes is what you can get' basically meaning that if you don't ask you will never get)

    Ton

  5. Hi all,

    any body had a LABVIEW PDF ?? :wub: i want any source related to electrical and electronics engineering :D plz help me I am requestin g some books but I didnot get them so far

    Hello Alnaimi,

    you should search the LabVIEW bookshelf, if you have LV 7. In 8 it is removed. But the LabVIEW help covers most everything there is to know about LV. Now if you want to digg deeper consider a LV basics course, if I'm right you can purchase those books without a course.

    But why do you connect LV and electrical/electronics engineering?

    LV is (almost) a full blown IDE for a programming language, and the block diagram might on the first hand look like a electrical print but there is no connection :nono:

    Now for starter questions (like your previous about the amplifier), the NI forums are better.

    Search on the LV learning center for the knowledge you need.

    Ton

    (oke the :wub: turned me over and the coffee is OK)

  6. "Hal9000 is my hero."

    :worship: :wub: :worship:

    Didn't know that I had so much in common with LV.

    Is this the reason that LV 8 introduced itself as seperate Application Instances, so they can speak Esperanto with each other?

    ne VIs kun erros

    Now comes the Q:

    what INI-key starts this mode?

    Second (philosophical) Q:

    Does LV sees itself as male, female or neutor?

    Ton

    PS Aristos, you made the sun come throught the clouds

  7. Hi Gianmarco,

    A framing error is mostly meaning there is something wrong with the serial settings.

    Have you tried other settings?

    A good thing to start with is MAX, if you succeed to communicate with the device from there you will get it in LV right.

    Second pass the VISA-resource from one subvi into the next, I'm not sure if it is usefull but better safe than sorry.

    You should rise your timeout, in MATLAB you use 10 seconds and here just 1.

    Ton

    PS don't quote a full post in a reply

  8. Hi gianmarco,

    I see some issues in your code, you tell VISA to wait for a termination character (the T-boolean), and specify this byte as 0x00 (a null-byte) but your specs say it should be a CR (0x0D).

    You try to read 1024 bytes thought you'll only get 14 bytes per reading.

    You specify XonXoff as flow control this doesn't show up in your specs

    Why did you modify the VISA configurator?

    Hopefully this code can help you:

    post-2399-1165086997.png?width=400

    Ton

×
×
  • Create New...

Important Information

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