-
Notifications
You must be signed in to change notification settings - Fork 17
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
maxTxPower on Conduit #12
Comments
Ttnmapper uses packets received, which is not related to transmit power. Do you still have the pre conversion global and local configuration files so these can be compared to the current ones? The parameters in the advanced configuration are used to generate the configuration files for the packet forwarder, once converted you are running the TTN provided configuration which may have different settings. |
Yes. Seems logical. Ok, I can check the results from an other spare Conduit I still have in the box on the shelve. I'll get back on this one after comparing configs. Thx |
Hi I have the same question, how to set up Tx Power on conduit, because original lora-network-server is not running after installing ttn-pkg-fwd |
Tx Power is set by the back-end. When running lora-network-server you are running your own back-end which requires setting the max power. Once connected to TTN the TTN back-end takes care of that. |
Hi Kersing, thanks so much for your immediate answer. |
Look at the github repo for TTN code (github.com/TheThingsNetwork) and documentation (on the main website thethingsnetwork.org) and the TTN forum for additional information. |
Hi there,
Could it be that by disabling the lora-network-server we also did something with the maxTxPower? Since running the installer script on a spare Conduit I lost a lot of coverage with TTN mapper as it seems. I haven't done any other physical changes with this particular setup.
From the multitech advanced lora config there are settings for manipulating the system.
Or am I missing something differently and am I barking up the wrong tree?
great work,
keep it up,
Martijn
The text was updated successfully, but these errors were encountered: