-
Notifications
You must be signed in to change notification settings - Fork 40
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
frequency #7
Comments
Agreed; being limited to integer Mega Hertzes seems pretty coarse.. 😉 My personal taste would be to limit this function to integers arguments. IMO it is best not to introduce floats in an embedded system when not needed. Could make the Fancier would be to use an specialized |
I think this package is not active anymore. I've switched to https://github.com/rust-iot/rust-radio-sx127x and had much more success. My example usage is at https://github.com/pdgilbert/LoRaGPS-rust. There are some issues with it, but those are related to active development moving to |
hi @pdgilbert thanks for getting back to me on this very old issue 😄 Yes, I've had a look at the |
Yes, as a newbie I too have found the lack of examples frustrating. Also, because of the rapid state of development, random examples often work only with old versions of crates and device HALs. In an effort to help and also maintain my own sanity around what I have working and what is broken I started another project https://github.com/pdgilbert/rust-integration-testing with CI at https://github.com/pdgilbert/rust-integration-testing/actions. This is just to keep track of little examples. For awhile I was running it also with release versions of stuff but at the moment it is more focused on dev version. Some |
FREQUENCY in megahertz needs to be a float, not i64, otherwise only the nominal channel can be used, for example, channel 12 in the 915MHz band. Another option might be to leave it integer but in kHz or Hz. Here is a list of channels copied from some python code.
The text was updated successfully, but these errors were encountered: