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
Failed to set SX1250_0 in STANDBY_RC mode #67
Comments
The RAK2287 has its own firmware designed to work with the board described here. When using the sx1302_hal with the CoreCell board (PCB_E539V03A, user guide here), additional parameters are needed for the USB version with MCU mounted. Since the RAK2287 concentrator also has a MCU, try the following command instead: |
I have the same problem with lora concentrator module RAK2287. Sometimes it works ok after power cycle..I also noticed switching version from v16(working) to v5(not working). Tried RAK's firmware for RAK2287 as suggested but got the same problem. Also tried test_loragw_com and test_loragw_com_sx1250 but it READS only zero.
Edit: one more output:
|
I can confirm similar results. @kmuster-semtech Installed the latest RAK firmware as suggested. Same error. RAK Firmware
Note: chip_id (USB)
Note: This one doesn't seem to be using USB. chip_id (SPI)
Note: Same error test_loragw_com
Note: The Read Values are a fixed value. Also in Is there a way to read any error codes from the sx1302 chip to understand what is the exact error ? Any specific register that could be read ? |
|
@mareksbb Thanks for sharing ! It certainly is helping. The packet forwarder seems to be working fine now. GPIO 25 seems to be connected to the GPS modules's RESET pin (on the RAK2287 Pi HAT). Starting longevity test to check stability. The original cause of the issue is still unknown and needs investigation. |
this library is configured for raspberry pi os 32 bits. it's not compatible with 64 bits architecture |
@ahmed560 I have tested sx1302_hal with 64 bit os on Rpi4B. It is compatible as far as I can see it. |
So, I did a cross-compilation with aarch64-linux-gnu toolchain for this
project and i copied libraries and binary files in raspberry card the is
worked but the RX test show this problem
Le ven. 3 juin 2022 à 07:58, Guinnes Singh ***@***.***> a
écrit :
… @ahmed560 <https://github.com/ahmed560> I have tested sx1302_hal with 64
bit os on Rpi4B. It is compatible as far as I can see it.
—
Reply to this email directly, view it on GitHub
<#67 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOIYQAFDAE52XT3JCMH4LWDVNGNHVANCNFSM5KP2OBQQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@ahmed560 If you see the error Exact cause of the issue is not yet known. |
Ok, I will check. thank you for your interraction
Le mar. 7 juin 2022 à 10:28, Guinnes Singh ***@***.***> a
écrit :
… @ahmed560 <https://github.com/ahmed560> If you see the error Failed to
set SX1250_0 in STANDBY_RC mode then so far the only solution is to try
using GPIO25 , see : #67 (comment)
<#67 (comment)>
Exact cause of the issue is not yet known.
—
Reply to this email directly, view it on GitHub
<#67 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOIYQAEBFDCKAVSOTHEVO3LVN4B4FANCNFSM5KP2OBQQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thank you for your inquiry. Customers are encouraged to submit technical questions via our dedicated support portal at https://semtech.force.com/ldp/ldp_support. We invite all users to visit the LoRa Developer Portal Forum at https://forum.lora-developers.semtech.com and to join the thriving LoRa development community! |
I'm facing same issue: "Failed to set SX1250_0 in STANDBY_RC mode" Running on Raspberry Pi4B (4GB) with 64bit bullseye. Update: Changed the OS to 32bit bullseye and tried with SX1302_RESET_PIN=17 as well as SX1302_RESET_PIN=25. Same error:
|
This issue is generally due to a bad SPI connection/configuration. |
@mcoracin Initially I had the same assumption that the SPI connection is bad. However, I am able to use this setup with https://github.com/xoseperez/basicstation and able to connect it to ThingStack. I've reached out to the rak forum for help too. |
@chaudhariatul if the SPI is ok, I guess the issue would be around the reset_lgw.sh script, maybe the GPIO used on the RAK gateway are not the same ?
|
An update:
|
I'm a bit surprised by the "chip version is 0x05 (v0.5)", I don't think this version exists. |
Changing the speed to 2Mhz still shows
|
Which gateway hardware are you using exactly, and which version of the HAL ? |
@mcoracin First run after power cycle (shutdown + wait 5mins + power on)
Retrying after 10secs
After 5 mins
|
Update: Changing reset port to 25 and disabling temperature checks as done here helped: https://github.com/brocaar/sx1302_hal I will need to create or find a patch for BasicStation when using RAK2287 : https://github.com/lorabasics/basicstation |
So, disabling the temperature sensor is to avoid the startup error I guess, right ? |
Correct. RAK2287 board which comes from the Helium miner seems to be slightly different than the one sold separately. I cant tell what are these differences but looking from the top there is no GPS on the RakV2. So setting the reset port to 25 and disabling temperature check works. Here is the output:
I'm able to use the the board with thingstack:
So the next thing to identify is a patch required to disable temperature. I have these references and need to find a right solution: |
Note: The device is using the RAK2287 Pi HAT, which uses RAK2287 concentrator with one SX1302 chip and two SX1250.
The packet forwarder (latest version) fails during startup with the following logs -
Tried using the chip_id tool, but that gives the same error -
Interestingly power cycling (power off and on) helps. Logs after power cycle -
But after the above command, if it is ran again, the problem shows up again -
Note: Chip version goes from
v0.5
tov1.0
after a power cycle, which is probably not normal.Not sure how to fix/debug this ? Any help is appreciated. Thanks!
The text was updated successfully, but these errors were encountered: