Jump to content

orko

Members
  • Posts

    576
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by orko

  1. QUOTE (TobyD @ Apr 4 2008, 12:34 PM)

    I've been wondering what "mde" means for a full day now. All I could come up with after googling it was Mucinous Ductal Ectasia. I can't make that make sense in the context of the post...any ideas?

    My suspicion was it was some equivelant to "bump", since there wasn't a response yet. Either that or More Draft -- Edelweiss!

  2. By the look of the source you provided, it looks like there is a cookie being stored when you log on successfully (you can see the error javascript source setting this cookie's string to "LOGIN_LEVEL=0; path = / " on failure ).

    This might explain why the first attempt succeeds and the second one fails -- if there is a session cookie set up to store some sort of connection/session ID and it doesn't match when sent to the second unit you are testing.

    I'm unclear on how LabVIEW (datasocket or VI server) stores cookie related information in it's session cache. But if my instincts are correct in Windows, I would assume it uses the same mechanisms that Internet Explorer uses. That is if LV7.x supported session cookies at all...

    To test this, before running the second unit's test try clearing out Internet Explorer's cache and cookie history. In fact it may be a good idea to clear them out first before running the first test so you can see if there is a file being stored in your cookies for the IP you are using. If there isn't a persistent cookie file being stored (and I'm thinking there probably isn't), then this is a session based cookie and you won't be able to just clear it out every time manually (because the only way I could think to clear a session cookie would be to close LabVIEW like you are doing).

    Another option is to just re-request the page on this failure? Since the error page is "logging you out" via Javascript by clearing this cookie's content, wouldn't a simple retry work just like the login to the first unit? :)

    And yet another option is to disable cookies altogether in the security settings of your OS and see if there is a failback method that the unit uses for login...

    I hate cookies... :rolleyes:

  3. To add another piece of old documentation to the mix, take a look at this under "SubVI Overhead":

    QUOTE

    When you call a subVI, there is a certain amount of overhead associated with the call. This overhead is fairly small (on

    the order of tens of microseconds), especially in comparison to I/O overhead and display overhead, which can range

    from milliseconds to tens of milliseconds.

    However, this overhead can add up in some cases. For example, if you call a subVI 10,000 times in a loop, this overhead

    might take up a significant amount of time. In this case, you might want to consider whether the loop can be embedded

    in the subVI.

    Another option is to turn certain subVIs into subroutines (using the VI Setup Priority item). When a VI is marked as

    a subroutine, the execution system minimizes the overhead to call a subVI. There are a few trade-offs, however.

    Subroutines cannot display front panel data (LabVIEW does not copy data from or to the front panel controls of

    subroutines), they cannot contain timing or dialog box functions, and they do not multitask with other VIs. Subroutines

    are short, frequently executed tasks and are generally most appropriate when used with VIs that do not require user

    interaction.

  4. QUOTE (PaulG. @ Mar 31 2008, 06:34 AM)

    As it turns out a lot of folks turned every light in their houses ON for an hour in protest of the hypocrisy.

    I'll call your hypocrisy and raise you an act of stupidity...

  5. QUOTE (crelf @ Mar 30 2008, 08:16 AM)

    So, if you're still using a CRT monitor, tell your boss that switching to a new LCD will help save the planet :D

    I've asked for two, since that would be saving two planets, right?

  6. So I have to ask... if it isn't needed after activation, then why is it running as a service? Is there any stuff that we should be aware of that it does in the "background" before I turn it off on all my dev boxes (I can't stand processes that hang around for no reason...)?

  7. Bruce,

    I had problems with a project that I upgraded from 8.2 to 8.5. Initially it worked great, but then I opened up a typedef cluster to edit it and LabVIEW crashed. Subsequent tries to open the VI that contained the typedef hung LabVIEW. I cannot remember if I had problems opening up the project itself, but I feel your pain.

    In my case, the problem turned out to not be in the control I was editing at all. It turned out that there was an element of that cluster that linked to another cluster that had a typedefed reference to a graph that was causing the issue. (yeah...)

    The way I solved this was to create a folder outside of the search path, and do a kind of binary search. I took half of my folders in the project directory and moved them away, then tried to open the VI. If it crashed immediately, I restored the folders and took the other half away. I did this until I was down to a few Typedefs, and eventually found the one that was choking LabVIEW. Recreating this control and re-linking my VI's solved the crashes.

    With this and another example that one of my colleagues showed me, I am almost 100% convinced that older 8.x versions sometimes let linking errors slip by, and LV8.5 is better at preventing this...if you start with 8.5. Converting over to 8.5 can be painful if you have linking errors already existing in an older version of 8.x.

    This may or may not help, it's just based on my observations so far. Good luck!

  8. Just in case you somehow missed Google this morning

    post-3266-1206799154.png?width=400

    This is to promote

    , which I think is a great idea. What does it hurt to turn your lights out for 1hr? I'm anxious to see how successful they will be this year (even though I think it will be very hard to measure accurately).
  9. QUOTE (Jim Kring @ Mar 26 2008, 08:12 AM)

    Hankey San

    Yeah, his "Weeeeee!" cry in the video is burned into my brain somehow... that and the "What time is it when..." questions.

    This morning I heard "My MAX config is messed up" from across the room. Sure enough, immediately in my head...."What time is it when your MAX is messed up...?"

    Ma, Ma, MAX man!

    Please, someone post something catchy so I can dump this. Oh man...even that sounded wrong. :headbang:

×
×
  • Create New...

Important Information

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