packet:lora
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
packet:lora [2024/08/15 10:09] – 2e0hkd | packet:lora [2025/03/30 15:47] (current) – 2e0hkd | ||
---|---|---|---|
Line 15: | Line 15: | ||
These work completely standalone, but also offer KISS so external APRS clients can be used (for APRS only, not packet, see below!) The iGate firmware makes KISS available on TCP and/or USB-serial, the tracker firmware can do KISS via bluetooth. The tracker does expose a USB-serial port but it is not for KISS and is only for debug output or flashing the device. | These work completely standalone, but also offer KISS so external APRS clients can be used (for APRS only, not packet, see below!) The iGate firmware makes KISS available on TCP and/or USB-serial, the tracker firmware can do KISS via bluetooth. The tracker does expose a USB-serial port but it is not for KISS and is only for debug output or flashing the device. | ||
+ | |||
+ | If you do use the CA2RXU firmware, consider adding it to [[https:// | ||
In the UK, the LoRa APRS frequency and modulation settings are: | In the UK, the LoRa APRS frequency and modulation settings are: | ||
Line 23: | Line 25: | ||
Coding Rate 4/5 (ie. enter " | Coding Rate 4/5 (ie. enter " | ||
- | ==== License | + | ==== Mini how-to ==== |
+ | |||
+ | - Download VS Code | ||
+ | - Install Platformio IDE extension into VS Code | ||
+ | - Follow the iGate or Tracker path below. | ||
+ | |||
+ | === iGate === | ||
+ | |||
+ | An iGate is a " | ||
+ | |||
+ | A 433MHz Lilygo LoRa32 V2.1_1.6 makes a good board for an iGate. | ||
+ | |||
+ | There is web flasher, you can find it [[https:// | ||
+ | |||
+ | - Connect the board to your computer with a USB cable. | ||
+ | - '' | ||
+ | - Optionally replace '' | ||
+ | - Set the following fields, and save the file: | ||
+ | * callsign (SSID is optional) | ||
+ | * wifi.autoAp.powerOff - set to 0 to stop it from spinning up a Wi-Fi AP | ||
+ | * wifi.AP.ssid/ | ||
+ | * beacon.latitude/ | ||
+ | * aprs_is.passcode - enter your callsign on [[https:// | ||
+ | * personalNode - change the URL to include your callsign and feel free to create a page | ||
+ | - Click the Tick button in the bottom bar of VS Code (tooltip is PlatformIO: Build) to check everything builds | ||
+ | - Click the Right arrow in the bottom bar of VS Code (tooltip is PlatformIO: Upload) to upload firmware to the board | ||
+ | - In the left bar of VS Code, click the PlatformIO icon (ant head). | ||
+ | - In the next leftmost bar of VS Code, find Project Tasks (at the top). Expand '' | ||
+ | - Expand Platform, and click Upload Filesystem Image. Another upload will happen, ensure it is successful. | ||
+ | |||
+ | The board should boot and display its IP address from your Wi-Fi on its screen. Navigate to http:// | ||
+ | |||
+ | An iGate is best sited up high, connected to a full size 70cm antenna, e.g. a colinear, dipole, or 5/8ths or quarter wave vertical. | ||
+ | |||
+ | NB Sometimes uploading can fail, in this case try re-plugging or swapping USB port, or plug the board in with its RST button held. | ||
+ | |||
+ | NB If you don't use the recommended file with sensible UK defaults then you will need to set more options to be compatible with UK settings (most importantly, | ||
+ | |||
+ | === Tracker === | ||
+ | |||
+ | A tracker is a device you carry around with you and it sends and receives beacons, messages etc. It can optionally be used with a companion smartphone app (via bluetooth) or PC software (via USB or bluetooth) as a TNC. | ||
+ | |||
+ | A 433MHz Lilygo T-Beam Supreme makes a good board for a tracker. Add a single 18650 cell and a 3D printed case for convenience. | ||
+ | |||
+ | Unlike the iGate, at the time of writing, there is no web flasher, so you'll need to follow the steps, which are similar to the iGate. | ||
+ | |||
+ | - Connect the board to your computer with a USB cable. | ||
+ | - '' | ||
+ | - Set the following fields in '' | ||
+ | * callsign (SSID is optional) | ||
+ | * Remove the second and third beacon configurations (unless you want to have multiple configs available on the tracker, of course...) | ||
+ | * sendBatteryInfo: | ||
+ | * bluetoothType: | ||
+ | * For the UK, specify '' | ||
+ | < | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | }], | ||
+ | </ | ||
+ | - Click the '' | ||
+ | - Click the Tick button in the bottom bar of VS Code (tooltip is PlatformIO: Build) to check everything builds | ||
+ | - Click the Right arrow in the bottom bar of VS Code (tooltip is PlatformIO: Upload) to upload firmware to the board | ||
+ | - In the left bar of VS Code, click the PlatformIO icon (ant head). | ||
+ | - In the next leftmost bar of VS Code, find Project Tasks (at the top). | ||
+ | - Expand General, then Platform, and click Upload Filesystem Image. Another upload will happen, ensure it is successful. | ||
+ | |||
+ | The tracker should boot and start looking for GPS. Your iGate should show a green LED when it receives a frame from your tracker. Your tracker should now show up on [[https:// | ||
+ | |||
+ | APRS.fi have an iPhone app which works with this TNC for beaconing, and also it appears messaging, but this is hidden behind a subscription so I've not tried it. | ||
+ | ==== Licence | ||
If you want to run an unattended Digi that may be subject to 3rd party use (ie. digi'd packets from other people) in the UK, you will need to coordinate with the ETCC for a [[https:// | If you want to run an unattended Digi that may be subject to 3rd party use (ie. digi'd packets from other people) in the UK, you will need to coordinate with the ETCC for a [[https:// | ||
+ | |||
+ | This will be an '' | ||
+ | |||
+ | ===== LoRa-VHF APRS Gateway ===== | ||
+ | |||
+ | See: [[packet: | ||
Line 38: | Line 119: | ||
There are however other options, though these have not yet been tested by OARC members. These are: | There are however other options, though these have not yet been tested by OARC members. These are: | ||
- | * [[https:// | + | * [[https:// |
* [[https:// | * [[https:// | ||
RNode supports many of the same LoRa hardware options as the APRS firmware, but not all (it does seem to be actively worked on though), and even supports home brew hardware builds. It can also do a lot of other things as well as packet radio, not all amateur radio related. | RNode supports many of the same LoRa hardware options as the APRS firmware, but not all (it does seem to be actively worked on though), and even supports home brew hardware builds. It can also do a lot of other things as well as packet radio, not all amateur radio related. | ||
+ | |||
+ | |||
+ | ==== RNode TNC ==== | ||
+ | |||
+ | RNode firmware can be installed using the rnodeconf command included in the rns python package, which can be installed with pip: | ||
+ | |||
+ | < | ||
+ | pip install rns | ||
+ | </ | ||
+ | |||
+ | This provides the rnodeconf command. Install firmware by running: | ||
+ | |||
+ | < | ||
+ | rnodeconf --autoinstall | ||
+ | </ | ||
+ | |||
+ | This will prompt you to plug in your device to USB, and select the virtual COM port it is on. Select the correct model and variant of the hardware you have when prompted, and it will install firmware. | ||
+ | |||
+ | Note that as of 2024-08-14, 2E0HKD has noticed that selecting " | ||
+ | |||
+ | Once installed, the device can be put into packet TNC mode with a command like (change for your COM port, works with linux ports like "/ | ||
+ | |||
+ | < | ||
+ | rnodeconf -T --freq 439912500 --bw 125000 | ||
+ | </ | ||
+ | |||
+ | NOTE: this example is the LoRa APRS frequency, but limit your use of this in the real world so as not to crowd out that frequency with non-APRS traffic. Remember LoRa is spread spectrum and can use a wide bandwidth, although alternative settings can lower this bandwidth requirement. | ||
+ | |||
+ | You can now use the COM port for serial KISS (115200 baud was seen to work on Windows). ACKMODE does not seem to be supported at this time (2024-08). | ||
+ | |||
+ | This command will have to be run each time the device is plugged in to put it back into TNC mode. | ||
+ | |||
+ | It is possible to choose lower bandwidths to fit in narrower channels, but the bitrate drops (or even higher bandwidth and faster!), so creativity in different bandplans is feasible. | ||
===== Other Resources ===== | ===== Other Resources ===== | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// |
packet/lora.1723716581.txt.gz · Last modified: 2024/08/15 10:09 by 2e0hkd