3 replies to this topic

[Kenn Sebesta]

It seems hardware in the loop makes certain modules stop. For instance, I want HiTL to take in sensor data and have my sensor module do actions on the data and return an improved state estimate. While this works in peabody124's SiTL simulation and in real experiments, it doesn't work in HiTL. I'm supposing this is a setting turned on/off somewhere, could someone point me at it?

[hhrhhr]

	    UAVObject::SetFlightAccess(mdata, UAVObject::ACCESS_READONLY);
	    UAVObject::SetGcsAccess(mdata, UAVObject::ACCESS_READWRITE);

http://git.openpilot.org/browse/~br=next/OpenPilot/ground/openpilotgcs/src/plugins/hitlnew/simulator.cpp?hb=true#to250

[Kenn Sebesta]

Thanks, that makes perfect sense now. I thought that was something special on the flight side, I didn't realize it was as easy as setting the metadata. UAVO never cease to amaze me.

[osnwt]

Please note that not all flight modules even check for these metadata flags (for instance, the attitude module on CopterControl didn't until it was fixed for HITLv2).