-
Notifications
You must be signed in to change notification settings - Fork 41
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
Support for RAK 7243 / 2245 Pi hat #27
Comments
Might be related to this thread: https://forum.loraserver.io/t/rak2245-packet-forwarder/4246/2 |
Fixed it by adding a device config variable: |
Spoke to soon, after a few minutes an a restart I started getting "ERROR: Version of calibration firmware not expected, actual:188 expected:2" messages with the above setting. |
Maybe try even lower. I used BTW: If you get LTE working on the gateway in a Balena container, please let us know how. |
Same issue unfortunately, using PIN 11 and your speed: 02.05.19 16:51:19 (+0200) main Frequency plan: EU_863_870 |
Oddly, after about an hour it started working with those settings. I have the version without LTE, so unable to help there, unfortunately. |
If I remember correctly it was the same for mine. It wouldn't work the first few tries, but then after a while the packet forwarder will start up. Using RAK's image it worked ok. The only difference is that their image configures the gpios to talk to the LTE modem. Maybe not configuring the modem has the side effect of interfering with the LoRa concentrator. If you manage to get it working stable, please update us here. |
I have a new RAK7243 gateway (rak2245/RPi3+ based, non-LTE): after I lowered the SPI_SPEED to 1000000 [D(x)] my gateway connected immediately to TTN. Reset pin is 11 as already mentioned. This was not needed with my older trustworthy ISMT Lora Light Gateway (ic880a/RPi3+ (! not the older RPi1)) based; @jpmeijers I can confirm that the reset pin on the ISMT Light Gateways backplane is 29). Will now observe stability/reliability of the RAK7243. @dapendragon whats your impression so fare (service stop/start, reboot, etc.)? @jpmeijers thanks for your work here! |
after a reboot of all of my devices, only the RAK2245 device encounters... 08.06.19 00:34:35 (+0200) main 22:34:35 ERROR: [main] failed to start the concentrator lets see what happens in a few hours... good night. |
interim state: I tried RAKs 2245 hat with a RPi 1 B+ (2014, no wifi, should have no SPI issues) as well with the lates RPi 3 A+. Same result, often "failed to start the concentrator", sometimes even after 30h the concent can not be started. Sometimes it just starts after a couple of re-tries, often not. RAK 2245 seems to be problematic. I have no issues with ISMT ic880a or a balenaFIN-based gateway with RAK831 spi/usp PCIe concentrator (adapted run script). Maybe someone has more luck. |
@Fomi-RAK might be able to help |
I was wondering what it would take to add support for the RAK 7243 Pilot Gateway Pro (running a RAK 2245 Pi Hat under the hood).
I tried the naive approach of reusing this project, but I'm currently stuck on "ERROR: [main] failed to start the concentrator" after having tried various iterations of which reset pin to use.
I'm willing to contribute to get this working, but I need someone to point me in the right direction. :)
The text was updated successfully, but these errors were encountered: