Jump to content

ShaunR

Members
  • Posts

    4,849
  • Joined

  • Days Won

    292

Posts posted by ShaunR

  1. 23 minutes ago, CT2DAC said:

    so what can be so complicated in a trivial handful of commands and parameters?

    Termination characters, for a start.;)

    I would echo what Rolf is saying. With SCPI you can get some of the way there as it standardises instrument behaviours - but even then it' has limitations.

    IMO, the most expedient way to develop when you don't have the hardware is to use stubs rather than simulators. Design top-down and use stubs where you would have a driver to give you a value and an error that you can can use to develop and test  the rest of the software. When you get the hardware, you can use the stubs as an interface to a driver to massage whatever it gives into a form your software is expecting. You will, to all intents and purposes, be designing a proprietary interface for your particular software that you glue drivers underneath as and when you get your hands on them.

  2. 15 hours ago, bjustice said:

    I can't seem to figure out how they were able to make this combination, because I can't find any control on the native palette with these item parts.

    The System Button has the mouse over images.

    You can't "import parts", only the images for the states. That includes if you simply want to change the mouseover colour (copy the image, paste it into an image editor, change the colour, then import it back again).

    The mouseover also only works while the VI is running.

  3. 2 hours ago, SebastienM said:

    Well 2 years ago I saw a demo of System Link by a Ni salesman and that was a huge buggy disaster, absolutely giant failure.

    I convinced my company to use WATS of Virinco instead : best choice ever.

    Well. They are not really equivalent. System Link is, first and foremost, a configuration and asset management tool. Buggy? Maybe (I haven't looked recently) but that could be addressed. WATS is specifically a data analytics tool. WATS has more in common with Diadem than System Link.

  4. 16 hours ago, SebastienM said:

    In the end if LabVIEW is discontinued or let dying I could move completely from NI and honestly they would deserve it.

    We shall see. The "Fat Lady" hasn't sung yet and Emerson shareholders seem more than a little unhappy about the takeover. I'm still bullish on this failing despite Dr T's intervention.

    The more I look at it, the more this seems like taking out the competition as opposed to diversifying and entering new markets. I think System Link was probably the trigger for this as it could, in the future, take Emersons offerings head-on and provide a far more superior top-to-bottom solution given NI's driver, LabVIEW and Test Stand support.

  5. 1 hour ago, Rolf Kalbermatter said:

    My dream was that they can develop something that allows the LabVIEW front panel to be remoted as HTML5

    Actually you can sort of do this already but it's not native. Websockets made this possible. All it requires is to be able to map a web page to a front panel and come up with a protocol. It is surprisingly easy as long as you don't use panes.

    It would seem to be a nice feature to just lay down LV controls and for them to be replicated remotely, but then it'd just look like a LV front panel in a browser - you might as well send an image.

    63ce2d8215b25d14611365c2681dbf45_f62.png.ff0679d0485c742b9e6b9642c46d1ac8.png

    You need to be able to customise the HTML and the LabVIEW IDE would make an awful HTML editor. It's far better to make the HTML (or get a web-dev to do it) and tell LabVIEW what controls were pressed - effectively separating LabVIEW from the FP the user interacts with.

    3205f4f0b625ff24b1e3ba9e7968c6e0_f100.png.38b562e25945065b3d617d33b13f2525.png

    But I was thinking more of VI server being the interface for LabVIEW as a back-end, function server so that in addition to the above, it could also act as binding for other languages (RPC). They did something similar with their webserver where you could call functions but it was a hideous solution requiring deployment of the NI Webserver and Silverlight etc. You could map a web page address to a VI to call. VI server has much finer granularity than just user VI's and, IMO, should have been the starting point.

  6. 31 minutes ago, X___ said:

    what their logical conclusion will be moving forward

    Their logical conclusion would be that it's not a big market and we can't support it. You can say goodbye to LabVIEW, IMO.

    1 hour ago, X___ said:

    Here is it: develop a Python module that allows representing python code graphically. The execution parallelism implemented in LabVIEW would probably be the trickiest part, but I am not sure I would require it initially. And implement some type and syntax checking breaking the "diagrams" at edit time rather than at compile/runtime (typos is what I hate in text-based languages).

    This is a fantasy. Python is well known for being poor at multithreading, if you can call it multithreading. 

    I understand that you are just trying to find a new place for LabVIEW but getting Python to support a data-flow paradigm is probably a bit too much.

    We have a number of programming languages and paradigms at our disposal so why try to shoe-horn everything into Python? Use the right tool for the task. I don't use LabVIEW when writing webserver code.

    IMO, LabVIEW's biggest weakness is the UI. Python isn't a good improvement on that and vice-versa. LabVIEW would also be a very expensive and cumbersome development tool just for planning and maintining python applications. Perhaps a more realistic solution would be to improve the LabVIEW VI server so that it could interface with other languages directly using TCP - make it more like an RPC interface. That may scratch your Python fetish itch.

  7. 19 minutes ago, Rolf Kalbermatter said:

    The C compiler was their own invention I believe

    I think the C compiler was (or was based on) on the Watcom compiler.

    19 minutes ago, Rolf Kalbermatter said:

    Callback support in LabVIEW, while not impossible to do (ctypes in Python can do it too). always was considered an esoteric thing.

    Well. Callbacks are a poor-man's event. The C/C++ industry has always had problems with fitting event driven programming into their straight-jacket. They are being forced to nowadays with Service Oriented Programming and all they have is callbacks as an answer-leaving the programmer to figure out threading and asynchronous operation. It's why I prefer Object Pascal (Delphi, Lazarus et.al.) over C/C++ ;)

  8. 1 hour ago, Rolf Kalbermatter said:

    At the same time they stopped LabWindows/CVI completely which always had been a step child in the NI offerings

    I always felt they could have had a tighter integration between LabVIEW and CVI. It could have solved our lack of being able to use C callbacks for a start. A CVI node like the Formula node could have been quite useful too. 

  9. 6 hours ago, Reds said:

    Thats a pretty significant commentary on how he feels about current management.

    Maybe. Although he's getting on a bit and has an interest in Alzheimer's. Could also be looking at passing an inheritance where a cash drop like this would be great. Difficult to understand he'd be happy about his life's work being swallowed by another corporation just for a few decimal points of his billions in cash.

    Interesting he talks about "stakeholders" instead of shareholders but it does not bode well for NI.

    The plot thickens!

  10. 1 hour ago, Rolf Kalbermatter said:

    See this thread for a discussion of getting the GetValueByPointer to work in a build application or alternatingly replace it with another function that does not need this DLL.

    I like your solution. I've always used moveblock with strlen which, although it seems faster, is far less intuitive.

    On a different note. Try not to use those utility functions at all. They all run in the Root loop! I may use them for prototyping but always replace them in production code.

  11. 4 hours ago, drjdpowell said:

    Noone in the corporate world thinks any less of Emerson for doing a very normal business thing.

    It's only a normal business thing for American companies.

    My hunch is that this will fail. NI are vehemently defending and has foreign customers who are heavily invested in their technology-some of who are Governments. I'm sure customers like CERN are not very happy about the situation and similar organisations have very strong influence over these sorts of matters. I hope I am right but if I am not, I wouldn't be surprised at a few more spanners being thrown in to the works later down the line after a successful bid.

    I've my fingers and toes crossed for NI to ride this out.

  12. 25 minutes ago, Youssef Menjour said:

    But then why in the .VI version it works and in the .exe version not at all?

    Maybe it requires privilege escalation because it's in an executable. Maybe it needs a confirmation to run the command. The only way you will know is to not hide the cmd window and run it with the "/k" switch so you can see what it's actually doing.

  13. 37 minutes ago, Youssef Menjour said:

    If you want to see all cases you just have drag and drop on your labview diagram the sniped.

    Snippets don't work very well and the meta information is stripped by some websites and browsers. It is always better to post the code.

    3 hours ago, Youssef Menjour said:

    CMD inside the exe are blocked since cuda installer was launched, why ?

    Probably the "cmd /c where nvcc" isn't finishing for some reason (waiting for input?) and as you have the cmd VI set to wait until completion, it just gets stuck there.

  14. I overlooked it in the initial post but NI also changed their Rights Agreement. They's fighting hard.

    Quote

     

    • Flip In. If a person or group becomes an Acquiring Person, all holders of Rights except the Acquiring Person may, for the Exercise Price, purchase shares of Company Common Stock with a market value of $400, based on the market price of Company Common Stock prior to such acquisition.

    • Exchange. After a person or group becomes an Acquiring Person, but before an Acquiring Person owns 50% or more of the outstanding shares of Company Common Stock, the Board may extinguish the Rights by exchanging one share of Company Common Stock or an equivalent security for each Right, other than Rights held by the Acquiring Person.

     Flip Over. If the Company is later acquired in a merger or similar transaction after the Rights Distribution Date, all holders of Rights except the Acquiring Person may, for the Exercise Price, purchase shares of the acquiring corporation with a market value of $400 based on the market price of the acquiring corporation's stock, prior to such transaction.

     

    That last one is a doozy and is probably the "poison pill" Emerson are talking about.

×
×
  • Create New...

Important Information

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