crossrulz

23 minutes ago, Neil Pate said:

Yes I know. But this is LabVIEW which does not have null terminated strings. That is what makes this strange. 

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.

34 minutes ago, X___ said:

He didn't leave and in fact should be back by now:

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.

11 hours ago, ShaunR said:

I wouldn't put 99.999% of any code written today on a satellite-and that includes my own.

Go back 20 years and I would swear by any code that was written would have zero bugs otherwise it would not have been published.

The reliance today on "updates" and "beta" versions  is a detriment to all software. It's like psychologists creating models of human behaviour  and expecting it to model real life...with updates.

Call me cynical but I think software robustness is a far-cry from what it used to be. But that's progress, right? 

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.

3 hours ago, pawhan11 said:

- No significant new features and roadmaps, unknown future of the language. They killed NXG and announced it on forum post!...  Hope this new NI Conect will change my mind.

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.

Quote

4 hours ago, Jordan Kuehn said:

Yes. 
 

edit// my apologies. I’m realizing now that I was combining that excellent event with the CLA event in my mind. Perhaps it could happen again in parallel?

 

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

1 hour ago, Jordan Kuehn said:

Hmm. Well the stuff that made last year’s great was it was largely community driven with some NI involvement and almost no fluff or upward trending graphs without axis labels/scales...

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

3 minutes ago, Bryan said:

Did they give a reason?  I'm betting has something to do with "Microsoft CE" being a thing, and they don't want to even remotely draw any negative attention from Microshaft.

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.

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.

LabVIEW Community Edition (NI has strictly stated we should not call it "CE") is a full release.  It is nowhere close to a beta nor a replacement for a beta.  That said, I still have not heard anything on the upcoming beta.  I will have to see if I can get a hold of somebody about this.

1 hour ago, Antoine Chalons said:

Would it be possible to add support for maps / sets - as if they were arrays - ?

I can really remember if they were added in LV 17 or 18 or 19....

Sets and Maps were added in 2019.  But just to throw a wrench into your dreams, you can get some interesting combinations when it comes to sets and maps.  You could have a set of maps.  You could have a map with a set for a key.  I'm just saying, you would have to plan this out very carefully.

Shameless plug: Proper Way to Communicate Over Serial

This seems to work...

CRC16-CCITT-FALSE.vi

12 minutes ago, hooovahh said:

It was but does give us some character development.  Showing the exhaustion on his face, and surrounded by dozens of people that might attack.  He kinda is like, nah I'm done I got other things to do.

But  the real story:  Harrison Ford was sick and so the director just off-the-cuff said to just shoot the guy.  A big sword fight was originally planned, but instead we got one of the most iconic movie moments.

Looks like you have a few confirmations about the crash in 2019 but fixed in 2020.