-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MESHCOM 4.0 MODE no PACKET RX #230
Comments
hi, do you want to hear and decode Meshcom FW on my FW? with different CR4, SF and BD they wont communicate with each other. There should be at least the same Freq configuration for it. Then is Meshcom with AX-25 encoded data and sended as HEX values? |
Hallo and sorry for delay..... |
changing the parameters to match the MeshCom could be half way to listen to them. does it have a special bytes at start of the packet? |
i dont know if it has a special byte for starting but i could not receive anything from my Meshcom nodes.... ARPS decode workes well. regards Mike dg0opk |
please mike talk directly to him to let us know if he has one or few special bytes to get if this is the reason igate is not decoding MeshCom packets |
found this in the source code....example for EU settings
regards mike |
correction .....the default LORA_PREAMBLE_LENGTH for EU is 32
|
there seems a lot of differences in the way they transmit data and I have no info about the packet format they use. Will try to gather some info about this in the next week. |
Hallo ....
at FIRST... many thanks for your GREAT WORK and SOFTWARE!!
i tried to receive Packets in MESHCOM 4.0 Mode .....
uses SF11 BW 250KHz CODNIG RATE 6 but nothing was on on my local test
APRS in SF12 BW125 CODING RATE 5 woked fine....
MAYBE you can look on IT.....
https://icssw.org/en/grundlegende-spezifikationen/
THANK YOU VERY MUCH
regards and greetings from Mike DG0OPK
The text was updated successfully, but these errors were encountered: