I'm wondering if anyone can answer a simple question related to the MAVLink messages sent from the APM. I am running a program that uses a XBEE via USB to monitor the messages sent from the APM. When I run this program, using an APM1, I see over 10 different messages sent from the APM. These messages are sent from pwr on, until the APM is powered down. Moreover, only heartbeat messages are sent until the APM is initialized. But, once initialized, the APM sends many different messages.
The problem comes about when I try to do the same using the APM2 hardware. The APM2 will only send out heartbeat messages (id#0) and an occasional STATUSTEXT message (id#253). Why doesn't the APM2 send just as many messages as the APM1?? Is the APM2 waiting for a response before it starts sending all of the messages that the APM1 will send? I'm deadlocked at this point in my program, and need to be able to use the APM2 hardware while monitoring the mavlink messages. Does anyone know why the APM2 is not sending these messages?