jgcode

List of bug fixes in LV 2011

It's cool to see issues fixed that: I've posted (got CAR) or have affected me. One of the more interesting fixes for me is:

214860 — Build path too long when building application

This has been a problem since introducing the new exe structure in LV2009 (which was an awesome new feature). I look forward to looking at this in detail.

1. Your llb file names are prepended with an underscore. Do you do that because of potential naming conflicts between the llb and the class/library name?

Nah, I just wanted to show an example of Library with Classes distributed as llb's.

It was on me at the time, but that example is for reuse, hence the namespacing.

I have played with both, namespacing and not for Plugin Classes, I don't think it matters too much.

2. I assume you have to create a unique source distribution for each llb, and the llbs have to be built before you build the application. Do you script your build process to control the build order?

Well if they are truly Plugins then they do not have to be part of the application build process, only the 'interface' Class does.

However, it could be (both part of, and scripted) - it would depend on the application.

I don't have to create a unique source distribution for each llb, I can do multiple llb's in one source distribution.

3. Why do you have a directory dedicated to Yair?

Very clever

If you have been reading about the new features of LabVIEW 2011 you may have stumbled across this one:

NI LabVIEW 2011 FPGA Development Environment Improves Performance by 5X.

If you have a really keen eye, you might make out my LabIVEW style in the videos

I like to use a subVI layout similar to this:

What happened was that a NI group manger contacted me early this year.

It seems a video I posted on LAVA complaining of highlighting a slow FPGA development environment went viral inside NI:

...Well believe it or not, your little video catalyzed our FPGA team to do some serious banging on our I/O Nodes and wiring this release cycle, and your video has become kind of famous (at NI at least). I was hoping to get your code (not to share of course) but instead to do a side by side compare for our developers to show them that they fixed your issue...

Either way, just thought you'd like to know that we're trying to fix it....

<object id="scPlayer" width="793" height="549"> <param name="movie" value="http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/jingswfplayer.swf">'>http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/jingswfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/FirstFrame.jpg&containerwidth=793&containerheight=549&content=http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/FPGA%20is%20slow.swf"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/">'>http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/"> <embed src="http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/jingswfplayer.swf" quality="high" bgcolor="#FFFFFF" width="793" height="549" type="application/x-shockwave-flash" allowscriptaccess="always" flashvars="thumb=http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/FirstFrame.jpg&containerwidth=793&containerheight=549&content=http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/FPGA%20is%20slow.swf" allowfullscreen="true" base="http://content.screencast.com/users/jgcode/folders/LabVIEW/media/c0ec32fc-9d1f-4c99-bc81-0b0e3c3fdd66/" scale="showall"> </object>

Yes, that is my code in the videos!! - The performance increases look insane and I can't wait to try out FPGA 2011.

I am really excited that NI listens to the LabVIEW Community, and its great to have them hanging out here on LAVA - even if they are not participating in discussion they are obviously following them!

I basically got a feature request implemented and I didn't even have to post it on the Idea Exchange - thank you PJ and NI

Cheers

-JG

Is pleased to donated 2 Ipod Shuffles to the 2011 LAVA/OpenG NI-Week Bar-B-Q.

I won't be at the NI Week and therefore the BBQ this year. Which is probably a good thing as last year I won my own prize, then had to return it... Mad props to Christopher Relf for helping me out - someone buy that man a beer (or three).

I think the stability and performance features of LabVIEW 2011 get me most excited

Meaning it's 75 deg and sunny instead of 95 deg and sunny?

Funnily enough, it's raining and wet in the city, but where I am working at the moment it's 80+ deg (if my maths is correct) and yes, sunny

Well, seeing as how Australia is fueled by beer and bikinis, I'd look for the engines in bars and beaches. Best bet is prolly beach bars.

Unfortunately it's winter over here at the moment

Is Australia not like a big cruise ship ?

I will see if I can locate the engines, then set sail for Texas

Coincidently I am looking at your error logger project today, trying to understand it all so I can re-write our debug logging system in a similar vain.

If you have any questions feel free to ping me.

Anyway many congratulations to you jgcode... ...cheers for all the community support you give

Thanks for the kind words.

But so worth it and you could accumulate more frequent flyer miles

It's definitely worth it. I had such s great trip last year. If I could, I would love to go to both events each year!

The LabVIEW Tools Network (where OpenG is listed on ni.com) now has ratings. If you've used OpenG and like (or don't like!) it, you can rate it there...

http://sine.ni.com/n...g/en/nid/209027

I encourage all OpenG users to give their feedback!

Move Australia closer.

Is there any room available south of Texas?

Maybe you could come every year: one year for the CLA Summit and one year for NI Week. It would be better than every other year

Yer, that sounds like a great idea. It's just a long way coming from Australia.

Hi maddogpt.

I would suggest (cross) posting this on the JKI VIPM forum.

Are you going to come to NI Week this year? so we can congratulate you there in person

Unfortunately not this year

But definitely next!!

Woo-hoo to all!

My sentiments exactly. Congrats guys! [:beer]

Congratulations !!!

Thanks guys!

What would happen if (hypothetically) I do?

Have you seen the Simpsons episode with Bill Gates? I am thinking something like that

In my LV application I can see the device id.but I dont know how to proceed further..

I don't have it right of front of me, but you 'should' be able to popup on the io constant and select which class i.e. DO.

Did you check the manual? - DAQmx will definitely work.

The drivers are free and should be included with the device or can be downloaded from NI's website.

I just posted in my NI thread a link to your post. Let's see if we can get someone to revisit this issue, track it down and get it fixed

I reported this bug:

http://forums.ni.com/t5/LabVIEW/Unit-Test-Framework-Crashing-LabVIEW-Project/m-p/1110768

And got CAR 220428 for the icon issue but NI could not replicate the crashing issue when removing a test from the project file. It is the same issue you have? Did anyone get a CAR they can post? This bug is very annoying.

You should check out the latest VI Shots podcast.

Three words: Source Code Control.

Three words: Kill the cat

Good point, I hadn't thought of that. My classes are almost always contained in a library with other classes and I prefer my distribution format is consistent regardless of the content. Distributing an llb when there's no name collisions and a file system directory when there are name collisions kind of rubs me the wrong way. (This is just my personal preference... afaik there's nothing inherently wrong with doing that.)

Come to think of it, I've been assuming it's not possible to split a lvlib or lvclass into multiple llb files. Is that correct?

I also like to use the same as you - Library containing Classes e.g.

But when I distribute it looks like this:

As you can split it all up - I just think of llbs as a folder.

For development I like to set things out pretty much like this:

Where modules (under src) are Libraries, Libraries of Class, or single Classes or traditional modules (e.g. MFVI's) etc...

Curves is the name of an application, each application in the project (only 1 in this case) gets its own directory at this level (i.e. they share Shared VIs, Reuse VIs, and Modules).