piinthesky/lora-gateway

LoRa gateway to Habitat

lora-gateway's Issues

Integrating lora-gateway as an option to adsb-receiver project

The adsb-receiver project is a set of scripts/rasperbian image to package up various ADS-B data decoders and feeders, which is now expanding to add support for other similar protocols such as the Open Glider Networks FLARM implementation.

So I just wanted to check if your happy for the HAB lora-gateway to be added as an option to install as part of the adsb-receiver project?

Just to confirm I'm not suggesting integrating or sharing data between these various applications, rather to maximise the value of receivers that may currently be deployed for a single application by making it easy to add other applications...

Especially as there may be less motivation for the user to spent time reading install guides for an application other than why they set up the receiver in the first place, but hopefully there is enough in common between enthusiasts of all forms of flying objects to make it worthwhile :)

Change Mode from keyboard ?

Dave would it be possible to add an extra Keystroke to allow changing modes on the fly ?
Thinking "m" & "M" to toggle thru the modes available for each channel.
On occasions when the Mode is not known, it would save a lot of editing and restarting too find the match!
Perhaps it would also be possible to create a table of Modes defined in the config file or at least the define's rather than being held in the actual code itself ?

Interactive Features

So I have rewired my Lora HAT and it appears to be detected by the gateway binary; however the 'Interactive Features' mentioned in the README do not seem to be functional...

Is the expectation that, as per the docs, pressing the 'q' key should result in the gateway exiting?

LoRa Habitat and SSDV Gateway by M0RPI, M0RJX - V1.8.6

Channel 0 434.451.0 MHz
Implicit, 20.80, SF6, EC4:5

AFC

Tracker = 'hostname'
Channel 0 frequency set to 434.451MHz
LoRa Channel 0 DIO0=31 DIO5=26

Telemetry logging does not show which module was receiving

So, with 2 different antenna's and 2 modules I am not able to compare the results.

Can you add channel0 and / or channel1 to the telemetry.txt pse ?

73'
Ben

Stop overwriting of SSDV files

In V1.8.19 and possibly earlier, if the SSDV image count wraps from 255 (the maximum SSDV utilises) back to 0, the LoRa Gateway ssdv folder over-writes older images with newer images with the same index count. Could code be added to avoid this, and retain all received images? Perhaps this could be achieved by creating subfolders for each cycle through the SSDV image count on a given day or by prefixing/suffixing the image file name with date and/or time. Obviously, other approaches exist to resolve this behaviour.

Thanks for all the effort maintaining this excellent application.

Steve Hyde - hyde00001

ambiguous variables

Can you confirm the permitted values for the following variables which have =0 in the gateway-example.txt

implicit_0=0
lowopt_0=0

But show Y/N answers in the README.md

Implicit_=<Y/N>. e.g. Implicit_0=Y
lowopt_=<Y/N>. Enables or disables low data rate optimization.

Thanks

DIO5_0=-1 with XL1278-SMT causes 100% CPU usage

I ended up with a batch of XL1278-SMT modules so figured I'd try and protoboard a LoRa gateway.

After a bit of faffing with pin numbers, it all seems to work initially, but then it seems to hang (no interactive keystrokes work except Ctrl-C; 100% CPU usage). My additional debug info shows it's correctly reading the SX1278 module version, etc. It seems to go wrong when it starts trying to receive.

 $ sudo gdb
GNU gdb (Raspbian 8.2.1-2) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) attach 680
Attaching to process 680
[New LWP 685]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
0x0002530c in startReceiving ()
(gdb) info threads
  Id   Target Id                             Frame
* 1    Thread 0x75f15520 (LWP 680) "gateway" 0x0002530c in startReceiving ()
  2    Thread 0x75f14230 (LWP 685) "gateway" __GI___poll (timeout=-1, nfds=1,
    fds=0x75f13c10) at ../sysdeps/unix/sysv/linux/poll.c:29
