mavlink comp ids do not need to be the same #4
Description
you have a conditional in prototype.parseChar that requires the component ids to be the same for the message to be emmited, the point of component ids is to keep track of multiple components talking and infact they should be different rather than the same.