Jump to content

MikaelH

Members
  • Posts

    835
  • Joined

  • Last visited

  • Days Won

    49

Posts posted by MikaelH

  1. Hi Jim

    I had these problems when adding drag support from the Project Tree to my UML modeller.

    I had to solve it by using the Input Device Control VIs.

    This code will do the first part: -Know when the move is over the Path Control.

    Download File:post-941-1211341397.vi

    -The next should be to check if the button was pressed, when you entered the VI (drag started outside VI)

    -Check for button released.

    -Then you'll get the Path-Value change event.

    But of cause you like to check the content of the dragged file before, the user releases.

    E.g. Flag that the file has the wrong format and can't be dropped here.

    I guess you have to use some windows API to get the content of the dragged file.

    Good luck,

    //Mikael

  2. QUOTE (Yen @ May 20 2008, 03:38 AM)

    Frameworks which rely on features which are supported in RT should work, so Sciware GOOP should work (as you've seen) as well as dqGOOP (although I haven't actually tried it on RT). LVOOP is still not supported (and I don't think it's supposed to be in the near future) and I have no idea whether Endevo GOOP is supported or not.

    The Endevo GOOP2, is pure LabVIEW without lvclasses, just like Sciware GOOP so that should work.

    //Mikael

  3. Hi Tomi

    I've used LabVIEW to measure the composite video signal before.

    But what I never heard anybody managed to do is to generate a composite video signal from LabVIEW before :-)

    So if you get the fastest analog out card, and a real fast computer you could generate your own video signal and feed it to a TV :-)

    That would be something to show at NI-week!

    post-941-1210881828.png?width=400

    Good luck

    //Mikael

  4. Hi Tomi

    I've experiensed the same kind of effect, when I run a convert application from EndevoGOOP2 to EndevoGOOP3, the project I tried to convert took 65 hours, and it spend a couple of minutes each, when saving a modified dynamic dispatch VI.

    I guess your Save All, is about to save that kind of VI...

    I would start by right click on the classes one by one and select "Save All(this class)", and you could also try to open one class (.lvclass) at a time.

    And then "Save All(this class)", this approach has help me a lot.

    You could also try to remove all inheritance links among your classes, save all, and restore the inheritance.

    Cheers,

    Mikael

  5. I have had to use the "Deallocation VI", in one of my current test system.

    post-941-1210024602.png?width=400

    But I also needed to increase the memory to 3GB for LabVIEW to use.

    It's a simple switch in the "c:\boot.ini" file.

     [boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
    
    [operating systems]
    
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect [b][color="#ff0000"]/3GB[/color][/b] 

    You can read more about this in the section "Enhancing Virtual Memory Usage" in the LabVIEW help Contents: "LabVIEW 8.5 Features and Changes"

    Cheers,

    Mikael

  6. QUOTE (netta @ May 1 2008, 07:08 AM)

    LabVIEW: Memory is full.

    Hi

    I have a couple of suggestions.

    My first option would be to upgrade to EndevoGOOP3 class templates, using the GDS function "Convert Goop2 classes to Goop3...".

    If you can send me the code, I can help you out in converting it.

    I guess it's not a memory problem but if you're running LV 85, you could increase the memory from 2GB to 3GB for LabVIEW to use.

    Since Windos normally limits an application to use only 2GB.

    You do this by adding the /3GB swith in the c:\boot.ini file, like this:

    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect [b]/3GB[/b]
    

    You could also try to build the executable with the "Enable debugging" mode on, if you are running LV8.5.

    Cheers,

    Mikael

  7. post-941-1204168174.png?width=400



    Do you want to join my team...
    Cheers,
    Mikael

    Optium Australia is a rapidly growing high-tech company that designs and manufactures communication products for optical fibre telecommunication networks. We have a number opportunities for Labview Software Engineers to join the Manufacturing Software Team. This team is primarily responsible for developing automated solutions for high precision manufacturing incorporating vision systems and precision motion control.

    Optium Australia is located 5 km from Sydney's CBD with excellent access to public transport. At Optium, we have created a philosophy that thrives on change, new technology, teamwork and partnerships within and beyond the organisation. We set expectations and exceed them...consistently.
    For more information about these roles please send your CV to nmartorano@optium.com



    Position Title: Manufacturing Software Engineer
    Reporting To: Process Engineering Manager
    Effective Date: Feb 2008

    Main Focus:
    Responsible for developing and improving manufacturing and test software for the production of optical modules for the telecommunication industry.

    Main Activities/Tasks:
    Program manufacturing rigs used in the manufacture, calibration and test of optical telecommunications devices
    Liaise with or Manufacturing Engineering staff to ensure software functionality meets the requirements of the automated equipment's specification and the specifications of the product being produced
    Liaise with Production staff to ensure ease of use and understanding of the GUI.
    Liaise with suppliers to understand the operation of their equipment. ie: software drivers and settings to enable the combined components to work seamlessly as a constructed/coordinated rig.

    Experience required:
    Extensive Labview programming experience (2-3 years) particularly in relation to the development of software for automated test equipment.
    Experience in developing software for precision motion control systems and interfacing to instrumentation
    Flexibility and ability to handle multiple tasks in a high energy environment.

    Education & Skills
    Degree in Science, Engineering or Computing.
    Good communication and interpersonal skills strongly preferred, with the ability to work with people in all levels of the organisation.
    Programming skills in LabVIEW ver 7.1 or higher with particularly with an emphasis on the control of instrumentation and motion control.
    Ability to work in a dynamic start-up environment

    Desirable:
    Experience with developing vision systems and using National Instrument's Imaq package.
    Understanding of Object Oriented Programming within a Labview development environment.
  8. QUOTE(Alexis @ Feb 3 2008, 04:21 AM)

    Hi Alexis

    When I have trouble getting my hands of a easy way to hook into an application, I use AutoIT (http://www.autoitscript.com/autoit3/downloads.php).

    This is a script language that can be compiles into an Executable.

    Then I run the exe-file from LabVIEW.

    The AutoIT scripts are very flexible when it comes to automate GUI tasks.

    I use it for automated tests of LabVIEW GUI applications.

    Some features:

    • You could emulate mouse clicks and keyboard strokes.

    • Read write data from/to files

    • And also it's free!!

    A script could look like this:

    [font="Times New Roman"][size=3]Run("notepad.exe")
    WinWaitActive("Untitled - Notepad")
    Send("This is some text.")
    WinClose("Untitled - Notepad")
    WinWaitActive("Notepad", "Do you want to save")
    Send("!n")[/size][/font]

    I have also done my own LV-application that records the keyboard and mouse and generates an AutoIT script.

    Cheers,

    Mikael

  9. Hi Omar

    I've never experiensed this kind of delay when updating my attributes using the Endevo classes.

    But I got alot of crashes in 8.21 when attribute (type-defs) has other classes public type-def inserted in them.

    Currently I'm working on 5 projects using from 5-30 Endevo Classes in them but that is in 85 and I'm NOTusing IMAQ references.

    You could try to drop your project file and create a new empty project and add the files one by one again.

    Cheers,

    Mikael

×
×
  • Create New...

Important Information

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