crossrulz

A new hardware platform called TestScale sounds interesting. Unfortunately, NI's web site has no information on it yet.

Yeah, but this is still a major support hole.

HP spun off the T&M into Agilent, who grew into the Life Sciences industry. Agilent then spun off the T&M into Keysight. Personally, I'm expecting NI to spin off the T&M part of their business into a new company in the next 5-10 years. Whether or not LabVIEW is part of that, I have no clue.

Your DAQ sample rate is 1 second. So you need to make sure you are pulling off the data at least at that rate. 1. Again, change your Timed Loop to a normal While Loop. It is hurting you more than helping. 2. Change your DAQmx Read to be N Channel 1 Sample. This will simplify things a little as you will no longer need the 5 functions just to get a single value out. You will just need to use Index Array (expand to 2 elements so you can get both channels). 3. You need to clear the task once the loop is done.

No call for presentations. It will be all NI.

1. Change your Timed Loop to a simple While Loop. The DAQmx Task will limit the loop rate. 2. Don't use the DAQ Assistant. Learn to use the actual DAQmx API. You will make things a lot more efficient.

Well, that explains what I encountered today as well. I did notice an extra character. I didn't investigate beyond that. Hopefully this will be fixed quickly in a patch.

crosspost on the dark side: https://forums.ni.com/t5/LabVIEW/Application-recovery/m-p/4213987

Yeah, but you are talking about pasting into other applications. How are they interfacing with the clipboard? We have no control over that. You will see this same issue if you try to interact with a DLL that uses C-style strings (data will be cut off at the NULL character). I should also state that the NULL is copied over if you paste into another LabVIEW string control (yes, I just tested it).

It may be valid, but for any application that uses C-style strings, the NULL character ends the string.

Last I was aware, he is still not part of R&D. His initial project came to a close and he moved on to another one.

Code is also orders of magnitude more complicated now than back then due to more computational power being available and therefore more features are possible. More code just increases the probability of bugs. About 15 years ago, I was peripherally involved on testing code for a $50k FPGA in a satellite. The amount of testing that code went through was absolutely insane, including days of just Reed-Solomon test cases.

What do you mean "no significant new features"? 2017: Malleable VIs, 2019: Maps and Sets, 2020: Interfaces I'll give you the rest though. I have about as much hope in NI Connect as I did during NI's marketing event last year. And NI's communication lately has been lacking at best.

I think you are referring to the GLA Summit that happened in November. VIWeek was in May. Yes, everything changed last year...

I'm left to assume you are referring to VI Week, which was put together in a week or two, completely by the community.

Jordan, the Beta is public. This means you can still participate in the beta forum. That would be the place to ask. https://forums.ni.com/t5/LabVIEW-2021-Public-Beta/bd-p/labview-2021-beta

That was one of the main reasons.

Probably related to this: Spam emails

The Delacor Queued Message Handler (DQMH) is based on using events. You might want to give it a good look.

What I typically do in this situation is use a QMH that manages the hardware. The control loop can send a message to the device loop using a queue. The device loop then does whatever needs done and sends a reply back to the control loop. If no messages are coming in (the queue has a time out), then the device loop can collect data. What this does is isolate the device to a single loop and only it needs the object. The alternative is to use a Data Value Reference (DVR) to store the object. The In Place Element Structure that acts as the boundary so two operations cannot happen at the same time.

You can install NI Linx to LabVIEW 2020 using VI Package Manager.

It looks like you went through a lot of work trying to recreate the Actor Framework, which is already built into LabVIEW. Perhaps you should dig through the examples for using Actor Framework.

You could store it as what I call ASCII Hex. You use 2 ASCII characters per byte to represent the value. You can then use Scan From String or other string manipulations to convert that to a U64 or byte array.

I always stored my SVN repositories on a network drive that was constantly being backed up (I think most IT setups do it nightly). The issue with SVN is that you cannot do any commits or reversions if you cannot access the repository. So if you don't have access to the server, SVN won't do much. That is one of the good things with GIT: you have the remote and the local repository. You can commit and revert locally all you want and then eventually push your updates to the remote repository when you can.

I regards to merging: https://en.wikipedia.org/wiki/Merge_(version_control) In short, it is trying to reconcile the differences between two versions of a file. This happens when you try to merge branches or if you are working in a team and more than 1 person tries to update the same file. If working alone, just don't branch and you will never have to worry about merging.