Thanks both.
Regarding hardware issues, I have tried two of the Microchip modules, one at a time and together.
No issue with uplink or downlink in any arrangement at close range.
The antenna used in each case was that supplied with the device and was attached prior to power, as per the instructions.
I have not got any specific RSSI or SNR values but will try to obtain them.
Regarding distances: of course the actual distance is important but I was trying to impart the fact that it was far less that a Km. This would vary depending on actual orientation to the antenna due to factors such as elevation, vegetation etc. However the distance was in the range of between 150m and 300m which appears to be significantly below expectations.
However, back to my original question … does anyone understand if there is a relationship between the two commands “Radio Set Pwr” and “Mac Set Pwridx” on the RN2483 ?
Just look at the console. It is important to know these values, if not is difficult to understand.
according to the RN2483 manual, the latter refers to an array of values defined in the LoRaWAN specification (here). So one sets according to LoRaWAN definitions, the other sets in dB. However, if you do not know RSSI of received packets, it does not make sense to just play with these values…
Thanks again UdLora
I’ve got RSSI and SNR values now and will do some further tests.
I appreciate your point about adjustment of power, but I am trying to ensure I understand if these two values interact in some way e.g. does one take priority over the other somehow ?
I’ve read the spec but it is more to do with how these config parameters have been implemented by Microchip on the RN2483
Thanks LoRaTracker
Yes, it does seem that I have a fault somewhere, but after two different gateways, two end devices, two high gain antennae and a lot of testing I thought I would just ask the community to see if there was someone who has had similar issues and found the “obvious” answer.
I am only using the Microchip dev device “out of the box” at the moment and it clearly works at short range.
I’ll try a completely different location and see if there is an improvement and then try to track down the issue.
I expect the last you use will set the power, at the end you have just one radio chip. Likely, MAC commands are LoRaWAN specific and ensure compliance, radio commands maybe could be used for pure Lora too.
However, do you have the software that runs on the node? check there what is used for setting power… so you will be also sure about the level set as default.
It’s worth checking that you are not over modulating. I once spent a very frustrating afternoon trying to get a WhisperNode to work, only to find that the issue was I was too close to the gateway. Reducing power to minimum solved the problem.
Regarding the two commands, my interpretation is that they are effectively analogous to each other in their effect, however, the the set pwridx command allows the output power to be expressed in units meaningful to the LoraWAN specification. So, if you’re using a LoRaWAN specifically, you would use this command. If you using LoRa MAC (i.e. rolling your own protocol on top of the LoRa modulation technology) then you’d probably use radio setpwr.
Hi LoRaTracker,
Just to mention I had a quick look at your “KISS” paper whilst looking through other docs… interesting.
I see you were in South Wales… at the time.
Do you have a gateway setup in the area ? I could (perhaps) try my end device on your gateway if it is open, as I’m also in South Wales.
Hi Aagin,
all I am doing is “talking” to the device using RealTerm over a USB connection … it seems to be accepting all the commands and works fine at short range.
I see your point, but I’m finding no issues when really close (0 to 10m) (RSSI -87 / SNR 9 / SF 8 / airtime 103mS).
It’s just that performance drops off quickly. Just tried inside the building and only got about 25m (RSSI -126 / SNR -10.5 / SF 11 / airtime 741mS)… but it is an old building with concrete and steel.
I’m going to change location completely and see what happens.
As example, in this moment I have a TTIG gateway indoor 1st floor, and a couple of trackers inside my car, at about 10m (something more). The one with the best antenna floats around -45; the others are around -60.
You should only be using “mac set pwridx” command with TTN. The “radio set pwr” command is only there for testing in static setups, i.e. no protocol, so it will be quickly over-written if the mac layer is active.
It is unlikely that the RN2483 module is damaged, they are quite robust. My guess would either be software configuration or a wrong antenna supplied with the kit. I would trust a random wire antenna better. You could try soldering a 8.6cm wire to one of the kits and see if it makes a difference.
Come to think of it, you mention using a terminal and USB connection to control the Mote. There is a chance your PC is injecting noise over the USB connection. Try reverting to the stock application on the Mote and test in standalone mode with battery power for minimal noise.
I have certainly damadged a fair few SX127xs as fitted on DRF1278F and RFM9x modules over the years since 2015 due in the main to my own carelessness operating them without antennas etc.
The symtoms of damage are normally extreme short range, due to measured power output being almost non-existant.
Thanks JDP… that helps my appreciation of the two power commands.
I’ve ordered some new antennae and new (different) motes to try to appreciate where the problem sits.
Regarding the usb… I only use that for config and then revert to standalone, battery mode… but an interesting observation.
Hi LoRaTracker
Interesting comment, but I cannot find any reference to SX127…though I see your point.
The board I’m using is the microchip DM164138 with the RN2483 on board.
It has a connector in place for the 868 antenna and a through hole for the 433 “wire”.
I have just used it out of the packet… it was meant to be an easy intro !