Ours were super fast. Did it in early summer. Thought is was about a 2 week turnaround.
Announcement
Collapse
Technology Forum Has Moved!
The FIRST Tech Challenge Technology forum has moved to a new location! Please take a look at our forum blog for links and instructions on how to access the new forum.
Note that volunteers (except for FTA/WTA/CSA will still access their role specific forum through this site. The blog also outlines how to access the volunteer forums.
Note that volunteers (except for FTA/WTA/CSA will still access their role specific forum through this site. The blog also outlines how to access the volunteer forums.
See more
See less
Firmware update for Modern Robotic modules
Collapse
X
-
Sent our in beginning of July and I had to email them middle of of August to find out where they were. They had our for 5 weeks!! and they only got sent after I contacted them that I had not received an email update to pay??
Fast email response and items sent out quickly afterwards but they sat on them for 5 weeks!!Dave - Mentor
CVTM Robotics Team 6966 (Bat Bots) Rookie Season 2013/14
CVTM Robotics Team 8257 (Bond Bots) Rookie Season 2014/15
Comment
-
We shipped ours to MRI on 9/16 (Friday). They arrived there on 9/19 (Monday). The update was completed on 9/23 (Friday), paid for, and shipped. USPS says we should receive them back on 9/26 (Monday). So a total 10 day turn around for us, including 2 day shipping in both directions. Pretty quick! Yeah!
Comment
-
Originally posted by tvsknights View PostCan anyone report on any benefits of this update? Has anyone actually had the update and noticed any improvement in function?
It is absolutely worth it.
Comment
-
The latest version of the MRI Core Device Discovery application has new features that access the new features in the updated MRI module firmware. In particular:- For motor controllers, you can select the type of DC motor used (e.g., Neverest, Tetrix) for the PID closed loop control algorithms (or select custom settings of your choosing).
- For servo controllers, you can select the extended range of operation that apparently allows a full 180+ degrees of operation on the standard 485 servos.
I haven't found a way to implement these changes in software, so to me it looks like you have to change these settings using the Core Device Discovery app. Others, please let me know if I'm wrong about this.
The Core Device Discovery app also allows LEDs on the Legacy modules and Core Device Interface modules to be turned on and off. Does anybody know if there is a way to do this in software using the SDK?
Comment
-
Originally posted by Cheer4FTC View PostThe latest version of the MRI Core Device Discovery application has new features that access the new features in the updated MRI module firmware. In particular:- For motor controllers, you can select the type of DC motor used (e.g., Neverest, Tetrix) for the PID closed loop control algorithms (or select custom settings of your choosing).
- For servo controllers, you can select the extended range of operation that apparently allows a full 180+ degrees of operation on the standard 485 servos.
I haven't found a way to implement these changes in software, so to me it looks like you have to change these settings using the Core Device Discovery app. Others, please let me know if I'm wrong about this.
The Core Device Discovery app also allows LEDs on the Legacy modules and Core Device Interface modules to be turned on and off. Does anybody know if there is a way to do this in software using the SDK?
The DcMotorControllerEx and DcMotorEx interfaces don't even seem to expose the PID preset option, and are likewise not implemented by any classes. I am also not sure whether the servo or motor controllers will save these values that were set in the Core Device Discovery application once restarted.
On the other hand, the LEDs on the DIM have been controllable since last year. Use DeviceInterfaceModule.setLED(). LED 0 is the blue one and LED 1 is the red one.
Comment
-
Originally posted by GearTicks View PostI am also not sure whether the servo or motor controllers will save these values that were set in the Core Device Discovery application once restarted.
Originally posted by GearTicks View PostOn the other hand, the LEDs on the DIM have been controllable since last year. Use DeviceInterfaceModule.setLED(). LED 0 is the blue one and LED 1 is the red one.
Comment
-
180 Servos
Originally posted by GearTicks View PostIn regards to the extended servo PWM range, I don't believe it is currently possible to set that in the SDK. There is an interface called ServoControllerEx that seems to allow this functionality, but it has no implementations. There is also a ServoImplEx class that extends from ServoImpl and makes use of a ServoControllerEx. Unless it is possible to hide SDK classes from the implementation tree, it does not seem that these can be used yet.
The DcMotorControllerEx and DcMotorEx interfaces don't even seem to expose the PID preset option, and are likewise not implemented by any classes. I am also not sure whether the servo or motor controllers will save these values that were set in the Core Device Discovery application once restarted.
On the other hand, the LEDs on the DIM have been controllable since last year. Use DeviceInterfaceModule.setLED(). LED 0 is the blue one and LED 1 is the red one.
Comment
-
180 Degree Servo
Originally posted by FTC9765 View PostConnect the servo controller to your PC, then run the Core Device Discovery app. It's a setting that you can change.
Here is the web site to get the Core discovery App. http://modernroboticsinc.com/coredevicediscovery
Here is the page to get the drivers for the Modern Robotic Controllers http://www.ftdichip.com/Drivers/VCP.htm
I had problems getting the Core Discovery App to work until I download the drivers. This was not working until I found the "Available as a setup executable" for the Drivers.
Once you get the Core Device Discovery App working you can go into the Advance Tab and enable the feature for each port on the Servo Controller that you want to be able to extend the range to what they should be.
Comment
Comment