Skip to content

Dynamics Config in EEPROM

Craig McDonald requested to merge feature/dyn-cfg-eeprom into devel-ufe

Description

Added Dynamics configurations to the EEPROM, so now they are CoAP message types. This resulted in a couple of files with a massive number of lines changed, as you'll notice. The first is the very long dynamics config, dynamics link config, and dynamic drive config types all being taken out of Dynamics.cs and moved into the CoAP.MsgTypes name space. The second change is maybe dumb, so if you have thoughts I'm open to hearing them. The file MsgTypes.cs has gotten so large that MonoDevelop slows down dramatically when editing it, so I split it into two files. I just called the second one MsgTypes2.cs, since I didn't bother grouping them in any logical way.

The functional changes are just making sure that the robot CoAP client can successfully get/put dynamics configurations, and I used my favorite ConfigurationFileTest.cs to confirm that.

Requires mainboard firmware version 6.7.0 or greater.

What to focus on

  • Use ConfigurationFileTest program in Sandbox to confirm that we can get/put the DynamicsConfig, and it's two components DynamicsLinksConfig and DynamicsDriveConfig. You can also use the automated test, but be sure to press [N] to switch the system configuration over to V2Teneo when testing with Teneo. Test with both Teneo and CPI.
Edited by Craig McDonald

Merge request reports