(gdb) bt
#0  0x0002530c in startReceiving ()
#1  0x0002780c in setupRFM98 ()
#2  0x00012320 in main ()
(gdb) thread 2
[Switching to thread 2 (Thread 0x75f14230 (LWP 685))]
#0  __GI___poll (timeout=-1, nfds=1, fds=0x75f13c10)
    at ../sysdeps/unix/sysv/linux/poll.c:29
29      ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb) bt
#0  __GI___poll (timeout=-1, nfds=1, fds=0x75f13c10)
    at ../sysdeps/unix/sysv/linux/poll.c:29
#1  __GI___poll (fds=0x75f13c10, nfds=1, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:26
#2  0x76e62690 in waitForInterrupt () from /lib/libwiringPi.so
#3  0x76e62730 in interruptHandler () from /lib/libwiringPi.so
#4  0x76d40494 in start_thread (arg=0x75f14230) at pthread_create.c:486
#5  0x76cc3578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73
   from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

I'm not great gdb user, but I think it's stuck waiting for an interrupt. I can manually short DIO0 to ground to get it out of this state, but that doesn't really fix the problem.

Has anyone else tried to use a XL1278-SMT module rather than the RFM98 or DRF1278F, etc.? It's got an XS1278 on board, so it should 'just work'. DIO5 is an edge connector rather than through-hole so there's no chance of using that without a breakout.

It's quite possibly my wiring given I'm dead-bugging 0.05" pitch, but the fact I'm able to read at least the version register gives me hope.

gateway.txt:

tracker=[removed]
Latitude=[removed]
Longitude=[removed]
Antenna=A tiny bit of wire

##### Config Options #####
EnableHabitat=Y
EnableSSDV=Y
JPGFolder=ssdv
LogTelemetry=Y
LogPackets=Y
CallingTimeout=60
ServerPort=6004
#SMSFolder=./
EnableDev=N

#NetworkLED=22
#InternetLED=23
#ActivityLED_0=21
#ActivityLED_1=29

##### Config CE0 #####
frequency_0=433.650
mode_0=5
AFC_0=Y
#bandwidth_0=125K
#implicit_0=0
#coding_0=5
#sf_0=8
#lowopt_0=0
#power_0=255
DIO0_0=3
DIO5_0=-1

PPM correction.

Could you add a simple test to output a carrier on 434.leo so that the modules can be checked against a Ham Radio and a PPM offset could be put back into the Gateway ? That would help at the narrower bandwidths where the drift is much less than the initial offset.

Received HABpack Corruption when using 2x LoRa Modules fitted

eg.

"$$1900,49,10:05:13,50.183739,-5.802828,7,1,2e534",G8KNN
"$$1900,49,10:05:13,50.183739,-5.802828,27714,14,1.4385349","GOONHILLY,0x17_pi,M0EYT-BH"
...
"$$1900,2928,10:02:21,50.17802,-5.763629,35689,14,1.4418364","M0NRD,GOONHILLY,0x17_pi,M0EYT-BH,M0RPI/5"
"$$1900,2928,10:02:21,50.17802,-5.763629,0,2,3c999",G8KNN
...
"$$1900,2920,10:01:55,50.17629,-5.757079,35558,14,1.4199b01","M0NRD,GOONHILLY,M0RPI/5,M0EYT-BH,0x17_pi"
"$$1900,2920,10:01:55,50.17629,-5.757079,1,2,3654e",G8KNN

Very likely due to the author not considering that some users have 2x LoRa Modules fitted.

lowopt_ settings

Doesn't appear to function any Y/N/0/1 makes no difference.

Enabling SSDV

The Github README.md doesn't mention installing SSDV to store images locally while the UKHAS wiki https://ukhas.org.uk/guides:lora_tracking_guide?s[]=lora does. It would probably help fools like me to update the Github instructions... Many thanks for all the effort you put into this.

MaxAFCStep may be used uninitialised

