LAVA 1.0 Content

I should probably discuss it with Steve and Heiko before posting anything, but I'm sure this could be interesting. Especially in combination with Local User Group meetings.

I should probably discuss it with Steve and Heiko before posting anything, but I'm sure this could be interesting. Especially in combination with Local User Group meetings.

You can't have one of these without food!! Went to an NI early morning event... No food! Everybody talked about that fact. No one remembered the discussion, just that there was no food. Depending on attendance, we'll see what will be available. Although Gabrielle Pizza or Colonade Pizza would be good! Thanks Heiko for posting it!

You can't have one of these without food!! Went to an NI early morning event... No food! Everybody talked about that fact. No one remembered the discussion, just that there was no food. Depending on attendance, we'll see what will be available. Although Gabrielle Pizza or Colonade Pizza would be good! Thanks Heiko for posting it!

Color ramping between two colors can be accomplished by interpolating the RGB values seperately and then recombining the components (See below). Ben

Color ramping between two colors can be accomplished by interpolating the RGB values seperately and then recombining the components (See below). Ben

Are you asking how to create a dialog that looks and functions like the color chooser for a graph, like the screen capture below?

Are you asking how to create a dialog that looks and functions like the color chooser for a graph, like the screen capture below?

QUOTE(bono02 @ Nov 20 2007, 11:38 AM) This depends on your application, I can not say if 3600 are just fine or not... The motion controller (MC) makes a 4 x of your encoder pulses. (If you have a A and B signal) That mean if you have 3600 counts per revolution, the MC will use 14'400 steps per revolution... I use encoders from 500 to 10'000 pulses per revolution... So you have to calculate the resolution you would like to have and then you can choose the right encoder. We usually use an absolute and an incremental encoder for all axes, since we then don't have to make reference moves...

QUOTE(Aitor Solar @ Nov 15 2007, 10:36 AM) Most property / involke node work with the English names, so I have not yet started to translate all the txt files... I probably "only" have to figure out the german names of the property / involke node which cause an error...

QUOTE(tcplomp @ Nov 19 2007, 09:50 AM) Hi Ton, Let me get something straight here. I have NO idea what I am talking about. On my machine, under LV 8.5, the SDE appears under the add-ons. http://lavag.org/old_files/monthly_11_2007/post-29-1195485564.png' target="_blank"> I do not recall installing it for LV 8.5. I did install it under LV 8.5 Beta (It installed under the State Chart Beta install) but I had deleted that. I can't explain why I see the SDE in palettes. Ben

QUOTE(tcplomp @ Nov 19 2007, 09:00 AM) Check under you LV 8.5 add-ons. It appears to now be a freebie. Unfortunately no bugs are getting fixed for the freebie. Ben

I'm Websensed at work, so I don't get to enjoy LAVA posts with videos or audio all that much. I took some time Friday night to watch the Benny LAVA and Girly Maaan videos from home. OMG this stuff is too funny! I nearly wet myself! My wife thinks these are just wierd, but I found myself humming Benny LAVA and Girly Maaan while cleaning the leaves from my yard this weekend. Thanks (I think )

Scratch in the record of my brain. After 24 hours these videos are still running in my head. Can anyone offer any advice on a good shock therapist that works cheap? Hmm.... Maybe I can can wire up an defribulator to a tin foil helmet... "Benny LAVA ..... Girly man...." Ben

QUOTE(Justin Goeres @ Nov 16 2007, 09:22 AM) He first revealed Himself to LAVA on April 27, 2006 http://forums.lavag.org/Jesus-t3067.html&st=15&p=12032#entry12032' target="_blank">here...

QUOTE(Usman Shafiq @ Nov 15 2007, 05:35 AM) REPORTED AS SPAM

QUOTE(Norm Kirchner @ Nov 13 2007, 04:29 PM) Thank you Norm for this link. I am going to use it on the NI Forum to show how Lithium's updates are handled. Ben

Side Note: I will attempt to place the control for which an event is configured in the event case itself. This alllows me to double click on the control from the FP and quickly find the event for that control. Ben

QUOTE(Aristos Queue @ Nov 14 2007, 08:53 PM) This thrad is cross posted on the NI forums and can be found here. Another way to increase the complexity of reverse engineering code would involve including a lot of flse leads. From my limited reverse engineering experience (no, not LV. I used to do crash dump analysis which was all reverse engineering with hardware failures thrown just to spice it up) you want to start by finding some reference point in the code that can be used to start walking through the code. This could be machine code that has a valid form of a loop, code loading, etc. To make it more difficult you could include a lot of false leads. One method of doing this involves imbedding bogus VIs within your VIs. In the "Obfuse Code" thread I presented a VI that had another VI imbeded in it as a constant on the diagram. The VI, when run, wrote the data to file and then opened and ran the VI using VI server. So to reverse engineer that VI you had to distinguish between the code of the top-level VI and the VI embedded there in. So if you included in your VI the raw data of 99 bogus VIs (that almost implemented your algorithm but all had fundamental flaws) then the reverse engineering would have to pick out the "1-out-of-100" to figure out what your code was doing. You could even through some encrytion into the data saved (in the block diagram) to add another hurdle they have to cross before they even get to the 1 in 100 chance. Security in general I used to work as a security consultant to the Federal Reserve Bank. The rule of thumb was "Make it ten times more expensive to break in than what was stored in the vault." So if your code is worth $100K then make it cost $1M to reverse engineer. It also seems that a conversation with a lawyer ahead of times. It seems with the proper EULA the law suit should be stream lined greatly. Ben

I think FSM would make a great LAVA mascot; I also like the jolly pirate fish

QUOTE(Aitor Solar @ Nov 13 2007, 01:26 PM) My Picture looks almost the same... VI Server is still VI Server... EDIT: If I right click on a property node and klick on "select class" then Vi Server is written VI-Server... So I entered VI-Server istead of VI Server... This way, a lot of property/involke node can created using the SWB. However I still get errors on some property/involke nodes: Application:Command Line Arguments Application:Debug Name etc...

Thank you guys for your answers This week i'm home with my laptop from the company, so there is no ctrl key on the right hand side, but that's a good idea I'll get a usb keyboard ! I didn't know about the sticky key option, I'll try that. Thanks again for your help EDIT : QUOTE(TobyD @ Nov 13 2007, 09:58 PM) WOW !! The sticky key option is made for those who only have one hand ! It's what I need !!

I broke my left arm at a rugby game and my left shoulder is also really painfull at the moment so if anyone has a trick not to have to press at the same time "ctrl + alt + delete" because with just one hand I can't do it ! Great idea Microsoft ! PS : posted form a mac

QUOTE(Neville D @ Nov 13 2007, 12:56 PM) Thank you for the update. You may know this already but a timed loop will let you spec which CPU the code runs in. The timed loop does not have to iterate, it can just hold the code you want to control whcih CPU it execute on (at least that is how it will work on LV-RT). This may help "hedge your bets" with keeping up on the UDP incoming. But short of trying to implement TCP/IP over UDP, there will always be a potential for missed packets. If you get to a point were it looks like even the Gigabit E-net can't transport data fast enough, then you may want to look at SCRAMNet by Curtiss-Wright. It screams (both in performance and cost, ouch). Ben

You might want to consider tinkering under the hood a bit and try modifying the Nagle example. By modifying the TCP socket's buffer size, you can let the OS buffer more and prevent the transport protocol from blocking. I did this to increase the default buffer size for UDP sockets (8192 bytes) and it worked out well. For all available options for tuning sockets under Windows, Google "winsock2.h".