Jump to content
News about the LabVIEW Wiki! Read more... ×

Deon

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0

About Deon

  • Rank
    Active
  • Birthday December 27

Profile Information

  • Gender
    Male
  • Location
    New Forest

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since
    1995
  1. Went an NI seminar on NXG recently and the app engineers have indicated that the two versions of labview will continue side-by-side for the foreseeable future, with the NXG continuing as a separate application. FWIW
  2. How to Downgrade DataSocket Server to 4.0 Download LabVIEW Run-Time (LVRT) Engine 6.1 Installer Delete the Datasocket folder in Program Files/National Instruments (! this is very important !). Now run the LVRT 6.1 installer and allow it to do a default install. Run the DataSocket Server file cwdss.exe in Program Files/National Instruments/Datasocket and wait for it to initialise and open. Click on the DSS menu Help/About Datasocket Server and verify that the version displayed on the About panel indicates 4.0 Click here to view the article
  3. Version 1.0

    142 downloads

    The Threshold Hysteresis VI allows an input (for example, a sensor) to drift out of an inner limit without generating an invalid flag, but if it drifts outside an outer limit it then becomes invalid. For the reverse, when the input crosses back into the outer limit it remains invalid until the value falls inside the inner limit. For simplicity, only one input parameter is provided for both the inner & outer limits, and is negated for the lower limit, as generally tolerance limits are equidistant from the nominal.
  4. Name: Threshold Hysteresis v1.0 LV8.6.1 Submitter: DeonvanBergiestad Submitted: 10 Nov 2014 Category: General LabVIEW Version: 8.6 License Type: GNU Public The Threshold Hysteresis VI allows an input (for example, a sensor) to drift out of an inner limit without generating an invalid flag, but if it drifts outside an outer limit it then becomes invalid. For the reverse, when the input crosses back into the outer limit it remains invalid until the value falls inside the inner limit. For simplicity, only one input parameter is provided for both the inner & outer limits, and is negated for the lower limit, as generally tolerance limits are equidistant from the nominal. Click here to download this file
  5. Name: Deon Bester Submitter: Deon Submitted: 06 Nov 2014 Category: *Uncertified* LabVIEW Version: 8.6.1 License Type: BSD (Most common) Sexiest threshold hysteresis VI on the web! Click here to download this file
  6. Deon

    Unable to upload files

    Yes could you send a status update as the upload failure is quite frustrating. Thnx!
  7. Deon

    NI Visit 2002

  8. QUOTE(jpc @ Nov 16 2007, 11:53 PM) QUOTE(jpc @ Nov 16 2007, 11:53 PM) We are experiencing what we believe is a memory leak in Labview 7.1 when attempting to open and reopen an ODBC connection to a SQL database.I have seen this topic mentioned in several places......but, the problem resolution seems to be to just open and close the connection once. OK, you lose 4K of memory and no big deal.But in our case, we have a control system reading and writing to a SQL database at regular intervals, and would like to re-establish that connection automatically if it becomes broken (server crash, maintenance, backups, etc.). So the app was designed to loop every few seconds trying to reconnect. We wrote the code, it works well unless the server is down for extended periods of time. Then we noticed the app crashes from depleted memory. We isolated the problem to an open/close connection problem just like in the links above.So my questions are:Has this been confirmed to be a Labview problem?Or is it a ODBC problem with SQL?Does anyone know if NI has ever addressed this issue?And, yes, we have a workaround in place. The error is flagged and an operator must manually reconnect when the server is determined to be back online. We cannot risk crashing the control system. We would like to go back to the automatic reconnect, but I still haven't seen this memory leak problem resolved. My colleague who wrote code claims Labview 8.5 still has not fixed this problem.-John QUOTE(jpc @ Nov 16 2007, 11:53 PM) We are experiencing what we believe is a memory leak in Labview 7.1 when attempting to open and reopen an ODBC connection to a SQL database.I have seen this topic mentioned in several places......but, the problem resolution seems to be to just open and close the connection once. OK, you lose 4K of memory and no big deal.But in our case, we have a control system reading and writing to a SQL database at regular intervals, and would like to re-establish that connection automatically if it becomes broken (server crash, maintenance, backups, etc.). So the app was designed to loop every few seconds trying to reconnect. We wrote the code, it works well unless the server is down for extended periods of time. Then we noticed the app crashes from depleted memory. We isolated the problem to an open/close connection problem just like in the links above.So my questions are:Has this been confirmed to be a Labview problem?Or is it a ODBC problem with SQL?Does anyone know if NI has ever addressed this issue?And, yes, we have a workaround in place. The error is flagged and an operator must manually reconnect when the server is determined to be back online. We cannot risk crashing the control system. We would like to go back to the automatic reconnect, but I still haven't seen this memory leak problem resolved. My colleague who wrote code claims Labview 8.5 still has not fixed this problem.-John Hi JohnI had a memory leak with MySQL using LabVIEW 6.1 and it turned out to be the version of OBDC driver. I had to revert to an earlier version, rather than the latest, to solve the problem; namely MyODBC-3.51.04.exe.Attached is the installation document I produced. Don't know if this will solve your problem, but maybe it will provide additional info to help you.Best Regards.
  9. Deon

    Another name for "LabVIEW 2 Globals"

    QUOTE(Jim Kring @ Jan 11 2006, 08:44 AM) At SALT we called them Object Data Managers - I think a term that came from the C world.
  10. Deon

    Another name for "LabVIEW 2 Globals"

    QUOTE(Jim Kring @ Jan 11 2006, 08:44 AM) At SALT we called them Object Data Managers - I think a term that came from the C world.
  11. Deon

    LabVIEW Performance & Memory Management

    QUOTE(Neville D @ Jul 21 2007, 01:45 AM) Yip, find attached file.
  12. Deon

    My Real-time Experiences

    Hi Guys Just wanted to add my 2 cents worth! I am busy developing code for a FieldPoint Rt controller, and found DataSocket too slow, TCP too much hassle, and so settled on UDP to communicate between the Host PC and the RT module. Works very well. Also, as I'm programming in LV6.1, to pass data between the core & comms loops in th RT software, I used an ODM (Object Data Manager), which is simply a non-running While Loop with a shift register and a case statement to Set & Get the required data. Btw, I use complex clusters for all data communication and transfer. Thanks for a fantatsic site! Regards Deon.
×

Important Information

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