Thanks for your question. The steps to deploy .NET skills using a USB-to-Ethernet adapter require the adapter to be connected to your router, and the router provides the IP address for the adapter.
That said, live debugging of .NET skills no longer requires a USB-to-Ethernet adapter. As long as your robot is running the current version of Misty’s software, you can apply the recent Android patch to enable live debugging of .NET skills using Misty’s Wi-Fi IP address.
The patch adds new ports to the list that Misty’s 820 WiFi connection forwards to the robot’s 410 processor, which makes it possible to use Misty’s Wi-Fi IP address – instead of her 410 IP address (which is really the IP address of a USB-to-Ethernet adapter connected to your router) – to deploy .NET skills and attach a debugger from Visual Studio.
Keep in mind the following when you deploy .NET skills:
- The first time you deploy a skill, it may fail to attach for debugging after deployment, and you may see a message in Visual Studio that indicates the skill is already running. If this happens and you want to walk through the debugger with your skill, you can generally just deploy the skill again, and it should attach for debugging the second time.
- On the Task Properties page for your skill project in Visual Studio, there is a checkbox that says: Uninstall and then re-install my package. All information about the application state is deleted. If this box is checked, the task is reinstalled each time you deploy it to Misty, and it never moves to debug mode. You’ll want to make sure this box is unchecked, and then the debugger should attach and run on the second deployment.
- The task only runs as a debuggable background task for a less than a minute unless the skill starts, so you should try to start the skill from he Skill Runner page fairly quickly after deployment.
I’m sorry for any confusion around this. If this doesn’t get you what you need, let us know and we’ll keep working toward a solution