I may be missing something, but If I don`t set MaxAFCstep in config, I am not going to be able to use calling mode to correct drifty payloads.

nice to have: seperate tracker ID's with 2 receiver modules

Hi,
If possibly, could you add separate tracker_0 and tracker_1 ID's for when having two receivers modules with different antenna's ?

Kind regards,
Ben

Dragino Lora/GPS HAT v1.4 RPI v3

Hi,

Can anyone tell me how to create a lora node from my RPI and send data to the dutch KPN network?

tnx

UI displays when launched, and then program immediately closes.

As per the issue title, when I launch gateway I see the blue UI (but without any information displayed in the blue section, aside from 'AFC'). The program then closes within 1 second of the UI being visible.

I am running on a Raspberry Pi 3 with the latest 32-bit Bookworm OS. I'm using an Uputronics LoRa HAT with a 433Mhz RFM98 in CE1. gateway is version 1.10.6.

Config is shown below:

`##### Your details #####

tracker=Me
Latitude=53.8
Longitude1.56
Radio=Uptronics LoRa HAT
Antenna=Diamond X-50

Config Options

EnableSondehub=Y
EnableSSDV=Y
JPGFolder=ssdv
LogTelemetry=Y
LogPackets=Y
CallingTimeout=60
ServerPort=6004

NetworkLED=22
InternetLED=23
ActivityLED_0=21
ActivityLED_1=29

Config CE0

#frequency_0=434.250
#mode_0=1
#AFC_0=Y
#bandwidth_0=125K
#implicit_0=0
#coding_0=5
#sf_0=8
#lowopt_0=0
#power_0=255
#DIO0_0=31
#DIO5_0=26
#UplinkTime_0=2
#UplinkCycle_0=60

Config CE1

frequency_1=433.650
mode_1=5
AFC_1=Y
bandwidth_1=125K
implicit_1=0
coding_1=5
sf_1=8
lowopt_1=0
power_1=255
DIO0_1=6
DIO5_1=5
UplinkTime_1=5
UplinkCycle_1=60

#EnableMQTT=Y
#MQTTHost=mqtt_host
#MQTTPort=1883
#MQTTUser=mqtt_user
#MQTTPass=mqtt_password
#MQTTClient=mqtt_client_name
#MQTTTopic=topic_name

