Jump to content

LAVA 1.0 Content

Members
  • Posts

    2,739
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by LAVA 1.0 Content

  1. QUOTE(bono02 @ Nov 20 2007, 11:38 AM)

    I am thinking of buying incremental, with 3600 resolution, open collector type. I read that the motion

    controller can distinguish a signal with 100ns width. What do you think about it, is it good enough?

    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...

  2. QUOTE(Aitor Solar @ Nov 15 2007, 10:36 AM)

    Error 1077 is usually associated to a wrong property name. Are you sure all the German names you put are correct?

    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...

  3. QUOTE(tcplomp @ Nov 19 2007, 09:00 AM)

    I noticed recently that the latest SSP release (august 2007) that came with LV 8.5 didn't cary the State Diagram Editor on the toolkit CD.

    I have a feeling this has to do with the Statechart Module. I contacted to my local NI rep and he wasn't sure about the why of the removal.

    Does anybody have an opinion of this silence kill of the SDE?

    Ton

    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

  4. 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 :blink: )

  5. 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

  6. 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

  7. QUOTE(Aitor Solar @ Nov 13 2007, 01:26 PM)

    My Picture looks almost the same...

    VI Server is still VI Server...

    post-1396-1195039831.jpg?width=400

    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...

    post-1396-1195041534.jpg?width=400

  8. 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)

    Press the "Shift" key 5 times in a row. This turns on "Sticky Keys" (You can also turn this feature on from the Accessibility Options in control panel). You can then press CTRL, ALT, DEL in sequential order, without having to press them all at the same time.

    WOW !!

    The sticky key option is made for those who only have one hand ! It's what I need !!

  9. QUOTE(Neville D @ Nov 13 2007, 12:56 PM)

    Hi Ned,

    Our system consists of a VME computer (non-LV) that transmits line scan data to a windows PC running LabVIEW and Vision. The image data is about 500k, and once processed by the LV PC, the returned results are about 1KB or so.

    We tried UDP, and it definitely is a LOT faster.. a few ms to transfer the data. But on the windows (receive) side, we seem to be missing packets inspite of having a parallel loop that simply reads the data and buffers to an Img buffer.

    To the others that have replied with helpful comments:

    Ben, and JFM,

    I am in the process of experimenting with Nagle, and it might help on the transmit side (windows->VME) where the data is quite small and it takes about 10ms to just open a socket. Disabling Nagle on the VME didn't make any difference.

    I will try experimenting with different packet sizes on the VME side.

    LVPunk,

    I have also tried increasing UDP packet size to 4k and it seems to work OK.

    I have just got a quad-core machine and have upgraded to Gig-E. Preliminary tests are encouraging. The Gig-E with even a dual core allows us to use UDP without missing packets.

    Also, going from 100MB/s to Gig-E seems to offer roughly twice the performance.

    Will post more info for reference, later on.

    Many thanks to all of you!

    Neville.

    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

  10. 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".

    • Like 1
  11. QUOTE(Michael_Aivaliotis @ Nov 12 2007, 11:29 PM)

    ...

    Can someone explain the difference between State Diagram and State machine?

    ...

    I'll try and wait for correction*.

    A State Machine is a programing construct that implements a state diagram.

    A State Diagram is a drawing that illustrates the various states a process can be in and the conditions under which it will transition from one state to another. I have also heard them called "State Transition Diagrams.

    This is illustrated in the State Diagram Editor. With the SDE you edit the SD and LV re-codes the state machine.

    Ben

    * Don't give up easy. ;)

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.