|
Why can't we specify an IP Address to search for in the cRio Imaging Tool?
My team spent some time this summer giving an overview of using the 3 supported languages and what the toolchain looks like.
However, the team laptop we usually use for these things was unavailable, and we used a student's laptop running Ubuntu, but ran Windows 7 Pro inside of a vm (Oracle's VirtualBox was used).
We could ping 10.XX.YY.2 (the ip address of the cRio) from both the host computer and from inside the VM. We could even specify using the MAX tool what ip address to look for and access the cRio as such.
Pictures/proof can be provided upon request.
However, the cRio Imaging Tool will refuse to do this because it only scans relative to the perceived local ip address (10.XX.YY.1-254?), which is just in its own little world because of the virtual network device the VM uses.
Can we please have an option to specify what ip address to look for a cRio at in the cRio Imaging Tool we get from FRC?
This goes beyond just satisfying a small use case by one team, but would extend to every team that develops on a Linux box (running a VM), would like to, or is forced to because of odd circumstances. Besides that, it would remain consistent with the other tools we are given like the LabView development environment, Axis Camera Imaging Tool, and Driver Station, which all have options to specify what ip address to use or target. Furthermore, it would be quite simple to implement and probably save people some time while waiting for the scan to complete (such as those who must run such software from a netbook they use for a Driver Station).
|