search

NebraLtd / hm-pktfwd

Helium Miner Packet Forwarder
https://nebra.io/hnt
MIT License
12 stars 25 forks source link

Sx1302 not working #70

Closed shawaj closed 2 years ago

shawaj commented 2 years ago

Sx1302 / sx1303 not working with current packet forwarder. Need to investigate why

shawaj commented 2 years ago

Manually running chip_id on SX1301 based device:

root@0f1e195f0f9c:/opt/sx1302# ./chip_id 
CONCENTRATOR_RESET_PIN parameter not passed in, using value from the environment (val=)
./reset_lgw.sh: 33: echo: echo: I/O error
./reset_lgw.sh: 36: ./reset_lgw.sh: cannot create /sys/class/gpio/gpio/direction: Directory nonexistent
CoreCell reset through GPIO...
Opening SPI communication interface
Note: chip version is 0x00 (v0.0)
ERROR: Failed to set SX1250_0 in STANDBY_RC mode
ERROR: failed to setup radio 0
ERROR: failed to start the gateway

This correctly gives a 1 exit code

On SX1302 based:

root@b020abb3ab4e:/opt# cd sx1302
root@b020abb3ab4e:/opt/sx1302# ./chip_id -d /dev/spidev1.2
CONCENTRATOR_RESET_PIN parameter not passed in, using value from the environment (val=)
./reset_lgw.sh: 33: echo: echo: I/O error
./reset_lgw.sh: 36: ./reset_lgw.sh: cannot create /sys/class/gpio/gpio/direction: Directory nonexistent
CoreCell reset through GPIO...
Opening SPI communication interface
Note: chip version is 0x10 (v1.0)
INFO: using legacy timestamp
ARB: dual demodulation disabled for all SF

INFO: concentrator chip model ID: 0x00

INFO: concentrator EUI: 0x0016c001ff1a08f0

Closing SPI communication interface
CONCENTRATOR_RESET_PIN parameter not passed in, using value from the environment (val=)
CoreCell reset through GPIO...

This correctly gives a 0 exit code

However when running automatically on an sx1302 device, it is not recognised as being sx1302 based.

Issue, I guess, is something to do with the check: https://github.com/NebraLtd/hm-pktfwd/blob/3f7c41eedfcbda414faec4d2cc13e149d7ca704e/pktfwd/utils.py#L62-L76

Or possibly how we use it later.

These devices on balena are running sx1302 https://dashboard.balena-cloud.com/devices/28c44310bfc8ffc6098bce2b3696336e/summary https://dashboard.balena-cloud.com/devices/7f17117b0ff743debb90055bf21ceaa7/summary

shawaj commented 2 years ago

@marvinmarnold I guess from python docs it needs to be without the stdout like this:

subprocess.run(util_chip_id_cmd, capture_output=True, 
                        text=True, check=True)

as we aren't using stdout for anything currently?

maybe in future we will want to use the output to determine if sx1302 or sx1303 but not sure if that maybe is best in a different function? not sure what you think?

shawaj commented 2 years ago

created a PR in #71 - unless you think there is a better way to do this?

shawaj commented 2 years ago

Ok, that didn't seem to work anyway! 🤦

shawaj commented 2 years ago

On second thought, I guess this is the issue:

./reset_lgw.sh: 33: echo: echo: I/O error
./reset_lgw.sh: 36: ./reset_lgw.sh: cannot create /sys/class/gpio/gpio/direction: Directory nonexistent

As it's probably throwing an exception

Actually I think that's just due to a missing ENV variable when I was calling it manually

shawaj commented 2 years ago

