ShaunR

Thanks guys. No wish list? Gripes? Suggestions?

Anyone actually using this? (apart from me ) I've another release almost ready so if you want any additional features / changes.... now is the time to mention it (no promises ).

Posting the command reference manual would be helpful

If the above suggestions don't work. then try forcing the libs into the exe:

Very elegant

MAX uses NI-IMAQdx so you should be using the IMAQdx functions instead of the USB driver.llb functions (see the link I posted earlier). These are notoriously problematic. Make sure they are uninstalled / removed from your system. Also, make sure you have the latest IMAQdx drivers installed.

Interpolation (As the name suggests) is for creating intermediate values where none exist. I don't think this is what you are trying to do (maybe wrong ). From the VI implementation and description it looks like you are trying to find a motor position that is a close match to the desired frequency since the motor position cannot be fractions (discrete steps). I.e you have a look-up table. So based on that I have modified your VI to do this.

Post them and we'll take a look

Thanks Yair. Unfortunately uses OGlibs so cannot try it. It talks about inheriting "daughters'" properties which might be the reverse of what I was seeking.But should we really use a tool to do this? I did briefly look at scripting to generate the VIs for the properties and methods, but couldn't get a list of them from the original control. But still. That's a lot of VIs to do what the control already does

Indeed. My gripes are a bit more fundamental than that though. All I wanted to do was add a "Clear" method,alternating row colours and make it accept arrays of strings instead of using the "Item Strings" property to a multicolumn list box. But the amount of effort in re-implementing all the standard stuff just doesn't make it worth it. Only took me 15 minutes to create the control and make the changes I wanted, then it looked like another 2 days to re-implement the standard stuff.

There is not supposed to be a wait. The read function will wait until it either has the number of elements requested, or there is a time-out. In this respect you change the loop execution time by reading more samples. If you are pegging the CPU then increase the number of samples (say to 15000) and increase your PCs buffer appropriately (I usually use 2x te FPGA size). 5000 data points was an arbitrary choice to give a couple of ms between iterations but if the PC is is still struggling (i.e there is some left over in the buffer at the end of every read) then it may not be able to keep up still when other stuff is happening.

Spooky I was playing with Xconrols this weekend too (not fr buffer stuff though). I shelved it in the end since I was really annoyed that a XControl doesn't inherit all the properties and methods of the base data type meaning you have to re-implement all the built in stuff.

Not really. The PowerMeter class has no dependencies its just a container used to manipulate the object you pass in to give the results context and meaning. PowerSensor Could Just as easily be an RTDSensor. You put it more eloquently than I in your previous paragraphs but basically we are thinking along the same lines. LVOOP! My other language is DelphiHorses for courses.

The "Othello" contribution in the "Examples Competition" uses property nodes. Othello

In other words free resource

I too was surprised at a lot of the finalists. Considering the purpose was to tender "Example" code, I think many of them are way too complicated and don't really demonstrate anything that isn't already there. I was expecting small simple, easy to understand demos rather than complex (1-2 MB) applications (although the games one might be the exception). Perhaps I misunderstood the purpose .

Then its your FPGA FIFO that is probably filling up. Try this for the read loop.

Why go for one OR the other. Surely a "PowerMeter" contains a collection of "PowerSensors". (amongst other things ) So my "PowerMeter.GetPowerFromSensor(1..n)" would actually be "PowerMeter.GetPowerFromSensor(PowerSensor)". I would also say you would need a lot of knowledge about the power meter since you probably won't be able to talk to any sensors and it will be the device that contains range, scaling, math functions and probably calibration data (unless the cal is on-board the sensor). So you will need things like PowerMeter.SetRange, PowerMeter.SetSamples, PowerMeter.Calibrate etc, etc. So from my viewpoint, the sensor is just a value. The PowerMeter makes that value meaningful. And PowerMeter, Ammeter, Voltmeter are semantics.

What's the FIFO depth? You need to set it both for the FPGA (when you create it) AND the host (default for the host is 10,000 if memory serves me correctly.) You'll use up the 10,000 n 40ms which can easily happen if you task switch in windows.

Yup. Jacks fault

Hyperbole

Nope. they live in the same dimension only aren't married

If you get rid of the imaqUSB.llb (usb is has been supported in MAX since V2009) you can just include the MAX configuration in the installer. USB Camera Error

Yes it does. It's just not what you think