After I installed RDS 4, it seems like nothing works. I try to run the eddie-service from the DSS command prompt but I get red errors saying reference platform IO controller is configured wrong or something.
JonnyBritish you beat me to it! We're really excited about the official release of RDS 4.
Trygve, if you do just install RDS 4 without updating anything else, the Eddie service will break. In order to upgrade from beta, you also need to uninstall Kinect for Windows Beta 2 and install the official release of Kinect for Windows. There is also an updated Eddie Service that will need to be reinstalled. The updated service and installation instructions are available on www.parallax.com/eddie.
There have also been a couple of updates to the Robot Dashboard. Most notably, obstacle avoidance has been implemented while driving Eddie with the Wireless Xbox Controller. Also, previous bugs pointed out on this forum (inverted left/right & B button not disabling motors) have been fixed.
If you would like to use the Robot Dashboard without obstacle avoidance, you can do so using EddieDirect.cmd script instead of Eddie.cmd.
There have also been a couple of updates to the Robot Dashboard. Most notably, obstacle avoidance has been implemented while driving Eddie with the Wireless Xbox Controller. Also, previous bugs pointed out on this forum (inverted left/right & B button not disabling motors) have been fixed.
Enjoy!
After assembling Eddie, what are the steps I can follow to load the required software to the computer and a demo example so I can see Eddie roaming the room as you said in Eddie page.
Is there any PDF file that has all the steps regarding the software similar to the one you have for assembling the hardware.
Thank you
The Visual Studio configuration for the IO controller is whack. trevtay and drwho have their directories in a lot of places and after I removed them and built it, it won't run because it's looking for something on trevtay's drive. I can't find that setting. Just an FYI.
I want to add some devices to the controller, so I hope you can get a clean solution file for us.
I am using the Windows Kinect device now. Works well with MRDS 4.0. Such power in a sensor package.
In the setup instructions that come in the Eddie firmware package there is a section that talks about modifying the Propeller code. It mentions a setup script that you have to run. Sorry, I'm not at the computer that has the info so that I could give the exact wording. It essentially runs the DSSProjectMigration tool that fixes all of the path references and pointers to your key etc. Just run the script and re-open VS and the IO controller will compile.
JonnyBritish
Posts: 8
Comments
Trygve, if you do just install RDS 4 without updating anything else, the Eddie service will break. In order to upgrade from beta, you also need to uninstall Kinect for Windows Beta 2 and install the official release of Kinect for Windows. There is also an updated Eddie Service that will need to be reinstalled. The updated service and installation instructions are available on www.parallax.com/eddie.
There have also been a couple of updates to the Robot Dashboard. Most notably, obstacle avoidance has been implemented while driving Eddie with the Wireless Xbox Controller. Also, previous bugs pointed out on this forum (inverted left/right & B button not disabling motors) have been fixed.
If you would like to use the Robot Dashboard without obstacle avoidance, you can do so using EddieDirect.cmd script instead of Eddie.cmd.
Enjoy!
Wonderful...thank you!
Rick
Is there any PDF file that has all the steps regarding the software similar to the one you have for assembling the hardware.
Thank you
Let us know if you run into any problems!
I want to add some devices to the controller, so I hope you can get a clean solution file for us.
I am using the Windows Kinect device now. Works well with MRDS 4.0. Such power in a sensor package.
In the setup instructions that come in the Eddie firmware package there is a section that talks about modifying the Propeller code. It mentions a setup script that you have to run. Sorry, I'm not at the computer that has the info so that I could give the exact wording. It essentially runs the DSSProjectMigration tool that fixes all of the path references and pointers to your key etc. Just run the script and re-open VS and the IO controller will compile.