-
Notifications
You must be signed in to change notification settings - Fork 148
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
Fixed wrong frequency (json) & upload for TTN V3 #72
base: master
Are you sure you want to change the base?
Conversation
Workaround for wrong frequency in json file. Will also solve the problem with upload for TTN V3. Tested with 868 MHz.This is the first time ever I upload or commend in gitub. Hope I did it wright.
Workaround for wrong frequency in json file. Will also solve the problem with upload for TTN V3. Tested with 868 MHz.This is the first time ever I upload or commend in gitub. Hope I did it wright.
Nice finding ! Did you try to simply change from doc["freq"] = "" + (freqs[gwayConfig.ch].upFreq / 1000000); to doc["freq"] = "" + (freqs[gwayConfig.ch].upFreq / 1000000.0); ? |
Thank you for your fast answer. I tried your fix for both lines: doc["freq"] = "" + (freqs[gwayConfig.ch].upFreq / 1000000.0); But as example the frequency for channel 0 was 868099975 so it did not fix the issue. |
Thanks for trying ! |
Thanks a lot :-) It is really a great project and it should also live with stack V3 :-) |
src/loraModem.h
Outdated
// TTN defines an additional channel at 869.525 MHz using SF9 for class B. Not used | ||
{ 868100000, 125, 7, 12, 868100000, 125, 7, 12, "868.100"}, // Channel 0, 868.1 MHz/125 primary | ||
{ 868300000, 125, 7, 12, 868300000, 125, 7, 12, "868.300"}, // Channel 1, 868.3 MHz/125 mandatory and (SF7BW250) | ||
{ 868500000, 125, 7, 12, 868500000, 125, 7, 12, "868.800"}, // Channel 2, 868.5 MHz/125 mandatory |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be here 868.500?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think has to be 868.500? Which value should be changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"868.800"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, now I see - typing error! I will correct it - thanks!
Thanks for this great project and thanks for this fix. Node: Gateway: In the OTAA case I try to trace it from TTN Cloud to 1ch Gateway to Node Serial Log. In the TTN Cloud the Downlink is send to the gateway: In the Gateway I can see the transfer: But in the Node Serial log there is nothing arrived: Any ideas? |
@itsygithub
and does not require to change |
// ftoa((double)freqs[gwayConfig.ch].upFreq / 1000000, cfreq, 6); This is working for me. |
To fix precision for frequency things4u#72
Workaround for wrong frequency in json file. Will also solve the problem with upload for TTN V3. Tested with 868 MHz.This is the first time ever I upload or commend in gitub. Hope I did it wright.