Jump to content

Neil Pate

Members
  • Posts

    1,156
  • Joined

  • Last visited

  • Days Won

    102

Everything posted by Neil Pate

  1. @pawhan11 yes this was done because the "data" said that more people create a constant, so it should be at the top of the menu. Truly wish NI would stop f*cking around with stuff like this and fix NXG. There are tokens to turn it off but I have not bothered and instead just learning to get used to it.
  2. Nope, don't use it. I use my own logger I wrote myself. I am intrigued with the idea of using a DB for log messages in that I can get clever and do queries and things but at the end of the day human readable text files will probably trump for me due to their simplicity of consumption.
  3. Thanks @Jim Kring. The RC installed fine on my PC and editing the ini file to turn off the auto-start also seems to work.
  4. Not really tried sourcetree enough to make an educated comparison. I really like the look and feel of GitKraken and am now invested in learning how to use it properly. Also, at the time I was super annoyed with Atlassian for the way they handled the sunsetting of Mercurial and was fed up with dealing with their snail-slow Bitbucket servers all the time so I just picked up my toys, set aside a week or so to move 30 repositories over and now am a happy Github koolaid drinker.
  5. @jksh thanks for the explanation. In every other VCS I have used I can pretty much arbitrarily move around the changesets without fear. All I did was roll back to check out some earlier code and my recent changes just "disappeared" from the client. That is very unexpected behaviour. Sure, I was able to get them back by looking up the commits using the reflog because they were not truly missing, but it is really strange behaviour to me. Not wanting to sidetrack the discussions, I now using Plastic SCM at work where I do Unity and C# dev and its really quite nice to use. Apparently it is based on git but made more for game devs.
  6. Try GitKraken, it is not free if you want to access private repos on GitHub (which I do) but I really like the interface and does everything I need apart from showing the reflog which I believe Fork does show.
  7. I have recently embarked on this same journey and also found things to be way less intuitive than Hg. Which client are you using? I found GitHub desktop awful and am now using GitKraken which I really like. Just a few days ago I "lost" some work by rolling back to the "wrong" commit. I was able to get back my commit by reverting to the commit using the hash which can be found by running: git reflog I seem to get into a Detached head state quite often. No idea what I am doing wrong but have sort of figured out how to recover from it. Was not able to see the commits from another user for love or money. Turns out somehow the "upstream" on the remote (whatever this is) was not set correctly Anyway, stick with it my friend. The war is over and git has won...
  8. Quick update. I can send data from my cRIO to an Azure IoT hub, from there pass it to an Azure Streaming Analytics job which pumps the data into an Azure SQL DB and also to a Power BI Dashboard. The pieces of the puzzle are starting to fall into place 🙂
  9. Uninstalled 2020 when my computer fan was spinning up for no apparent reason and then I seem some VIPM Browser stuff chewing at my CPU. That is odd, I thought I disabled it.... oh wow the tickboxes cannot be unselected so last time I thought I was turning it off I was actually doing nothing. Installing 2019, thanks for the link @Michael Aivaliotis. By the way got any hacks to allow VIPM 2019 to manage LV2020 packages? This sucks 😞
  10. @Rolf Kalbermatter when is your kickstarter launching? You know the one where you write all this useless but interesting crap down in a nice coffee table book. I would back this project...
  11. Yeah I was quite surprised to see the new VIPM hidden away even when I thought it was turned off. Run with Windows start? Hmmm, no there is enough other crap starting then. Run with LabVIEW start? What??? Are you joking? LOL never.
  12. I used something like this about 5 years ago in a lab test. Interfacing with it over VISA was really easy it pretty much performed flawlessly.
  13. Is this what you want? I still don't really understand the subtleties of all the different scientific vs floating point formats and normally just play around until I get what I want. I find going into the Advanced numeric formatting is a huge help as it basically tells you the exact formatting string to use. Especially useful for timestamps!
  14. Yes but that is no longer Engineering formatting which is where the confusion is coming in. Format into string should be able to give you what you want, I will put an example shortly.
  15. Aren't engineering strings always multiples of 3 digits? You cannot have an engineering string 1.2x10E10,it will be 12x10E9 Maybe I misunderstood the question. if you want advanced string formatting you can use the format to string function, it allows a very flexible formatting string. Sorry on mobile now or would put some pics.
  16. Thanks AQ, you are the first to actually spell this out in words that make sense to engineers. Not sure too many here are going to like it though! ps: I liked your post due to its honesty and absence of marketing weasel words, not because I think this is a particularly good strategy for NI. Maybe I have just had a weird career but in the 20 years or so I have been developing LabVIEW based solutions virtually never would a custom off-the-shelf piece of software like Signal Express or similar come anywhere close to doing what I needed it to and it would require so much customisation that the benefit would be so low. To me LabVIEW is a programming language or RAD tool and the responsibility of NI is to deliver first class hardware with amazing software to help me bring the two together and that is it.
  17. The new colour scheme is growing on me, I quite like the green. The logo I think is entirely forgettable but this is really not important to me. Regarding the name change, were we not already referring to them as NI anyway? I think what we are forgetting is that none of this guff is for us... we are already customers and need no reminding of the benefits of spending your whole instrumentation budget on a cRIO! This stuff is to get the next million customers, the young engineers who might have never heard of National Instruments. The slogan is meant to ignite passion in young people, not to excite the already battle hardened. I do think the event was completely overhyped, but this is what marketing is about. In the short to medium term absolutely nothing is going change just because it cannot. A behemoth such as NI has so much momentum (or is it inertia... always get that wrong) that things will take time to change. NI was stagnating anyway, so this is probably a good thing.
  18. I did look at your Github page but did not try your code as I though it was the broker only. However upon closer examination I see it does include a client also. Would it be of interest to you to see if I can get it connecting to my Azue IoT hub? Edit: there seems to be an error in the project, the two Destroy.vi are not there. Removing them manually seems to fix the Test Server e I did try make the TLS changes and connect with sensible parameters but it did not seem to work. I can try again tomorrow if you like, otherwise I am probably going to park this here for now as I have a working solution with the other MQTT library.
  19. Mixed messages here... I was poking around tonight trying to bring a cRIO VM up to speed and realised just how many places on disk or in MAX and other applications they use the name National Instruments. Changing all those over to NI is going to be a job even bigger than developing NXG! This is going to get pretty confusing to the next generation of ambitious engineers using the products.
  20. WOOT! Just tested this MQQT library running on a simulated cRIO in a VM and it also works and can talk to my Azure IoT hub 🤩
  21. Wow that does look pretty similar! I guess the missing square in the top right corner makes all the difference though, there is no way anyone could get confused. I am not sure sure about the colour appearing in NXG though. new-NI has collected lots of data which conclusively proves that engineers and scientists are actually put off by colour and so are sticking to light grey, dull grey and washed out grey.
  22. This is the only change I made to the MQTT library. Simples 🙂
×
×
  • Create New...

Important Information

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