ShaunR

I can see continuous fluctation when at position zero from -0.02 to 0.02. If I plot this voltage this draws into a sine wave. Consequently my controller output is a continous unstable signal.

What frequency is the sine wave. 50Hz? What is the +-0,02 in comparison to the range (+-5v sensor?)

Does your PID controller implementation have a dead band?

Luckily, we don't have to guess. It's called math. :-)

A guesstimate is not a guess. It is an estimate without having all the facts. As Order Of Growth is a simplified relational analysis and usually only denotes a upper bound; it is a "guesstimate" however much maths you put around it. It is a very crude way of describing processes.

Algorithms Part 1 began today...

What do you call a programmer that doesn't understand order-of-growth calculations? Hopeless?

Perhaps you are just more use to the older terminology of "guesstimate"

Me was about Labview 2012 f1 Patch.

I do not know so well english language , to explain exactly what I mean.

I thought, that you are intelligent enough to understand what I mean.

It was a "play on words".

Intelligent? Me? Naaah. I write LabVIEW programs. If I was intelligent I'd write Malbolge.

In me it works.

I bet you say that to all the boys

Have you got a CAR number?

No. As Phillip states. It is not a modem and therefore does not use Modem hardware signalling.

Labview 2012 f1 Patch, already is.

http://digital.ni.com/public.nsf/allkb/C43244DFBC6AE9FA86257A440064199F

Not even a week and there's a patch?

Are you trying to open the port on the LabVIEW side twice? You can only open a port once or, more specifically, you can only bind one socket. If you are trying to "multicast" then you must use a multicast address, however, you will still open only one socket.

Use the VISA property node.

It's in my profile.

We have so much code and libraries that we don't upgrade very often. The last upgrade happened when we went from 7.0 to 8.6 in December of 2008.

I try to participate in the betas and keep up on things, but I'm falling behind the times. I did download 2012 today, but won't do much with it until the end of the year. We might start our next project on 2012, the latest TestStand and win7

This is quite common so I wouldn't feel too left behind. Moving to a newer version represents a significant project risk and if/when you upgrade (which should be for a very good reason rather than there is just a new one) it's better to let other people find all the bugs/issues and any work-arounds for them. I'm still on 2009 which is far more stable and performant than than 8.6 (and, anecdotally/arguably, more performant than everything to date) and I'm waiting for a feature list or bug list that warrants an upgrade.

However. Back to toolbars. The change was made in 2011. 2009 and 2010 both have the (much better IMHO) standard 3D button bar.

Woah. Cats resurfaced. That's worth a "like" in itself

Unbundle the error cluster after the Error Message Dialogue VI and "OR" it with the stop button to terminate the loop. The loop will then stop if there is an error or if you press the stop button.

So. Whats the verdict?. Likey, likey?

Just got LabVIEW installed but had to kill NI Error Reporting (NIER) using task manager. The LabVIEW install popped up a 1303 error.

(null)

Why Do I Get Windows Error 1303 When Installing NI Software?

Hi ShaunR. Is this figure of 8 independent of CPU core count (ie. in my case I have 8 logical cores)? The reason I ask is that the threadconfig.vi in the sysinfo.llb allows me to specify up to 20 threads in each combination of execution system and priority. I might be understanding this wrong, maybe this ability in threadconfig.vi is misleading? On my machine all the table entries were set to 8 initially as you suggested.

Or is this a case of a single thread, per execution system, per priority per CPU core (hence the default of 8 in the tables on my machine)?

Hmmm. In 2009 and 2010 it was max 8 per exec, per priority irrespective of the number of cores. Max 200+1 in total.

I've just looked in 2011 (I rarely use it) and indeed you seem to be right; you can set 20. However, it can be set to 20 on both my Quad core (8) and my dual core (4) so I think they just bumped up the limit rather than made it scalable in accordance with number of cores.

Thanks everyone for your posts.

The solution I have run with is separating the tasks out into each execution system. In particular, I placed only the tasks with .net calls into the "Other 2" execution system and specified, by the configuration ini file, for 20 threads at Normal priority (there are 20 maximum simultaneous calls to the dll) for this ES. I added this as a Post-build action in the executable build configuration to automate that process.

This has fractionally increased CPU loading by a few percent as expected but also allowed all the remaining tasks to operate within their required timings (ie. now properly "insulated" from the dll calls). So it would appear the .net dll calls were consuming all available threads, as suggested by Mark Smith.

I'll dig deeper into seeing if I can improve the performance any further (ie. via tweaking VI priorities) but this helps me out for now, thanks all for your help!

The maximum is 8 per execution system, per priority. You can get your twenty by spreading them over 3 execution systems (for normal priority)

+1 for JSON.(strings)

Strict typing is for wimps.

Some pragmatic info here.

This is a bit outdated but still a good base reference.

You would still use a FG as a cache, right? Rather than query every time you need a setting?

Nope. Why do you need a cache for prefs? (let the OS do that) Kind of defeats the object.

After I posted, this route crossed my mind, just wasn't sure if there was a better way. Do you use this often for ini files and such?

No. I use a database (SQLite) nowadays for preferences.

You can still use a Get method. Just you have to make it a singleton (which is the default for a VI, but you have to program it for classes-e.g use a DVR).