i have been getting very strange numbers from my IR sensors. i plug in the flight pack into my funjet and ir1 is -500 or something. i try wiggling wires and unpluging IR and its still crazy. i unplug the flight pack,wait, then plug it back in and then its at around plus or minus 10 like it should be.i tripple check everything and it all looks good. when i went to fly my funjet on thursday the first time i went in to auto1 it spiraled to the left so i recover in manual. check the messages and its the - 500 again. i unplug and plug it in and give it another go. auto1 works great. a couple minutes into the flight i do a pass it crashes into the ground.
i have glued the funjet and gear does not even have a scratch. but i still get the strange values. my PFD jump around crazy even when its "working" and i have my hand under irv. here is a video.
i try to replay a flight, but i am getting this error when i build my airframe with SIM as the target and replay.
CC /home/mecevans/paparazzi3/var/MCE/sim/main_ap.o main_ap.c: In function ‘reporting_task’:
main_ap.c:245: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘double’ main_ap.c:245: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘double’ main_ap.c:245: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘double’
main_ap.c:245: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘double’ main_ap.c:245: warning: forCC /home/mecevans/paparazzi3/var/MCE/sim/datalink.o CC /home/mecevans/paparazzi3/var/MCE/sim//home/mecevans/paparazzi3/sw/airborne/sim/ppm_hw.o
this happens with ALL the other A/C's. i noticed that when you have the modem plugged in when replaying a flight, files get messed up. i cannot play any flights either and i get this over and over.