Is User Hook available in APMRover?

Hi - sounds very interesting what your doing. Your correct that the Userhook code is only available in Copter. Its very old and not the recommended approach moving forward.

The standard way to implement what your doing is to write a driver. Presumably if you have new I2C device you are plugging onto the APM you have written a driver for it?

The APM has very little on board storage so I wouldn't advise trying to keep data there unless you plan to upgrade to a Pixhawk which has loads of local storage on the SDCard.

The log file isn't sent to the GCS. Telemetry data and some other bits and pieces are sent to the GCS and logged there. You could include your new data in the telemetry stream and the GCS would log it.

The best place to start is look at how an existing driver works. Try the plane airspeed sensor. libraries/AP_Airspeed. Because your on APM2.6 have a look at AP_Airspeed_I2C .h/cpp files. That's the driver. You can see that ArduPlane.pde around line 454 creates the airspeed class and in that constructor it calls init. That then registers the _timer method in HAL schedule call back and your done. _timer will be called periodically from the scheduler and you can do your stuff in that.

Thanks, Grant.

Replies

Developer

Grant Morphett April 28, 2015 at 12:56am

Hi - sounds very interesting what your doing. Your correct that the Userhook code is only available in Copter. Its very old and not the recommended approach moving forward.

The standard way to implement what your doing is to write a driver. Presumably if you have new I2C device you are plugging onto the APM you have written a driver for it?

The APM has very little on board storage so I wouldn't advise trying to keep data there unless you plan to upgrade to a Pixhawk which has loads of local storage on the SDCard.

The log file isn't sent to the GCS. Telemetry data and some other bits and pieces are sent to the GCS and logged there. You could include your new data in the telemetry stream and the GCS would log it.

The best place to start is look at how an existing driver works. Try the plane airspeed sensor. libraries/AP_Airspeed. Because your on APM2.6 have a look at AP_Airspeed_I2C .h/cpp files. That's the driver. You can see that ArduPlane.pde around line 454 creates the airspeed class and in that constructor it calls init. That then registers the _timer method in HAL schedule call back and your done. _timer will be called periodically from the scheduler and you can do your stuff in that.

Thanks, Grant.
David Gitz April 27, 2015 at 4:16pm

^ Bump ^

Any ideas? I'm working on a project too. Can't figure out how this code works. Can't do Serial.begin, Can't do digitalRead.

This reply was deleted.

ArduRover User Group

Replies