I’m working on a device that uses a Lambda62 module (868 MHz). This module is built with a SX1262 and I have modified lora_device_lib to adapt this library to an ATmega1284. Library has been modified also to run with a module that doesn’t use IRQ. Library runs as expected and my device can join a LoRaWAN 1.1 network.
I have seen that Tx power is very low. At 1 m, my LoRaWAN gateway shows RSSI=-60 dBm for a Tx Power set to 14 dBm. If Tx Power if set to 0 dBm, gateway receives a signal with RSSI=-75 dBm. If distance between device and gateway is greater that 40 m, no signal is received by gateway (!).
Thus, I have checked my schematic, my routage and library. Dialog between CPU and Lambda62 is for example:
I have done some measurements. When lambda62 sends a packet at 14 dBm, input current is about 42 mA (sleep : I=0,6mA) for a 3V3 power supply. Datasheet indicates 45 mA for a 14 dBm output power, thus, I’m pretty sure that SX1262 is correctly driven. In a second time, I have disconnected pin 1 (RF output) from PCB and I have soldered a 50R coaxial cable to directly connect a level-meter (Rhode & Schwarz URV35) at RF output. Result : when lambda62 is configured to transmit a packet at max power (14 dBm in EU868), level-meter indicates… -12 dBm !
I have tested three different lambda62 modules with the same results. I suppose I have done a mistake somewhere but I’m unable to fix it.
However, the 26db loss indicated by the R&S puts me in mind of another problem; where I have seen static damage in the past which has been enough to degrade if not fully kill device, either LoRa device or the rf switch, I have noted signal degradation or around -25 to -45db. Looks like you are into this so have my suspicions…
Am not familiar with that specific module so cant comment on actual programming/setup or overall ESD sensitivity…
Depending on what SF you use to transmit, the output-signal is a short pulse. I am not sure what is displayed by the URV35 when receiving pulses of a few 10ms.
There seams to be some kind of resonator between the module and the antenna. Is this device still ok?
Then suspicion falls on the antenna…what model used? Connector type? As @wolfp calls out your schematic calls out a strange version. 20-30db loss also common if mixing male/female sma’s etc with female to female only giving weak capacitive coupling…
… but that would not explain poor direct coupled power measurement…(if done right!)
I think that device works as expected as I have the same result with two different modules. This morning, I have tested another one (direct connection to level-meter or lambda/2 antenna). Still the same result.
LoRaWAN is configured to use SF8 and I don’t use antenna, I have directly connected module RF output to a level-meter. I have done this kind of measurement as RSSI returned by my base station was very low (30 dB lower than expected). Thus, I have tried to confirm that my modules don’t emit 14 dBm…
That module has an RF switch to select transmit vs receive path, Id expect a bit more loss with it set wrong but make sure you are correctly driving it.
What’s sad is that the SX1262 has a mode where a DIO output could do so automatically, and the switch chip has a single control signal mode, but the way that module is designed I think you’ll need a tinylogic inverter. Or just use a processor GPIO.
Study the module data sheet internal schematic and then get the one for the RF switch chip whose identity is given in the module data sheet.
I’m pretty sure I correctly drive this RF switch. Unfortunately, I don’t have internal schematic of this module (schematic in lambda62 datasheet isn’t module schematic as it contains a PE4259 RF switch).
RFsolutions support answered a long time ago:
The PE4259 is not the antenna switch that is used in the LAMBDA modules. It’s an AS213-92LF and the only way to use 1 I/O to operate the switch would be to use a transistor circuit to invert the signal to one of the IC inputs.
I don’t use a transistor, I have routed a 74LVC1G04.
That’s rather unfortunate if the data sheet shows the wrong RF switch.
One way to verify you’re correctly operating whatever is there is to configure the transmit power to a minimum for safety, and then try transmitting with both what you consider to be the right setting, vs what you consider to be the wrong one. Do the same for the receive path - set aside expectations and figure out what gives optimal performance.
You could also see if there’s setup detail in the FCC test report… it’s required to be there, though of course that doesn’t mean it is.
Ah another possibility… have you run the modules without ant? If so the energy reflects back into front end potentially damaging/degrading performance… other than the comments noted above wrt rf switch this is another district possibility. Please make sure you have ant connected or at least a 50 ohm dummy load or test instrument if /when powered…
To measure TX power with (most) power meters you need to provide a packet that lasts maybe a second or two, so set up a test transmit of SF12, BW125000 and maybe 64 bytes. Set TX power to say 0dBm in case you do something wrong.
And since you reported the Gateway does see the packets at some point, did the node join to TTN OK ?
Gateway sees packets and node can join network. But gateway reports a RSSI 30 dB lower than expected. Of course, I never try to emit without antenna or a 50R load.
If you have more than one module, I would be testing them module to module, start transmitting at 14dBm say, then reduce the TX power 1dBm at a time and see if the RSSI on another module drops accordingly.
RSSI returned by base station is -112 dBm, but now, device returns a lower RSSI but a higher SNR. Of course, I have redone these measurements to be sure.
