Kurt Friday

Just took a look on the NI Instrument driver site and there is a driver for a

Uni-Trend UT804

So I'd take a look at that and see how they have implemented the protocol, I suspect it would be similar.

Also go to the Uni-Trend site for your model there is some software which you can interface to your multimeter which will allow you to read values etc, its not a driver but the useful thing is that it will give you a reality check, also if you build a serial proxy or sniffer you can then look at the packets going back and forth which will give you some insight into what you need to implement in your own driver.

But in the mean time definitely do as Francois has suggested and contact the manufacturer and ask for the protocol.

Hi John

I built the same code in LV 7.1 and you don't see the issue, and its fine in 8.2.2 however at 8.5 you see the behavior you are experiencing.

So it looks like a bug.

A possible work around may be to build a LV 7.1 dll that does this operation for you.

hi

i try your program

but it does not work i do not know why

plz can you add your program to my attached file

mey be i made some mistake in some where

thanx for helping me

Ammar

Sure here it is, done in LV 7.1

LogDat.WriteDaily.vi

Hi Kurt - thanks for your reply.

I have noticed the "do not delete" comment for a property node for a control whilst trolling through some of your old code here

Ha, cool, didn't recognize you Jon without your Bee Avatar.

I prefer method 1

What I do instead of waiting in a loop is to pass an occurrence ref into it and then when the spawned vi is loaded it sets the occurrence which is the signal to the launcher that it can continue.

Another advantage I like about method 1 is that you can include your vi within your code but have it cased out, so if it's broken you know about it at top level also you don't need to include it as a support file when you build, its already there.

One trick you need to be aware of is that LabVIEW will strip the front panel of any vi unless you have the vi property "Show Front Panel When Called" set to true or you have a property node of a control in the code.

I don't know the performance advantages of each method though.

I don't know if it will help at all without seeing the rest of your code but try data flowing those two case structures together, ie left one must complete before right.

Hi Ammar

I think what you want to do can be achieved with a vi like the following.

Each time the date changes a new data file is generated.

I've been having problems with creating the executable application. I get to the Project Explorer, then right click on Build specifications and all I get is "New >> Source Distribution" rather than the "Application" tab that I need. Am I not saving the instrument correctly to get the correct menu? (I tried to upload a screen shot, but it won't let me )

Do you have Application Builder or LabVIEW Professional?

Have a look in your NI License Manager which you can access from Start Menu >> National Instruments >> NI License Manager have a look at what you have activated.

What is the difference between LVOOP and GOOP Developer ?

Hi Bjarne

The Open Source GOOP Templates that GOOP Developer uses to build classes was developed by SciWare and JKI before LVOOP was around and doesn’t use LVOOP in any form. The differences between the two are.

Advantages

• You can develop OOP systems for RT platforms.

• Building your system to an exe is really easy, just add your top level vi and then build. Building a system that includes LVOOP is a more complicated process.

• It’s a by reference implementation, LVOOP is natively is by value, although there are LVOOP frameworks that will give you by reference implantations see Endevo's GOOP Development Suite (GDS).

• You can create Active Objects, i.e. each instance has its own process running in the background. However there is a Design Pattern in GDS that I contributed to with Mikael Holmström that will allow active objects.

• You can develop in LabVIEW 6.1 and up.

• The GOOP Templates are open source under the BSD open source license.

Disadvantages

• You have to be vigilant about keeping your interfaces between parent and child methods the same, there is no development environment mechanism that will warn you, like LVOOP does.

• You cannot easily shift inheritance from one class to another. In GOOP Developer you build a child from a parent.

• Super Messaging is more elegantly implemented in LVOOP.

• You have the ability in LVOOP to make methods private or protected.

• A method call in LVOOP is faster than that derived from an existing Open Source GOOP Template.

Thanks for the great news Kurt. If you don't mind. Why the decision?

I suppose my main reason for doing this is that I get a real kick out of having my software used.

