Jump to content

Rayc

Members
  • Posts

    6
  • Joined

  • Last visited

    Never

Posts posted by Rayc

  1. If i'm reading the question correctly, I would suggest that one possibility would be that you could transform both the timestamp and datapoints to a string before putting them together in an array and writing them to a file. If you have an example that you can post of what your trying to do I might be able to come up with a better suggestion.

    Dave

    Hello Dave, Aristos

    Firstly, thanks for the reply.

    I am using the Express VI "Write LABVIEW Measurement File". I have tried to bundle both the string data (which is the format from the "Get Date/Time String", and my data which 1-D array) and connect them to the "signals" input of the file saving VI, but it baulks at this.

    I have also attempted to change the string data (time) to a number and add to the array, but the output format is not appropriate for my needs.

    The problem seems to be with the Express VI, and what it likes to see at it's input.

    I would like to post a copy (or even a cutout) of what I am attempting, but the project this belongs to is "commercial in confidence", so I am not permitted.

    Before I give up and return to the lower-level file saving VI's, I"ll spend some more time on this.

    Thanks again fellas

    Ray

  2. Hello All

    I have a wee problem (well, I'm scratching my head) which may be quite simple for others...but.

    I am collecting data from inputs, building an array and then saving the array points to a file using 'Write LABVIEW Measurement File". This is working fine.

    Now I want to add a timestamp (with the seconds field) to each set of sample points, but am having a mental block when it comes getting the above VI to accept the two different data types.

    What am I doing wrong here, and what am I missing.

    If anybody can help I would be most appreciative.

    Thanks and best regards

    Ray

  3. You need to be prepared to change your mindset - LV PDA is not LV!

    Well, it is LV in the sense that you use the same editor and can use a lot of the same code, but it's not LV in the sense that a lot of the functionality is missing, that there are *a lot* of bugs and that you might need to do code differently in order to get your program to run.

    First off, the device - get a Windows device. NI removed support for PalmOS in 8.2, so I wouldn't get Palm (although I don't have any experience with it). There are many varieties, but depending on your LV version, CE.Net 4.2 and above or WM2003 and above should work for you.

    Second, LV. The PDA module only started with version 7.0, so every version has seen some important additions. You should consider getting a newer version of LV for this (7.1, for instance, does not have the ability to display arrays). Also, be aware that there is no RTE for the PDA module - instead, LV translates the code into C and then compiles it. This is an opening for a lot of bugs, which do exist in the PDA module - working around them can make your development time a lot longer.

    PDAs are significantly slower than PCs - be aware that there will be limits to how fast your program will run. You might need to do some optimizations contrary to normal LV style (like having less subVIs). PDAs also use batteries, especially when dealing with wireless communication. Be careful if you get an industrial PDA, because I have seen that the special power optimizations used by these can mess up your program.

    You should also consider licensing issues, because if you want to distribute more than one copy of your program, it will cost you. NI should be able to give you the details.

    After all this, I would suggest that you consider another alternative, like a thin Linux client which will run an LV application or a wireless connection to a Windows server which will be the one actually running your program. A solution of this sort will get you around all of the problems of the PDA module and might be a much better solution for a system where you have a computer anyway.

    Thanks for your considerations Yen......food for thought

    best regards

    Ray

  4. Hello All

    I am about to undertake a project which will require the use of labview on a pda. Although I have been using labview for quite a long time, I am all at sea when it comes to porting over to PDA's.

    Currently I use Labview 7.1 on a desktop PC, but am stunned by the amount of information regarding this topic, and don't know where to begin.

    Could somebody explain to me what basic requirements are necessary such as.....type of PDA (not model, although anybody with recommendations, please do so)....O/S running on the PDA.....labview software. etc.

    I realise the broadness of this query, but anybody with successful experience in getting a system running are welcome to respond.

    BTW...the system will be used in remote machine monitoirng (digital i/o control, and analog data monitoring.

    Thanks for any assistance and forebearance with my ignorance

    Regards

    Ray

  5. sorry, I could not resist (as the question is allready solved):

    mouse over a hot area? make sure is is made out of asbestos or watch it melt (and don't forget to protect your mouse pointer, it may melt, too, or even burn! ;)

    cheers,

    CB

    Thanks guys for the tips....and the humour. Both made my day.

    See you soon from downunder

    Ray

    Hi Rayc welcome to LAVA.

    I have attached a sample VI that might give you some ideas. It is a simple way to display information that is triggered off the mouse enter and mouse leave event for the indicator in question.

    I tried using the tip strip property of the indicator but the value does no update while the tip strip is visible.

    For more advanced options, you may want to have a look at the examples for dynamic events that ship with LabVIEW.

    Hope this helps.

    Cheers & Beers

    :thumbup: & :beer:

    Thanks for the example Phil, unfortunately I'm using 7.1 and can't open it........

    Ray

  6. Hello All

    My current application requires that the user be able to hover the mouse pointer over an indicator on the front panel (say a tempereture reading) and have a small window pop-up with extra information enclosed (say a SAR value), and disappear when the mouse moves on.

    I simply have no idea where to begin, and would appreciate some assistance from others who may already have achieved this.

    Thanks in advance guys...and gals.

    Regards

    Ray

×
×
  • Create New...

Important Information

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