THANK YOU VERY MUCH
regards and greetings from Mike DG0OPK
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
<!-- github-sync-id:2793345780 -->
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?
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?
<!-- github-comment-id:2596544114 -->
Hallo and sorry for delay.....
I want to use it as RX Monitor , to see whats coming out via RF of my Meshcom Modules.
Your Software has the possibility to lsn only,and free use of LORA parameters but it does not work with the LORA Meshcom parameters.
regards Mike dg0opk
Hallo and sorry for delay.....
I want to use it as RX Monitor , to see whats coming out via RF of my Meshcom Modules.
Your Software has the possibility to lsn only,and free use of LORA parameters but it does not work with the LORA Meshcom parameters.
regards Mike dg0opk
<!-- github-comment-id:2598426080 -->
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?
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?
<!-- github-comment-id:2598625011 -->
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.
Maybe Kurt OE1KBC has the answer?
contact..... e-mail-adress: oe1kbc@icssw.org
should i ask him?
regards Mike dg0opk
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.
Maybe Kurt OE1KBC has the answer?
contact..... e-mail-adress: oe1kbc@icssw.org
should i ask him?
regards Mike dg0opk
<!-- github-comment-id:2598747251 -->
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
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
<!-- github-comment-id:2599789538 -->
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.
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.
<!-- github-comment-id:2623193944 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
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.....
I want to use it as RX Monitor , to see whats coming out via RF of my Meshcom Modules.
Your Software has the possibility to lsn only,and free use of LORA parameters but it does not work with the LORA Meshcom parameters.
regards Mike dg0opk
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.
Maybe Kurt OE1KBC has the answer?
contact..... e-mail-adress: oe1kbc@icssw.org
should i ask him?
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
default: // EU
meshcom_settings.node_freq = RF_FREQUENCY;
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.