Weirdly, it also seems to try to reset twice....

 packet-forwarder          SX1302_LORA_PKT_FWD_FILEPATH=/opt/sx1302/lora_pkt_fwd
 packet-forwarder          SX1301_LORA_PKT_FWD_DIR=/opt/sx1301
 packet-forwarder  
 packet-forwarder  2021-11-15 16:42:32,945 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).set_variant_attributes -- /opt/pktfwd/pktfwd_app.py:(91) - Variant COMP-RAKHM set with reset_pin 17 and spi_bus spidev0.0
 packet-forwarder  2021-11-15 16:42:32,946 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).start -- /opt/pktfwd/pktfwd_app.py:(39) - STARTING PKTFWD
 packet-forwarder  2021-11-15 16:42:32,948 - [DEBUG] - hm_pyhelper.miner_param - (miner_param.py).await_spi_available -- /opt/pktfwd-dependencies/hm_pyhelper/miner_param.py:(217) - SPI bus spidev0.0 Configured Correctly
 packet-forwarder  2021-11-15 16:42:32,950 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).prepare_to_start -- /opt/pktfwd/pktfwd_app.py:(73) - Region set to EU868
 packet-forwarder  2021-11-15 16:42:32,950 - [DEBUG] - pktfwd.utils - (utils.py).await_system_ready -- /opt/pktfwd/utils.py:(49) - Waiting 5 seconds for systems to be ready
 packet-forwarder  2021-11-15 16:42:37,956 - [DEBUG] - pktfwd.utils - (utils.py).await_system_ready -- /opt/pktfwd/utils.py:(51) - System now ready
 packet-forwarder  2021-11-15 16:42:37,957 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).prepare_to_start -- /opt/pktfwd/pktfwd_app.py:(76) - Finished preparing pktfwd
 packet-forwarder  2021-11-15 16:42:37,971 - [DEBUG] - pktfwd.utils - (utils.py).update_global_conf -- /opt/pktfwd/utils.py:(99) - No chip EUI. Assume SX1301
 packet-forwarder  2021-11-15 16:42:37,972 - [DEBUG] - pktfwd.utils - (utils.py).replace_sx1301_global_conf_with_regional -- /opt/pktfwd/utils.py:(116) - Copying SX1301 conf from /opt/pktfwd/config/lora_templates_sx1301/EU-global_conf.json to /opt/global_conf.json
 packet-forwarder  CONCENTRATOR_RESET_PIN parameter not passed in, using value from the environment (val=17)
 packet-forwarder  CoreCell reset through GPIO17...
 packet-forwarder  CONCENTRATOR_RESET_PIN parameter not passed in, using value from the environment (val=17)
 packet-forwarder  CoreCell reset through GPIO17...
marvinmarnold commented 2 years ago

Weirdly, it also seems to try to reset twice....

I think this is because chip_id calls reset and then immediately after we explicitly do another reset before starting the concentrator. Its a little weird that the replace_sx1301_global_conf_with_regional logline doesn't show up in between the two resets, but given there's a mix of logs coming from python vs C, not too surprising.

marvinmarnold commented 2 years ago

72 is only a partial fix. With that change, the correct concentrator version is now detected. But it still fails to start:

2021-11-16 02:54:25,361 - [DEBUG] - pktfwd.utils - (utils.py).await_system_ready -- /opt/pktfwd/utils.py:(49) - Waiting 5 seconds for systems to be ready
2021-11-16 02:54:30,368 - [DEBUG] - pktfwd.utils - (utils.py).await_system_ready -- /opt/pktfwd/utils.py:(51) - System now ready
2021-11-16 02:54:30,370 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).prepare_to_start -- /opt/pktfwd/pktfwd_app.py:(76) - Finished preparing pktfwd
2021-11-16 02:54:32,601 - [DEBUG] - pktfwd.utils - (utils.py).is_concentrator_sx1302 -- /opt/pktfwd/utils.py:(72) - SX1302 / SX1303 Detected
2021-11-16 02:54:37,626 - [ERROR] - pktfwd.utils - (utils.py).retry_start_concentrator -- /opt/pktfwd/utils.py:(185) - lora_pkt_fwd stopped with code=1.
shawaj commented 2 years ago

Hmmm strange.

shawaj commented 2 years ago

@marvinmarnold just had a thought. What happens if you put the rest script both in the old location and the new location?

It used to work, so I'm wondering if the packet forwarder is expecting it somewhere else?

Or perhaps in the same directory as the sx1302_hal

shawaj commented 2 years ago

Actually it's showing a message saying it can't find global_conf.json so maybe that's in the wrong place: https://github.com/NebraLtd/hm-pktfwd/blob/3f7c41eedfcbda414faec4d2cc13e149d7ca704e/pktfwd/utils.py#L128-L130

Think this should be sx1302 directory or root dir?

shawaj commented 2 years ago

testing in https://github.com/NebraLtd/helium-miner-software/pull/264 and this issue will be closed when pushed to production

marvinmarnold commented 2 years ago

This is in production now. Closing.

Benixpearlin commented 2 years ago

