crossrulz

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

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.

I used to use Tortoise SVN. It was extremely simple to use as it was right from Windows Explorer. Due to company requirements, I have moved over to GitHub (enterprise server) with SourceTree as the interface. Both work well for me. The only real problems when it comes to SCC and LabVIEW is when you have to merge. If you avoid merging, you will rarely have issues. Text languages also have issues when it comes to merging, it is just easier to manage text files than binary files. I have yet to run into any other issues due to the SCC screwing up.

At this point, I would probably go a slightly different route. You could get an Arduino or Raspberry and program them to do the I2C communications for you. In the RT system, you can just communicate the data through a serial port. Another option I have been tempted to go with is to use a SC18IM700IPW, which is a I2C-UART chip. Again, you just have to use a serial port to talk to it. But this would be more hardware design than the other option.