#DumpBuffer=Y
#DumpFile=./LORA_dump
`

Incorrect (un-modified) frequency shown when closing the help dialog.

Steps to reproduce:

• Open lora-gateway (eg. on 434.450)
• Press 'd'/'D' twice to tune upwards 2 KHz (eg. to 434.452)
• Press 'h' to open help dialog
• Press any key to close help dialog
• Bug: Original frequency is displayed (eg. 434.450), not tuned frequency.
• Press 'c'/'C' to tune downwards 1 KHz, this will be applied to the actual frequency, not the displayed frequency (eg. 434.451 is now shown)

LoRa Gatewau needs UKHAS CRC checks

As allready done in Hab Base. the LoRa Gateway would be better of with UKHAS CRC checks too

Thanks,

Ben

Excessive CPU usage.

habitat.c and ssdv.c both need to sleep briefly when there are no packets to upload.

New Feature: Additional metadata logging

Would it be possible to expand the logging info. possibly using an additional config. parameter say;
TelemetryMetadata=[Y/N]
The data to consist of modem config., recieve metadata and raw telemetry.
Channel, Frequency, Imp/Exp, Bandwidth, SF, EC, LDRO on/off, Recieve time, AFC, RSSI, SNR, "raw data"
e.g.
0,434.2950MHz,Explicit,20.8k,SF8,EC4:6,LDRO,201508031408,-0.3Khz,-100,20,"Telemetry"

This would then allow much easier understanding of the performance of a given link after the event.

Sondehub HTTP 202 error

Hi, after starting the gateway, the following error appears after some time
"Unexpected HTTP response 202 for URL 'https://api.v2.sondehub.org/amateur/telemetry'"

But error.txt file contains error 400
Example: 21:20:22: 400 response to: [{"software_name": "LoRa Gateway","software_version": "V1.10.0","uploader_callsign": "TrEsLora868","time_received": "2023-08-18T19:20:22Z","payload_callsign": "TrEs2Lora868","datetime":"2023-08-18T21:19:22Z","lat": 51.24919,"lon": 6.18008,"alt": 48,"frequency": 868.6625,"modulation": "LoRa Mode 1","snr": 7,"rssi": -55,"raw": "$$TrEs2Lora868,173,21:19:22,51.24919,6.18008,00048,12,40.6,0.0,0.000,0123456A9P*70F8","sats":12,"temp":40.6,"batt":0.0,"uploader_position": [ 51.366, 6.413, 0],"uploader_antenna": "868_Self_Construction"}]

The gateway has normal internet, because the photos are transferred correctly to my ftp-server
and ping api.v2.sondehub.org also works correctly.

I attach errors.txt telemetry.txt packets.txt and gateway.txt.
Also attach screenshot showing gateway with error 202 and ping to api.

errors.txt
packets.txt
telemetry.txt
gateway.txt

Want to start a new flight in two weeks on 2023/09/01 :-)
Oliver

Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'

Hello,

In v1.9.1 I get, after some time of correctly uploading to Sondehub Amateur, a HTTP response 400. This error keeps rolling over the screen.

So basically, the software is uploading just fine and then after some time I get this error and I need to restart as the error keeps on scrolling over the screen.

Not sure if it is me, the software or sondehub amateur.

See screenshot: https://drive.google.com/file/d/1OuMVPzjV9Tyjx-lXQRKAFpnRxq_NH2oU/view?usp=sharing

Thanks,

Roel.

lora-gateway v1.10.3 uploads tons of packets for each received telemetry packet

As soon as one listener running v 1.10.3 receives a (valid) lora packet hundreds of uploads take place towards the api.v2.sondehub

Tried to bypass the error checking by disabling line 103 , 104 and 144. Does not make a change, as soon as gateway receives a lora packet the upload goes sky high.
errors.txt removed before starting and no errors.txt is created.

Tried to find if either sondehub messes up by enabling a network tool on the pi running lora-gateway, but as soon as one packet is received the number of bytes sent to the IP address which matches the api.v2.sondehub.org goes up a lot , I stopped the gateway when 6 similair connections happened which each where good for over 6000 bytes being sent to the API.

I have not the knowledge to find out why the upload continuous

One radio amateur had saved a local copy of 1.10.0 and switched to that version, which only uploads once after each packet.

getting a compilation error...

... with a 2015-05-05-raspbian-wheezy (sudo apt-get update sudo apt-get upgrade) install on a model a+ equipped with a pits lora expansion board:

pi@pi ~/lora-gateway $ make
gcc -Wall -g -O2 -o gateway.o -c gateway.c
gateway.c:19:20: fatal error: curses.h: No such file or directory
compilation terminated.
makefile:10: recipe for target 'gateway.o' failed
make: *** [gateway.o] Error 1

LoRa gateway on OpenWRT ?

It will be nice to have this LoRa gateway port on OpenWRT where we have connect HamNET network on 2.3/5.8 Ghz with telemetry network (weather station etc) base on LoRa

Support for Dragino Lora/GPS Raspberry Pi HAT

While it looks like there may be some wiring challenges, it would be useful to confirm if the Dragino Lora/GPS Hat will work out of the box with this project?

http://wiki.dragino.com/index.php?title=Lora/GPS_HAT

How many end-nodes can be connected

I can not see from here: http://www.hoperf.com/rf/lora/RFM98W.htm which Semtech transceiver this module integrates. I guess it is a custom chip with Semtech IP core.

Anyway, as I understand, for LoRa GW we need:

1. Concatenator - SX1301:
   http://www.semtech.com/wireless-rf/rf-t ... rs/sx1301/
2. Transcaiver - SX1276:
   http://www.semtech.com/wireless-rf/rf-t ... rs/sx1276/
3. I/Q modulator/demodulator - SX1257:
   http://www.semtech.com/wireless-rf/rf-t ... ers/sx1257

How come that this soultion does not need Concatenator and/or I/Q modulator?

How many clinets (end-nodes) can be connected to a GW like this?

Lots of: "Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'" errors

Hi

I have just upgraded (by moving the old install out the way and doing a fresh install), copied over my gateway.txt, added the "EnableSondehub=Y" entry and I am getting lots of errors:

Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
21:10:46 Ch0: $$KW01,277,20:10:44,52.32273,-0.70620,00093,0,0,5,21.7,3.898,0.66,0.00000,0.00000,0.0,0,-62,6,2,N*B44C
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry' 
21:10:47 Ch0: SSDV Packet, Callsign KW01, Image 38, Packet 46
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
21:10:49 Ch0: $$KW01,278,20:10:47,52.32273,-0.70621,00092,0,0,5,21.8,3.898,0.66,0.00000,0.00000,0.0,0,-62,6,2,N*7226
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
21:10:50 Ch0: SSDV Packet, Callsign KW01, Image 38, Packet 47
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry' 
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
21:10:52 Ch0: $$KW01,279,20:10:50,52.32275,-0.70622,00092,0,0,5,21.8,3.898,0.66,0.00000,0.00000,0.0,0,-62,6,2,N*9E92
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'
Unexpected HTTP response 400 for URL 'https://api.v2.sondehub.org/amateur/telemetry'

My full gateway.txt is:

##### Your details #####
tracker=G7PMO_PiRx
Latitude=52.322
Longitude=-0.706
Radio=LoRa
Antenna=Colinear

##### Config Options #####
EnableHabitat=Y
EnableSondehub=Y
EnableSSDV=Y
JPGFolder=ssdv
LogTelemetry=Y
LogPackets=Y
CallingTimeout=120
ServerPort=6004
#SMSFolder=./
EnableDev=N

##### Config CE0 #####
#frequency_0=434.650
#frequency_0=434.712
frequency_0=434.718
mode_0=1
AFC_0=N
DIO0_0=3
DIO5_0=26

#bandwidth_0=125K
#implicit_0=0
#coding_0=5
#sf_0=8
#lowopt_0=0
# Power PA_MAX_UK = 0x88 = 136
# Power PA_MAX_BOOST = 0x8F = 143
power_0=136

UplinkTime_0=2
UplinkCycle_0=60
UplinkFrequency_0=434.737
UplinkMode_0=6
SSDVUplink_0=Y

## Callingmode is 433.650 mode 5

##### Config CE1 #####
#frequency_1=869.850
#frequency_1=433.650
frequency_1=434.708
mode_1=1
AFC_1=N
DIO0_1=6
DIO5_1=25

#bandwidth_1=125K
#implicit_1=0
#coding_1=5
#sf_1=8
#lowopt_1=0
#power_1=136

#UplinkTime_1=5
#UplinkCycle_1=60

Any help appretiated.

Thanks very much
Kevin

RSSI calculated value ?

Dave, I've noticed in the code several places where;
"readRegister(Channel, REG_PACKET_RSSI) - 157)"
but in another place its
"readRegister(Channel, REG_PACKET_RSSI) - 137)"
The latter corresponds with the manual section
"5.5.5. RSSI in LoRaTM Mode
The RSSI values reported by the LoRaTM modem differ from those expressed by the FSK/OOK modem. The following formula shows the method used to interpret the LoRaTM RSSI values.
R SSI[dB m ] = –137 + RSSI"

Is it me or should they all be -137 as opposed to -157 ?
Geoff

Michrochip RN2483 Compatibility

Hi all,

I am working on LoRa RN 2483 -raspberry pi c 2011 gateway and I have to set server ip and ports. But on the instructions of semtech network server gateway settings, there are files such as sys_config or global_config but I do not have them on raspberry so I download packet forwarder to get that files. But on the cooking-hacks site where I have instructions for raspberry site, they do not have such instructions and no mention about packet forwarder nor lora gateway application. Do you have any suggestion? Can I use this code for michrochip RN 2483 also?

I have arduPi lib and LoRaWAN lib so far.And will try to connect OTAA join.

Thanks in advance...

Get parity error of Hamming decoding

Did you know how to get parity error result when Hamming(6,4) or Hamming(5,4)? In your implementation, you don't implement to report parity error result to the user when Hamming(6,4) or Hamming(5,4). So in the commodity LoRa nodes, is there a way to get the parity error when Hamming(6,4) or Hamming(5,4)? I look forward to hearing from you. Thanks a lot.

Add documentation for "EnableDev" property on settings file

Can anyone explain what does "EnableDev" property defined on "gateway-sample.txt" configuration file?

Option to run without ncurses

As running nurses based code and in particular ensuring it starts at boot time, which typically requires the use of 'screen', it would be great if it was possible to have an option to start the gateway in a non-ncurses mode?

Perhaps albeit at the expense of the interactive options this would be useful to assist with integrating this into other projects... Is this something that could be considered?

Thanks

To include Listener frequency

To add the Listener frequency for each port in the "listener_telemetry" and/or"listener_information" fields. This would allow identification of the freq. in use by payloads that are not well documented / announced in advance via the IRC robot functions.

Uplink Messages - send/receive using LoRa Expansion Boards?

Hello! Thank you for all the great work on such an interesting topic.

I recently purchased a couple of the Uputronics Raspberry Pi+ LoRa Expansion Boards (HAB-LORA-4N) to use as receivers in support of a local Amateur Radio Operator / School Teacher who has conducted several successfull HAB flights.

I did not realize that these boards were actually TRANSCEIVERS, not just receivers. What a nice surprise!

After configuring the proper settings to uplink SMS messages, I verified with an SDR that the devices were absolutely transmitting on the specified frequency.

While I see reference to receiving SMS messages in the PITS repository, is there any way other than purchasing a full tracker unit to receive & decode these uplink messages? I have two of the LoRa Expansion boards, but when one is configured as receive-only, all it displays when the other unit transmits an uplink message is: "Unknown packet type is 23h, RSSI -164"

Is it possible to communicate in any usable way between two of these LoRa Expansion Boards since they are in fact transceivers?

Thanks!

-Scott, K4KDR

Gateway Pi showing received data in gibberish

Hi all, I am sending data from a RFM98 (attached to an ESP32) to the other RFM98 attached to a Raspberry Pi 4b running LoRa gateway. The sending module is using arduino-lora.

The Pi is receiving the data but it's showing an incorrectly formatted string which looks like it's not been decoded correctly:

Not sure what the issue could be. Here's my sending code for reference:

#include <SPI.h>
#include <LoRa.h>

int counter = 0;

void setup() {
  Serial.begin(9600);
  while (!Serial);
  LoRa.setPins(4, 2, 15);
  LoRa.setSignalBandwidth(125E3);
  LoRa.setCodingRate4(7);
  LoRa.setSpreadingFactor(7);
  LoRa.enableCrc();

  if (!LoRa.begin(434E6)) {
    Serial.println("Starting LoRa failed!");
    while (1);
  }
}

void loop() {
  Serial.print("Sending packet: ");
  Serial.println(counter);

  LoRa.beginPacket();
  LoRa.print("$$hadie,");
  LoRa.print(counter);
  LoRa.print(",10:42:10,53.786244,-2.290401,27799.3,1:10\n");
  LoRa.endPacket();

  counter++;

  delay(4000);
}

Unable to install dependencies and make

I'm trying to install PiInTheSky on an RPi-II, but I ran in 2 problems.

Trying to install de dependencies I get:
pi@Maarten-pi:~ $ sudo apt-get install git wiringpi libcurl4-openssl-dev libncurses5-dev ssdv
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ssdv

Ignoring the earlier error I get with the make:
habitat.c:17:23: fatal error: curl/curl.h: No such file or directory
#include <curl/curl.h>

Thanks for all the works sofar, Maarten

No telnet service?

Hello, i watched ur YouTube video but in code i can't find the HAP Port. Was this an experimental Feature, will this merged with the main code?

https://www.youtube.com/watch?v=zq7Abui3Lds