Just to get this thread on my list...
Got me a NanoVNA, too. Have not really used it, yet, as I need to better understand what it actually does. So far I know it measures resistance and capacitance of A/C over frequency --> Impedance.
I am interested in writing my own software in VB .net, as I already did for the SMA/NWT Spectrum analyser developed by BG7TBL.
Is there any document to start with, explaining the serial communication protocol?
Not that I am aware of. I did search and ask the group prior to starting.
Questions to joeqsmith:
- What version of LabView are you using?
For home, I have a Pro license for 2011, along with the 2014 Home license.
- Is the HOME version worth the purchase (discussed in a different thread on this forum - a HOME version for personal use at 49 US$)?
You may as well ask me about houses, cars and handheld DMMs. There is no way I would know if the Home is worth the purchase for you personally. Obviously I felt it was worth it for me or I wouldn't have purchased it.
- Does it come with all required components/toolboxes?
You may have asked me if you car requires four doors or two. Again, I don't know what your requirements would be. But as I stated in the other thread you mention, you can run free one week trials on the tools to determine if they fit your needs or not. And again, they will extend these times. If your question is if I can run the code I developed for the Nano with the Home edition as supplied, then the answer yes.
- Are you allowed to distribute the compiled version done with HOME version for free? Or would that be against "personal use"?
http://sine.ni.com/nips/cds/view/p/lang/en/nid/213095You may share your work only for noncommercial, nonindustrial, and nonacademic purposes.
- How big is the time saving in doing your software in LabView as opposed to .net (C# or VB)?[/li][/list]
I had someone post about it being a pity that I did it in LabView rather than Python. When I first looked at the supplied software, I knew it couldn't be used for the demo which is why I decided to roll my own. I didn't waste a lot of time complaining about the problems but rather posted I was going to write my own in LabView, then proceeded to write it in LabView, then made a couple of videos showing the LabView code running it. All in the course of about a week. This included the time reversing the protocol.
Obviously, I am not doing anything to hinder this poster from showing us some Python code or posting about how long they took to develop it. You could certainly could show us another language and post your development time as well. Beyond some experts like yourself actually doing something like this, I can't really offer you any data on a time saving metric. I did however post how I exclusively use LabView for PC software development because of the time it has saved me.