crelf

All I know is:

Copy, paste, resize...

Copy, paste, resize...

Copy, paste, resize...

Sounds like a system that requires constant maintanence! :laugh:

Hi All,

I'm the author of "Image Acquisition and Processing with LabVIEW" - a hardback book that steps you through Vision, from camera, lens and light selection, to machine vision and processing technques with LabVIEW.

My book recently received a very poor rating by a customer on amazon.com. The reader thought that I'd missed the mark - some of my book was too simple and the rest was too complex, so there was no value in it for her at all. This has come as a bit of a surprise to me as I'd put a lot of work into the book in trying to balance the topics I selected and they way they were presented, and I was wondering if others shared her view? Up until now, I hadn't seriously entertained writing a second edition, but this has sparked my interest. Sure, I'd like to include a bunch of new stuff in a second edition, but I'd sure not want to write it in the same way if the amazon.com's customer's view was widely held by may others in the community.

To that end, if you've read my book, I'd really apprecaite it if you could log on to amazon.com and leave your comments there - good or bad. This will serve two purposes: it will give me a more of a balanaced idea of where I went wrong, and also give potential customers a larger reader sample set on which to base their opinions.

I'm not ask you to write a glowing review of my book (unless you want to! ), all I'm asking is that you spend a few minutes putting your thoughts down to enlarge the customer sample set.

Thanks for your time - I really appreciate it.

cheers,

Christopher G. Relf

I'd sure hate to see what's in the false cases, and how you managed to fit it all into that little area. Come to think of it, this would be better handled in OO...

FillWhole?

Oh very droll...

Both your example and some of the ones above use enums as the input to the CASE in the SM. I prefer text input to the CASE selector as it allows you to parse strings, scripts, etc and use some of that directly.

I completely concur - just remeber that case structure selectors are case sensitive by default (you can turn that off with a right click selection), and make sure you have a separate "Default" case with a "Syntax Error" popup for speeling mistkaes you make when coding

Perhaps we should have a year end "best of poetic posts" topic for each year and include a subcategory of HH posts and pithy replies.

I'd love to see that - we could hand out awards (free LAVA t-shirts) at the NI-Week LAVA / OpenG BBQ every year

I already searched Add/Remove program

LabVIEW 7.1 isn't listed directly under Add/Remove programs, it's under a category called "National Instruments Software" - have a look under that.

Since we're chastising, aren't those suggestions identical to mine?

I think identical is probably a bit of a stretch, but I have edited my previous post accorfingly

Hey Didier - a great big CONGRATULATIONS! :beer:

Please ignore this topic - it is a crosspost from here.

I wait a solution as soon as posible! Thank you!

Step 1: don't crosspost (post your question in more than one forum)

Step 2: upload an example VI showing us your problem - that makes it much easier for us to give you intellegent suggestions.

I know that, but...

Ahhh - good point. Consider me appropriately chastized :headbang:

Looks like Guillaume Lessard's yen's suggestions are going to be your best way out.

Of course in LV7 you don't have 64-bit integers for free, but you can either do them yourself with two 32-bit integers or use doubles; their mantissa has 53 bits of precision so you won't lose count for a good long time.

They are both valid options, but personally I'd go for the 2 x 32bit integers - it's a more elegant solution.

I see by using the Profiler that Config Data Registry.vi just continues to grow and grow.

Even though you're handling files appropriately, the memory used by the VI can be related to other tings - are you appending data to a FP control or shift register? Can you post your code so we can have a look at it?

I can not comment on what version of LV.

I tried it on LabVIEW 8 and got the same problem...

Since you don't have 64 bit integers in LV...

C'mon yen - get with the times! (LabVIEW 8 at least)

If anybody is interested. Here is the download link for "LabVIEW 8.20 anniversary edition"

Has anyone downloaded it yet? Is it a beta?

1) So, I either have to buy excel for each of the 7 test stands.

2) Change the user spreadsheet to save in .csv or .txt

3) get LV to open a .xls file in its native format.

Option 1 = lots of $$$

Option 2 = :thumbup: Not difficult

Option 3 = :thumbdown: Not doable as the .xls file format is Microsoft proprietary.

Can i convert the readings into a Extended precision variable?

I don't think convert is quite the right word - but you can add / subtract your i32 input to / from an i64 that you're handling in LabVIEW (I don't know your architecture, but maybe hold the position in a shift register?) Can you post some example code so we can make more informed suggestions?

It also depends on what you mean by commercial - do you mean that a company can't use it internally, or they can't use it in projects that they ultimately sell?

Either way, the software itself can't tell whether the code it's being used inconjunction with is commercial or not, so your easiest way out is a nag screen. That will stop anyone from selling your code as a component of their own...

the first waveform I am acquiring and the other one I am reading from file...

Can you pls upload a copy of the data file?

http://forums.lavag.org/index.php?showtopi...amp;#entry14161

As I said, the only place you can get answers (not rumours or conjecture) for either of these questions is NI directly.

...I was wondering if they would release a new version with fixes and patches ... and maybe having a release date would be great too.

The only place you can get answers for either of these questions is NI directly - have a chat to your local FSE.

Icons in LV, when properly used, are part of the documentation.

I agree whole-heartedly. I still don't understand when people just use the VI's name in the icon - to me, that's just plain stoopid - the VI's already got a name! That said, when doing OO, I still like to have the class name at the top of the icon and the method at the bottom, and a pretty picture in the middle. It's also good to differentiate classes by colour:

Ah - I understand now. I just downloaded your example and get the same problem (recompiling doesn't work). I get in contact with NI support if I were you - looks like a real bug...