Helo, i am using raspberry pi with sx1302 i am using sx1302_hal-master packet forwarder code

but i am facing the following error while starting the packet forwarder

Packet Forwarder Version: 2.1.0 SX1302 HAL library version info Version: 2.1.0;

INFO: Little endian host INFO: found configuration file global_conf.json.sx1250.CN490, parsing it INFO: global_conf.json.sx1250.CN490 does contain a JSON object named SX130x_conf, parsing SX1302 parameters INFO: com_type SPI, com_path /dev/spidev0.0, lorawan_public 1, clksrc 0, full_duplex 0 INFO: antenna_gain 0 dBi INFO: Configuring legacy timestamp INFO: no configuration for SX1261 INFO: Configuring Tx Gain LUT for rf_chain 0 with 16 indexes for sx1250 INFO: radio 0 enabled (type SX1250), center frequency 471400000, RSSI offset -207.000000, tx enabled 1, single input mode 1 INFO: radio 1 enabled (type SX1250), center frequency 475000000, RSSI offset -207.000000, tx enabled 0, single input mode 1 INFO: Lora multi-SF channel 0> radio 0, IF -300000 Hz, 125 kHz bw, SF 5 to 12 INFO: Lora multi-SF channel 1> radio 0, IF -100000 Hz, 125 kHz bw, SF 5 to 12 INFO: Lora multi-SF channel 2> radio 0, IF 100000 Hz, 125 kHz bw, SF 5 to 12 INFO: Lora multi-SF channel 3> radio 0, IF 300000 Hz, 125 kHz bw, SF 5 to 12 INFO: Lora multi-SF channel 4> radio 1, IF -300000 Hz, 125 kHz bw, SF 5 to 12 INFO: Lora multi-SF channel 5> radio 1, IF -100000 Hz, 125 kHz bw, SF 5 to 12 INFO: Lora multi-SF channel 6> radio 1, IF 100000 Hz, 125 kHz bw, SF 5 to 12 INFO: Lora multi-SF channel 7> radio 1, IF 300000 Hz, 125 kHz bw, SF 5 to 12 INFO: Lora std channel> radio 1, IF -200000 Hz, 250000 Hz bw, SF 7, Explicit header INFO: FSK channel> radio 1, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate INFO: global_conf.json.sx1250.CN490 does contain a JSON object named gateway_conf, parsing gateway parameters INFO: gateway MAC address is configured to AA555A0000000000 INFO: server hostname or IP address is configured to "localhost" INFO: upstream port is configured to "1730" INFO: downstream port is configured to "1730" INFO: downstream keep-alive interval is configured to 2 seconds INFO: statistics display interval is configured to 30 seconds INFO: upstream PUSH_DATA time-out is configured to 100 ms INFO: packets received with a valid CRC will be forwarded INFO: packets received with a CRC error will NOT be forwarded INFO: packets received with no CRC will NOT be forwarded INFO: GPS serial port path is configured to "/dev/ttyS0" INFO: Reference latitude is configured to 0.000000 deg INFO: Reference longitude is configured to 0.000000 deg INFO: Reference altitude is configured to 0 meters INFO: Beaconing period is configured to 0 seconds INFO: Beaconing signal will be emitted at 869525000 Hz INFO: Beaconing datarate is set to SF9 INFO: Beaconing modulation bandwidth is set to 125000Hz INFO: Beaconing TX power is set to 14dBm INFO: Beaconing information descriptor is set to 0 INFO: global_conf.json.sx1250.CN490 does contain a JSON object named debug_conf, parsing debug parameters INFO: got 2 debug reference payload INFO: reference payload ID 0 is 0xCAFE1234 INFO: reference payload ID 1 is 0xCAFE2345 INFO: setting debug log file name to loragw_hal.log INFO: [main] TTY port /dev/ttyS0 open for GPS synchronization CoreCell reset through GPIO23... SX1261 reset through GPIO23... CoreCell power enable through GPIO18... CoreCell ADC reset through GPIO13... Opening SPI communication interface Note: chip version is 0x00 (v0.0) ERROR: Failed to set SX1250_0 in STANDBY_XOSC mode ERROR: failed to setup radio 0 ERROR: [main] failed to start the concentrator

what am i missing??

shawaj commented 2 years ago

@Benixpearlin probably an incorrect reset pin script or configuration file