Making money out of GOOP developer was never my primary motivation for creating it, it grew out of an interest of mine and then into a passion/obsession, I had tremendous fun developing it and it’s a tool I cant live without and I love it when other developers are using it to build their systems. It’s paid for my LabVIEW licenses over the years and put some change into the beer fund, but the market that this tool appeals too though is quite small, smaller still is the group within that market who can afford the tool or get approval to buy it.

About 18 months ago I released GOOP Developer free of charge for academic use because there were people out there who wanted to use it for academic purposes but couldn’t afford or get approval for it, so I thought it would be cool to help them out.

Another reason is that GOOP Developer has marketing value, it gets people visiting my site which is important now that I’m working towards becoming an alliance member and concentrating on my development services.

Hi Everyone

I just wanted to mention that GOOP Developer 2.2 is now compatible with LabVIEW 8.6

To upgrade, evaluate or to learn more please visit my site

GOOP Developer 2.2 is also available free of charge for academic use which includes teaching and research.

Cool, very clever :thumbup:

No problem mate

Does the code I posted work on your laptop?

At the moment I'm not sure what the issue could be, could you post that code you displayed?

Try this

Download File:post-1058-1213255078.zip

Just a couple of updates.

1) The GOOP Template SciWare_JKI_V1R4 is now included in the build. This template resolves a bug with reentrant virtual methods in 8.5

2) All downloads are now zip files. Were previously rar renamed as zip which caused a problem if you tried to use windows zip.

Hi JG

I've updated my site and GOOP Developer 2.1 is now compatible with LabVIEW 8.5

To upgrade to GOOP Developer 2.1 Full simply visit the support page and enter the e-mail address you used with your order.

Hi JG

Yes classes developed with GOOP Developer will work on RT. I have a version that works with 8.5 that can be released so I'll get moving on that and put an update out soon.

I promised to use my LabVIEW powers for good, not evil, so I had nothing to do with this. Perhaps this is a sign that there is a market for a Euthanasia toolkit for LabVIEW?

Hi John

I did a Savitzky Golay smoothing filter some time ago which should help you obtain a smooth 2nd derivative, it might be worth having a play with.

http://www.sciware.com.au/freesoftware/index.html

Cheers

Kurt

I remember a few years ago the DSC shipped with a cute example called Chemical Reactor which had peristaltic pump indicators that were pic rings. I've scrounged through some old code and found the control.
 

[Moderator Note]

This post contained a broken link to an attachment. Best effort was made to find the attachment and fix the link. Unfortunately, the missing attachment could not be found. (ID 6360)

QUOTE(Sparc @ Jul 10 2007, 07:37 AM)

Plain labels don't have property nodes.

You can access the properties of a decoration, the following example shows how to change the visibility of a label decoration.

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

QUOTE(yen @ Jun 28 2007, 01:37 AM)

However, wasn't there a version of GOOP developer which did not require a license for commercial systems? It's possible that people still remember that.

Hi Yen

There was never a version of GOOP Developer that was free to use for commercial use. There are three versions of GOOP Developer, Evaluation, Full, and recently Academic. There is an open source GOOP Wizard that can handle creation of classes using the open source GOOP Templates, but it is nowhere as featured and user friendly as GOOP Developer.

Evaluation means exactly that, you are evaluating GOOP Developer, it even nags the user that they are using evaluation software and prompts them to purchase, I don't know how users can be confused about this.

Lately I have come across several users who have used the evaluation version of GOOP Developer to build commercial systems, which is a violation of the evaluation license. These encounters have been mostly by chance and suggests that the number of violations are quite large.

GOOP Developer cost me a lot of time and money to develop and supporting it is a continuing expense, I have to purchase my own LabVIEW licenses so I can maintain compatibility.

I really hate having to bring this up, but please, if you have used or are continuing to use the evaluation version to build classes for commercial use, then you need to purchase the full version.

QUOTE(yen @ Jun 14 2007, 01:50 AM)

You should read NI's news more often:

I really like the new datatype, G-Strings