Send a separate Discovery packet for P2 since some clients are lookin… #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…g for a 60 byte packet.
Hi Vasiliy, I am helping to work on a new ANAN board that uses a Xilinx FPGA and a
CM4 Raspberry PI module. The main developer has implemented the Protocol 2 in a
way that strictly looks for a discovery packet of 60 bytes. This is actually what is in the
protocol documentation. Other Hermes/Orion boards are not strictly looking at packet
size and work fine with the 63 bytes.
I have tested this not only on the new ANAN board (Saturn) but also on other Hermes both
P1 and P2.
BTW, Thetis also sends both a P1 and P2 discovery packet.