-
Notifications
You must be signed in to change notification settings - Fork 59
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
Hamshield mini packet transmission size #48
Comments
The AFSK_SerialMessenger app was originally built to support APRS, which has a maximum packet size of 256 bytes. We'll be leaving the official library as is for this reason. It should be possible to update the code to support larger packet sizes, but there will be a lot of bookkeeping variables to changes. In particular, there are a variety of counter variables (like currentByte) in packet.h that are defined as uint8s. Those would need to be changed to larger variable sizes. I haven't tested this, so you may run into some other issues as well. The main limitation probably has less to do with the HamShield library than with hardware. I'm not sure you'll be able to hit 10k chars in a packet if you're running this on an Arduino. The Arduino Uno only has 2k of memory in the first place. If you used a Raspberry Pi, you shouldn't be hardware constrained. For details on that, see here: https://github.com/EnhancedRadioDevices/HamShieldPy (you'll still have to modify the library to get this to use higher packet sizes) |
We observed that the github repository link you sent for the
library/source code is for hamshield mini; we just recently acquired your
hamshield LoRa edition because of the features it posseses that your
hamshield mini doesn't; we would like to confirm if the reply you earlier
sent is applicable to your Lora edition. We also need the github repository
link for the Hanshield LoRa library/source codes
…On Mon, 19 Apr 2021, 4:59 pm Morgan Redfield, ***@***.***> wrote:
The AFSK_SerialMessenger app was originally built to support APRS, which
has a maximum packet size of 256 bytes. We'll be leaving the official
library as is for this reason.
It should be possible to update the code to support larger packet sizes,
but there will be a lot of bookkeeping variables to changes. In particular,
there are a variety of counter variables (like currentByte, readPos,
dataPos) in packet.h that are defined as uint8s. Those would need to be
changed to larger variable sizes. I haven't tested this, so you may run
into some other issues as well.
The main limitation probably has less to do with the HamShield library
than with hardware. I'm not sure you'll be able to hit 10k chars in a
packet if you're running this on an Arduino. The Arduino Uno only has 2k of
memory in the first place. If you used a Raspberry Pi, you shouldn't be
hardware constrained. For details on that, see here:
https://github.com/EnhancedRadioDevices/HamShieldPy (you'll still have to
modify the library to get this to use higher packet sizes)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANUSNPMOT2MZRGDNQ3236G3TJRHPVANCNFSM4VOT2ELQ>
.
|
Also, just recently, we got the raspberry pi zero w integrated with our hamshield mini,' AppSerialController.py Is there an equivalent implementation of your AFSK_SerialMessenger in python for pi zero w? If yes or no, please point us in the right direction. Thanks you very much |
Hello team, I am currently working on a project using the Hamshield mini.
I am exploring the AFSK_SerialMessenger and I noticed a header indicating that I can transmit a message under 254 characters so I have a few questions and they are as follows:
Does the hamshield mini have the capacity to transmit over 10,000 characters at time.
If yes, what and what am I likely to adjust the AFSK_SerialMessenger codes and on the radio(if any) to enable me achieve a fluent transmission of 10,000 text characters or above.
If no, please can you advice me on my other options.
Thanks
The text was updated successfully, but these errors were encountered: