ShaunR

If you right click on the project name in the project tree, there is an option to "Find Items With No Callers".

I didn't say it was good. Just that I agree

I'm with Gary on this one. Another aspect is that not everyone "gets" OOP. There are many coders that use OOP capable languages that never write a bit of OOP in their entire career. Perhaps a better approach might be to start them on normal LV with the advantages of all the existing examples and training resources and filter out those that just don't have the head for it, rather than assume that everyone can and will learn.

Another opening soon for Vaguely Interesting Engineering. CVs to Crelf

Theres a system? I just randomly click click on posts because I like "green".

I know he was But I was kind a hoping he would feel guilty and go back and click on a few posts

To me, its a bit like Codegear selling you Delphi and expecting you to do bits in Visual Basic. People like LV because it is not C. What they could have done is run a linux kernel on the ARM and then use the linux RTE or ported their RTOS which currently supports intel and Power PC. There arn't that many platforms out there that they support so I think for that price they could have made a bit more of an effort.

OK. I've looked now Its a little bit more complicated than that, since the frame names has to match the number of cases. If you just wire it to an array of strings, you will get an error and only 2 cases will have the names. You have to create the correct number of cases (array length - 2) using the "add frame" invoke node then wire your string array to it.

Its a Japanese advert Thats a bit rich since I post an example and get zero points. You convert them to 8.x and get three

If you use an enum (your example uses a ring) then when you right click on the case there is a menu option to "Add Case For Every Value". I havn't looked, but there is probably a property or invoke node that enables you to do this in scripting.

Well. the board had a 2 line LCD display so it must have been tier 1. It did work "out of the box"....... with the demos. And as long as you changed only the data to the front panels it was fine. But when I said that our device was to have a 12 line matrix display and how could I mod the "display" vi to do that, he said I'd have to write my own display driver in C. He did demonstrate compiling, downloading and live debugging with a demo he had prepared. But when I started asking him to modify it, he changed some settings and then it would pop-up with a window full of c code and he would twiddle bits. I pushed him on it and asked why he wasn't changing the vis. Thats when I looked inside and found....well nothing, apart from the controls and indicators. The vis seemed to be purely placeholders for the generator.

Another tip. If you store the folders/files with the names in a "year-month-day" format (e.g 2008-10-02), then when you browse the folders they will be sorted chronologically. If you do it day-month-year they will be all over the place.

It was an NI rep and the toolkit was "The Embedded Module for ARM Microcontrollers" This is what it says in the sales blarb:

Where's my point then?

Except poor ol' Hooovahhs

The main difference between them is the speed. What devices are you intending to talk to?

I was interested in the ARM deveopment toolkit and asked the sales rep to come in, demo it and leave it with me for a couple of weeks. Long story short, I didn't bother with the demo kit and he left with it. The toolkit I saw was basically a C generator. there were limited vis that enable you to do certain things, but you cannot modify them. If you look inside theres nothing in them. When I asked (for example) "this matrix display demo, how do I modify it ?" He said you generate the c code and modify the c code to whatever you want It looked to me like a C template generator that you then go into and modify in the C environment of your choice. You might as well either write in in C in the first place or give it to a C coder since they are 10-a-penny. The sales guy couldn't really come up with a good reason for me to spend £3K on a toolkit when we've got ten C programmers on the payroll.

As its your first time, go with what you know! http://www.ni.com/can/

Use the express vi "Scaling and Mapping" in the "Signal Operation" palett and choose "interpolated". You can then define your table and use the vi to convert your readings fr any voltage.

I think it was dead anyway Indeed. I believe LV OOP was invented to give C++ programmers a warm fuzzy feeling and entice them to use Labview. The advantage for beginners that Labview brings is that they are able think in a sequential manner to start with and lay down code in the same order as their thought process when analysing problems. This means that they learn the environment a capabilities of LV quickly whilst still producing tangible results (i.e code that works) without being encumbered by how it works. Once they get used to using LV as a symbolic "scratchpad", they quickly move on to more complex subjects as a natural progression. They also don't have to worry about pointers, memory management and all the other obnoxious stuff that makes other languages so flexible so their time is spent on the problem rather than managing code. However, if you sit them down and explain that you have to spend 3 weeks writing code with (from their point of view) no discernible benefit apart from being able to make other code work. They quickly get confused, frustrated and bored. If they can sit down and in 10 minutes turn a light on and off, or make the computer beep every time they walk past it.....then you have an audience This is true. But when it doesn't give you what you were expecting, then you do! Just because a program contains objects (C++ .net or anything) doesn't mean it is an object orientated program. Non OOP programmers view these objects as "functions" to extract whatever data they need. They (I? ) mainly view them as a container with specialised features not dissimilar to a vi with a case statement that enables selection of a series of sub vis. This view is far less abstract and easier to digest for virgin programmers.

That's where your problem lies. I find it takes 1-2 months for a non-programmer that is eager to learn. You spend 6 months listening to text programmers whining about how they used to do it.

Oooooh.Managed to save something in 8.0

Your a sweety

A while ago I was faffing around with mobile phones and knocked this up. Should be a good guide to what you want to do.

1.5 MB/s is a bit of an odd number. 10BaseT is 1.25 MB/s and 100 BaseT is 12.5. If you have been using it for a while and its stopped working. then it probably has developed a fault and just needs replacing. (Just though I'd clarify that since it was not clear). If you quickly tested but found it unreliable over a period. Then there are a couple of things you can try (I presume you've eliminated the usual stuff like dodgy wires and poor connections). Some devices only support half duplex and can get confused by the probing if set in auto, or can succeed in full auto due to response times but fall over when the inevitable contention occurs. You can try explicitly setting the PCs network to "Half Duplex" and see if that helps. If your device supports wake up on lan. It could be going to sleep. To wake it up, you have to send a "magic packet" your documentation may tell you more. What is the model/manufacturer of the device?