Jump to content

crossrulz

Members
  • Content Count

    468
  • Joined

  • Last visited

  • Days Won

    18

crossrulz last won the day on January 27

crossrulz had the most liked content!

Community Reputation

87

About crossrulz

  • Rank
    Extremely Active
  • Birthday 04/22/1982

Profile Information

  • Gender
    Male
  • Location
    Cincinnati, OH

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since
    2005

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. Shameless plug: Proper Way to Communicate Over Serial
  8. This seems to work... CRC16-CCITT-FALSE.vi
  9. 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.
  10. Looks like you have a few confirmations about the crash in 2019 but fixed in 2020.
  11. The release cycle was changed so that the main release remained with NI Week. So there was no LabVIEW 2016 SP1 since NI Week was moved from August to May in 2017. AQ has told me that NI has a "quarterly" release cycle, so who knows when LabVIEW 2021 would be released (April? July? October? Never?)
  12. No, you are not the only one. Unfortunately, this is the color scheme all NI products are going with. Have you seen the LabVIEW 2020 SP1 Getting Started Window?
  13. My understanding is that NXG is a full platform effort, not just LabVIEW. The LabVIEW part was scrapped, not everything else. I suspect the devs for LabVIEW NXG have already been moved on to work on Instrument Studio, TestStand (2020 has the NXG look), VeriStand, Flex Logger, etc.
  14. Now imagine a "Senior Engineer" being brought in on a project and being told to redo everything because you used an Event Structure. No, I am not exaggerating. He had issues with the Event Structure in LabVIEW 6 and swore them off forever. Good thing I didn't listen to him, managed to get him to leave me alone, and the project was successful. My point here is that titles should be taken with a grain of salt.
  15. Coming from my personal experience, I still lean towards no. I had a discussion with Nancy Hanson about this and we came the the conclusion that the CLA was not a destination, but the opening of doors to learn (yes, this was alluding to the CLA Summits). Personally, I had 0 experience using OOP when I got my CLA. But after my second CLA Summit, I found an application that deserved a very basic OOP architecture. The CLA Summit opened that door for me. Now I would say ~50% of what I do is OOP. There is still A LOT you can do effectively without OOP. And keep in mind that part of a CLA is
×
×
  • Create New...

Important Information

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