Are you talking about the ardupilot differences? If so, APM stacks always sends params in float across mavlink whereas px4 puts them in the right part of the union. I haven’t run this change, but it doesn’t look like it would work against the px4fmu stack. Trey are you testing against APM or px4fmu stack?

On Apr 29, 2014, at 9:25 AM, Lorenz Meier <notifications@github.com> wrote:

> In src/uas/UAS.cc:
> 
> > -        }
> > -        else {
> > -            param = QVariant(paramValue.param_int32);
> > -        }
> > -        parameters.value(compId)->insert(paramName, param);
> > -        // Emit change
> > -        emit parameterChanged(uasId, compId, paramName, param);
> > -        emit parameterChanged(uasId, compId, rawValue.param_count, rawValue.param_index, paramName, param);
> > -//                qDebug() << "RECEIVED PARAM:" << param;
> > -    }
> > -        break;
> > -    default:
> > -        qCritical() << "INVALID DATA TYPE USED AS PARAMETER VALUE: " << rawValue.param_type;
> > +    switch (rawValue.param_type) {
> > +        case MAV_PARAM_TYPE_REAL32:
> > +            if (getAutopilotType() == MAV_AUTOPILOT_ARDUPILOTMEGA) {
> I don't quite get why this would be necessary - do you have an intuition? @DonLakeFlyer Could you maybe cross-test?
> 
> —
> Reply to this email directly or view it on GitHub.
>