Quote:
Originally Posted by Ari423
What are the major changes with v2 from v1?
Also what kind of luck have you had using LabVIEW with GitHub. My team has tried it a number of times but it never seemed to work out how we wanted.
|
The biggest change is how the navX is read from, better support for Serial, and better recovery support for power issues.
In v1 SPI/I2C were read and cached if needed when ever the user would make the read request. Where as the Serial had a background loop VI running to handle the serial buffer that would dump data into global variables.
In v2 all interfaces run in a background loop VI that handles and navX reading and writing for the navX, stores the navX registry cache, handles any brownouts/disconnects to the navX, and makes sure that the latest data is always available to the user. This also allows for using a common set of VIs for reading and updating the navX and switching interfaces without the need to rewrite code. The Serial protocol can now also be switched during runtime.
The biggest thing for myself is a better organization of the files. In v1 I started with I2C and SPI as my team didn't see the need for serial. I was later asked to add Serial by Scott from KauaiLabs so that was sort of just shoehorned in. In the new version all interfaces are handled the same.
On LabVIEW and GitHub:
LabVIEW and Git are not the best of friends, but can be made to work together. Here is an
NI Community Doc after a quick Google search about LabVIEW and Git.