It might be possible to configure your Mac OS to use a static IP of 10.TE.AM.55 allowing Parallels to grab 10.TE.AM.5. I doubt it, since the managed switch on the field network is only expecting one IP address to be issued to each driver station. I don’t know if the FMS’s DHCP server would be willing or able to provide more than one IP address on the team’s VLAN subnet. In this mode, the host OS (Mac OS) and the guest OS (Windows) both get an address on the 10.TE.AM.x subnet. If you really, really want to get this to work you might able to reconfigure Parallels to use Bridged Networking. The FMS would not be able to locate or communicate with the driver station software since it wouldn’t be at the expected 10.TE.AM.5 address. This guest OS would end up getting an address on a different subnet (probably .x). Assuming Parallels is set up in Shared Network configuration (the default), a separate virtual network is created and a private DHCP server is provided to the guest Windows OS. The FMS assigns the driver station laptop an IP address using DHCP. If you want the technical reason for why Parallels doesn’t work in the default network configuration, read on. ![]() ![]() Not only that, but if you run into any communication or connection issues at an event, it’s unlikely the FTA would be able to support or understand the setup. ![]() The network communication between the FRC Driver Station software and the FMS is timing critical. I would not recommend running driver station in Parallels.
0 Comments
Leave a Reply. |