MikaelH

If you probe the Image coming out from the GetImage Invoke node, does that contain the right image? Try 1 Bit of the Image Depth and use the Boolean 2D array out from the Unflatten Pixmap, does that work? --Mike

What version of LabVIEW are you using and what default fonts are you using? Could you give me a image screen shot of your block diagram, and I can update the code to support your font. Cheers, Mikael

I got it working in LabVIEW 8.6, but your right in 2009 it doesn't work. The characters in the Event Structure seams to be a pixel further down, compared to my tests in 8.6. By updating the search algorithm this could be fixed. Feel free to hack the code :-) If you're wondering about the second search loop, it's because putting some characters next t each other will remove the gap between the caracters so it's hard to splt the characters up. e.g. the "kl" next to each other don't generate a gap. Cheers, Mike

If you probe inside the OCR VI, does is extract the image (2D boolean array) for the text withing the quotation marks? It only sort the cases based on the name of the controls, the timeout e.g. will return an empty string. The OCR is very stupid, and I've just learned it exact how every character looks like and it does a one to one comparison. I noticed that even if I use different fonts and sizes the font, in the Event structure it is always the same, at least on my computer. Give me a screen shot of you event structure/font and I can compare. Cheers, Mike

I've updated the post, with a new download. //Mikael

Thank you for that. It would be nicer if they released the full API for Event structures of cause :-)

A while back I asked if anybody know how to sort the event structures by using scripting, and unfortunately that couldn't be done by scripting yet. So the other day when I held my weekly LabVIEW meeting, I went through how this could be done. Here is the solution: Here is a prototype RCF plugin. SortEventStructure2.zip Cheers, Mikael

Do I understand it correct, that you first want to create a generic object and then in some cases transform it to a more specific type? You can't just type cast it, you have to create a new Specific Object and copy the data over the new object. Cheers, Mikael

I've also used NSIS (8 years ago), with a combination of Labview App + Device drivers and windows application, worked great. But when I used it it was only script based and took a while to learn the syntax.

But then you realize that you just have to right click and select TortioseSVN->Revert to solve all your problems

Just one thing I saw, the codes will not give the same result since when you use the Insert Into Array, you have wired the Zero contant to the column input. Do you get the same behavior when wiring it to the Row input? Cheers, Mikael

Sure the PowerMeter might be the brain in the system, but I would like to hide that from the user insdie the PowerSensor class. I don't want the user to have to know that the Range of the PowerMeter has to be change to make a PowerSensor reading. So when I call PowerSensor.GetPower(ThisRange), this object would know which PowerMeter it's connected to and what the current Range is, and change it if needed. Also If one PowerSensor dies, and we replace it with another PowerSensor, that might be a standalone sensor without a PowerMeter, or connected to another PowerMeter, I don't want the user to need to handle this. That's just how I would have solved it. Cheers, Mikael

Hi Pete This is a common problem and I’ve seen many people going down the road of having one Power Meter object and then calling it like PowerMeter.GetPowerFromSnesor(1..n). I don’t like this approach because if you only start with only needing 4 sensor (assume that the Power Meter only have support for max 4 sensors), then your top application only needs to create One PowerMeter object. Then you suddenly needs another PowerSensor, then you have to create another PowerMeter Object and know which sensor ID and which PowerMeter every sensor is linked to. Instead I would go for the PowerSensor objects. Remember that the objects should reflect the reality, and it’s Power Sensors you are dealing with. If you need to have the knowledge of the PowerMeter I suggest that every time you create a PowerSensor object, just also creates a PowerMeter Object if needed and adds a reference to it. When I say needed, I would use named objects of the PowerMeter and if the PowerMeter this sensor is using has not been created yet they create it, and if it is already created then refer to the same object. Of cause this requires object by reference. This is how would have done it. PowerSensors.zip (LV 8.6, using GOOP3 object from GDS) Now I like someone to give me the solution to do this with ByValue objects. ( my reference objects ) Cheers, Mikael

It’s very scary if this new compile optimization cangenerate bugs like this. Because that means it can happen on all you code. Hopef3 comes soon J

Thanks Jim I get the crash as well for my 10.0f2 version, It’sstrange that basic functions like this get changed from one version to another. I hope they add this VI to their test suite before every released from now on. Cheers, Mikael

I got this message: Is it the same as this one?

It's the X-Control's INIT function that opens the VI and runs it. //Mikael

Hi Bjarne You've already got the lock sorted out now, but I was just wondering why you prefix all methods in the class the the class name? Any reason? Cheers, Mikael

Drag the image to your block diagram, (if using 2010).

Yes, it should be part of LV 6.1 and up, but might not be there is it's a Basic version. This is the Kernel Endevo's first version of Reference GOOP used. Cheers, Mikael

Make sure you don't have any other unclosed refs from that VI before you close the VI Ref.

Do you know that you can do this: Cheers, Mikael