ShaunR

Sorry, no. I'm a heathen and use GCC with CodeBlocks.

And there we have it! They couldn't get them to sell, they tried maneuvering for a takeover (which was thwarted) and now all they can do is appeal to the shareholders.

No. You cannot call LabVIEW VI's as function pointers in unmanaged code ... period! I will reiterate: It's only worth going to the original driver and interfacing directly with LabVIEW *IF* it means you don't need a callback.

LabVIEW cannot supply callbacks for unmanaged function calls. You will have to create a C/C++ wrapper DLL that creates and registers the callback with the function and inside that callback use PostLVUserEvent to send it to LabVIEW. You've read those articles but haven't quite understood that you need a DLL wrapper and it is what actually registers and executes the callback with the function.

Whether they would allow a takeover or not is really up to the shareholders. A professional group wouldn't be tying the hands of their shareholders with outright condemnations of potential future owners. My understanding is that this was an automatic response triggered by their share structure to prevent such things. This action will mean it cannot easily be forcibly taken-if that is actually what is going on. If you remember. Elon Musk increased his holdings in Twitter to 10% just before he bought them out. Twitter didn't mitigate it like this though. My interpretation was that they acknowledged someone was prowling and making moves and, now they are aware, they will see what the shareholders think of it after having mitigated the threat. $450k per annum with 100% bonus and 1.5M stocks. It beats the crap out of what you get for playing the piano.

No that much of a surprise. Emerson have been eyeing NI for a long time. Here's something from 2015...

Well. It would be consistent with: and since they state and time (or lack of it) seems to be important my money is on a hostile takeover.

Interesting... It's not the usual option for selling a company. You don't dilute your shares if you are going to sell. You normally do this sort of thing either if cashflow is a problem or you are facing a hostile takeover.

Very much the tail wagging the dog but it could certainly replace many of the managers I've worked with.

They should give it an error code. I would suggest Error ID:10T There are a number of interesting points here though. It evaluates logical inconsistencies - it's doesn't seem to be just a look-up or query engine. It doesn't know how to say "I don't know" or suggest alternative sources where information may be sought - It doesn't comprehend its own limitations. It behaves more like an Oracle than, say, quoting or suggesting papers where certain arguments or theorems were undoubtedly gleaned - e.g. Leibniz, Riemann et. al. Did you also ask it for the source of it's information or to introspectively analyze it's own answers to see if it could identify the flaws in it's own reasoning?

Yes. I was much more impressed with the imaging AI's. This video builds a website. The imaging is very straight forward and produces excellent results. He then uses ChatGPT to make some text (which isn't that awe inspiring) and then puts it all together with one of those do-it-all web services. In reality, the only impressive thing here is the imaging. However. ChatGPT is only used for a bit of content, not for creating the website proper. He spends a lot of the video creating the web pages in a service to use the images. I think the days of web businesses like Shuttershock are over though.

NXG was XML, was it not? Good job they abandoned it. Sigh.. No early retirement for me then. I suppose if I was prepared to give Skynet my telephone number I could have had it translate for me. But from Google it seems that was another fail to do LabVIEW. Even so. All the examples of how fantastic it is for text languages seems to always be fairly trivial examples - mainly single functions, that they cajole to an answer. My first impression is that it's an excellent natural language interpreter but not impressed with the claim that all our coding jobs are in danger. I'm much more impressed with the Graphics AI's such as Midjourney.

Everyone is losing their minds over ChatGPT. Well. Text programmers are Anyone played with it to try and produce LabVIEW code?

Right click on the tunnel and select "Linked Input Tunnel>Create and Wire Unused cases"

C:\ProgramData\National Instruments\Partners

Interesting. I assumed you used the TEK one here. It looks very much like the whole API is a "work in progress" as many functions are not supported and... Do they distribute the DLL source code as part of an SDK?

The caveat here though is that USB is not an easy interface even in LabVIEW. I've heard that many people decide to make a MAX configuration instead of USB driver because it's just so damned low level and does anyone remember the difficulties with webcams? I use libusb and a 3rd party wrapper for the RTL-SDR which is not only far easier but much faster. A wrapper and DLL driver is probably a must for asynchronous callbacks - it's not for the faint-at-heart. The only time a USB device is easy is when it presents itself as a COM port which I very much doubt for streaming high speed IQ data.

The Disconnect can take a device ID (according to the matlab example). However. this little gem was in the python: note: the API can only currently access one at a time I would expect better from them (intern?). Their proprietary software supports multiple devices so its just what they are supplying with the RSA API. All their GPIB and Ethernet devices are SCPI compliant so I wouldn't be surprised if it was just SCPI over USB with Bulk transfers for IQ data streaming. But considering the state of the API, you never know. You'd need the programmers reference.

Hmmm. This seems just plain wrong (on so many levels). The Tektronicss RSA API has the following two functions DEVICE_SearchInt DEVICE_Connect Which would suggest it can quite happily support multiple devices. Interesting though. I didn't see a "Close" or "Disconnect" function in the examples (I don't have the actual driver to check).

Well it seems to basically be NI's "Protocol Buffers" - scripted compilation to create [de]sterilizers. I lost interest at that point.

So do I.

Yup. this works too.

Yes. But he will be populating the array data inside the DLL so if he mem copies u64's into the array it's likely little endian (on Intel). When we Moveblock out, the bytes may need manipulation to get them into big endian for the type cast. Ideally, the DLL should handle the endianess internally so that we don't have to manipulate in LabVIEW. If I'm wrong on this then that's a bonus. I think this can also be done directly by Moveblock using the Adapt to Type (for a CLFN) instead of the type cast but I think you'd need to guarantee the big endian and using a for loop to create the cluster array (speed?).

A la.. cluster casting with moveblock.vi

You could do this. It may be a lot easier handling a contiguous array in your DLL than a LabVIEW array of clusters (but that is possible too). Instead of creating 1000 pointer arrays of 256 (uint64s?) just pass a single 1D pointer of an array of 256,000 elements and pars it out as above.