Open wkcwells opened 9 years ago
Mark suggests:
Split parameter matching and range checking into separate features. I suspect that for most parameters, we will want to see identical matches. However, a separate high/low feature could help with error checking… including errors that are inadvertently introduced into the master parameter file.
One example…. let’s say that we want Waliid to have a LIM_ROLL_CD of 5500 (55 degrees measured in centidegrees). Our intention is that each and every Waliid has the same limit, so we’d want a fixed parameter. However, we could also have bounds checking running in the background of 2500-6500. That way if a user goes into the master parameter file and accidentally changes it to 55 (units conversion error… degrees instead of centidegrees) it would flag.
Add meta data to the validator file to enable managing multiple files and multiple versions.
Includes the ability to generate a template rule file from an existing aircraft or parameter file. Most of this functionality will actually be implemented in the mavlink project.