On 30/01/2016 23:26, Bill Somerville wrote: > The error seems to be saying that you have sent a message with a higher > schema number than WSJT-X was advertising that it can handle. What did > the first Heartbeat message have in the "Maximum schema number" field? Hi again Laurie,
I should add that the WSJT-X code before network message schema negotiation was added did not have a "Maximum schema number" field in the Heartbeat message. This should be taken as schema number 2 is the highest supported (schema 1 is broken and is not used in the field). This probably needs explicit documentation as it is only implied by looking at the schema 2 version of the code, I will add a note to the NetworkMessage.hpp header. Note also that because the network message protocol is many to many topology; it is always possible that a new node may arrive that does not support the currently negotiated schema. This is OK but all other nodes must always be prepared to accept a lower than negotiated schema number and must stick to the lowered schema number until they are restarted. 73 Bill G4WJS. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
