Jump to content

ThomasGutzler

Members
  • Posts

    205
  • Joined

  • Last visited

  • Days Won

    23

Posts posted by ThomasGutzler

  1. The ViewPoint TSVN toolkit does not work with the latest 1.9.x version of Tortoise SVN client. I have emailed ViewPoint but have not gotten a reply yet.

     

    Yes, we found they usually lag behind current for a bit. Just adds to the pile of inconveniences leading to uninstall :/

  2. You have Rows, Columns, Pages, Books, Shelves, Bookshelves, Aisles, Libraries, Towns, States, Countries, and Planets.

     

    Wow, where do those come from? My LabVIEW calls your Books vol and the rest is just dimX :(

    Or did you just make that up

    And what comes after Planets? Solar systems? Quandrants? Universes? How much further can we go? :)

    • Like 1
  3. Web interface solutions would be interesting for us if they were multi-session (that is - support many users working on the same system in parallel), and handled multiple VIs/windows elegantly. If there was an out of the box solution for *that*, then we would definitely use it. Basically we would really want the client to be replaced by the web browser...(Controlling single front panels is in the "man look at this sweet thing I can do" category. We have only used such solutions occationally, to control internal test equipment.

     

    In theory my solution should be able to do that. It was certainly designed with that feature in mind - I just haven't tried it yet :)

    As long as the front panel is running somewhere and visible it can be interacted with.

    In fact, my plan was to have a navigation menu inserted into every html page to allow the user to navigate between all available front panels without having to type in a new URL or make an awkward link on the actual front panels. Unfortunately, all that only exists in my head...

    • Like 1
  4. You need to right click on the web service in the project and select start. Doing "publish" will have it run in the application web server context, while "start" runs in the project context (and I think probably doesn't show up in the WIF viewer).

     

    That's right, you shouldn't have to play with the Webserver configuration at all.

    I guess my "How to run it" description wasn't great. I've edited the post and added some screenshots to make it clear.

  5. When you're loading a project that does calls to external libraries, LabVIEW tries to read those libraries on load. If they haven't been installed properly or are distributed incompletely you will get an error if those libraries were built on a C++ version that you don't have the runtime installed for.

    I haven't seen this exact error so I'm not sure if that's what's causing it but there's a chance :)

  6. I'm aware of "the competition" and they all charge a lot. I've looked at

    • LabSocket
    • WebPager (after handing over $2k for the software they charge an additional $100 per hour for tech support. WTF?)
    • WebPanel (similar but dead?)
    • Wezarp (uses VNC)
    • NI's own Web UI Builder (dead, mainly thanks to Silverlight requirement I heard). Is that what you meant, hooovahh?

    VIremote sounds like it's using different technology, since it seems to be limited to apple devices. I hadn't seem that one before.

     

    What I wanted to do is to provide an open-source, low-cost or free tool that allows the developer to achieve similar functionality as the above via a web browser. Get them started in a pain-free way and if they're keen provide the ability to modify to their own needs.

    I'm not a huge web designer myself. Enough to get this demo to work (for me at least) but for the final version I would probably need some input.

     

     

    Pretty neat.  I couldn't actually get it to display live data for some reason.  I tried in the source, and the EXE and when running both only 8080 gave me a static image of the FP, and 8001 was page not available.

     

    There is a weird "bug". When you open the "Show Public URL" dialog the web service seems to freeze until you close that dialog again.

    • Like 2
  7. The way I've seen this done typically is to configure the path in on the diagram, and to use a separate (inlined) VI to store this path.

     

    Having (exhaustively?) tested combinations, I have found this strategy the least of evils. :)

     

    I like that, but it really just redefines the function of my scripting VI to: put the vi that contains the paths for different bitnesses on the BD and wire it up to every CLN (after enabling "specify path on BD").

     

    The idea of a scripting VI to do this automatically is super-neato in theory, but probably not practical further than advancing your own meta-programming ability, simultaneously tempering and battle-hardening your temptation to write/trust code that modifies code you maintain.   :)

     

    I think this is such a simple task that it must be able to get it right enough to be trusted almost blindly. With my original design, you'd get immediate broken arrows for trying to call libraries of the wrong bitness or incorrect path.

    When providing the path via input, those checks don't happen until runtime.

     

    This scripting vi was supposed to save time and keep me sane when I have a library with tens or hundreds of CLNs. I'm quite willing to let a script do the first run and then spend a smallish amount of time to fix up the bugs afterwards - as long as I don't have to repeat the same 4 steps a hundred times.

  8. Before I reinvent the wheel, has anyone done this?
    I'd like a VI that goes through a block diagram of another VI and places conditional disable structures around any call library node, sets the condition to bitness==32 and Default, duplicates the case, sets the condition of the new case to bitness==64 and changes the path of the called library from path/filename.ext to path/filename_64.ext or similar or something that gets passed in as a parameter.

     

    Optionally, there could be a check if a CD structure already exists, if a path is wired to the CLN, what bitness we're currently on (and change above behaviour), etc. etc. but let's start simple :)

  9. I am sharing my implementation of the Tic Tac Toe game.

    Unlike many others available, this one has an intelligent AI, which is trying its best to beat you by running a minimax algorithm to figure out the best move for every turn. Alternatively, you can put it on the dump (random) setting.

     

    I built it on a JKI statemachine and saved as version 2014.

    TicTacToe.zip

    • Like 1
  10. This has got to be a bug.

    As we know, probes inside parallel loops don't work. That's usually indicated by a slightly greyed-out version of the probe ID in the block diagram (1).

    However, if I insert a disable structure inside the for loop, I can suddenly have a working probe again (in the Enabled case)!

    In this picture, probe 3 is a memory I32 probe (old values are shown in the array) and I can actually step through the disabled diagram and get useful readings from the probe.

    post-28303-0-78642000-1440749894.png

    And no, this VI hasn't been flarned :)

    Works in LabVIEW 2014 32 and 64bit.

  11. I've been running Windows 10 insider builds for a while with LabVIEW 2014 and haven't had any problems. I did start with a fresh install, not an upgrade from Windows 7. The only thing I had to fix was the scrolling for my Wireless Desktop 5000 mouse but the Wireless Desktop configuration application lets you select applications for which scrolling doesn't work and somehow makes it work. Neat.

    I don't pin things in the start menu but I find it's too tile-y. Will have to look into that "Start10" thing :)

  12. The Array constant Wired to the XY Graph is not empty.

     

    Craig, unfortunately it's not that easy. That array is empty.

     

    Maybe I phrased my original post badly. Here's what I mean to say:

     

    These are the suggestions users usually get when asking a similar question. I've tried those and they don't give the result I'd like:

    - change the amount of plots shown by reducing the size of the array that connects to the terminal or Value property node

    - change the amount of items shown in the legend by setting Legend / Number of rows.

×
×
  • Create New...

Important Information

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