Skip to content
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

[Bug]: DFrobot Lark Sensor No data to be seen via I2C #5560

Open
MALAONE1 opened this issue Dec 13, 2024 · 7 comments
Open

[Bug]: DFrobot Lark Sensor No data to be seen via I2C #5560

MALAONE1 opened this issue Dec 13, 2024 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@MALAONE1
Copy link

Category

Hardware Compatibility

Hardware

Other

Firmware Version

2.5.16

Description

I have a DFrobot Lark sensor connected to I2C with a RAK 4631 with RAK 19003. The Lark writes all weather data to the internal memory. I2C communication is set in the config, the green LED lights up on the Lark which means that I2C is activated, all cables have been checked several times for the I2C interface to the RAK. According to the serial monitor, the LARK is not recognized.

Relevant log output

No response

@MALAONE1 MALAONE1 added the bug Something isn't working label Dec 13, 2024
@caveman99
Copy link
Member

do you have a bootup log where the i2c scanner is running?

@MALAONE1
Copy link
Author

do you have a bootup log where the i2c scanner is running?

The Lark is not visible in the serial monitor. The only thing that was detected on 0x40 is the also installed INA219. I also tried to uninstall this and only install the Lark. However, it is not displayed there. I will submit a copy of the output during the boot.

@MALAONE1
Copy link
Author

do you have a bootup log where the i2c scanner is running?

//\ E S H T /\ S T / C

DEBUG | ??:??:?? 3 Filesystem files:

DEBUG | ??:??:?? 3 RAK (108 Bytes)

DEBUG | ??:??:?? 3 adafruit (directory)

DEBUG | ??:??:?? 3 bond_prph (directory)

DEBUG | ??:??:?? 3 bond_cntr (directory)

DEBUG | ??:??:?? 3 MODE (1 Bytes)

DEBUG | ??:??:?? 3 prefs (directory)

DEBUG | ??:??:?? 3 channels.proto (160 Bytes)

DEBUG | ??:??:?? 3 module.proto (115 Bytes)

DEBUG | ??:??:?? 3 config.proto (166 Bytes)

DEBUG | ??:??:?? 3 db.proto (4978 Bytes)

DEBUG | ??:??:?? 3 Power::lipoInit lipo sensor is not ready yet

DEBUG | ??:??:?? 3 Use analog input 5 for battery level

INFO | ??:??:?? 3 Scan for i2c devices

DEBUG | ??:??:?? 3 Scan for I2C devices on port 1

DEBUG | ??:??:?? 3 Register MFG_UID: 0x2000

INFO | ??:??:?? 3 INA219 found at address 0x40

DEBUG | ??:??:?? 3 Register MFG_UID FE: 0xffff

DEBUG | ??:??:?? 3 Register MFG_UID 05: 0xffff

INFO | ??:??:?? 3 1 I2C devices found

DEBUG | ??:??:?? 3 acc_info = 0

INFO | ??:??:?? 3 S:B:9,2.5.16.f81d3b0

INFO | ??:??:?? 3 Build timestamp: 1733662250

DEBUG | ??:??:?? 3 Reset reason: 0x0

DEBUG | ??:??:?? 4 Set random seed 70880291

INFO | ??:??:?? 4 Init NodeDB

INFO | ??:??:?? 4 Load /prefs/db.proto

INFO | ??:??:?? 4 Loaded /prefs/db.proto successfully

INFO | ??:??:?? 4 Loaded saved devicestate version 23, with nodecount: 56

INFO | ??:??:?? 4 Load /prefs/config.proto

INFO | ??:??:?? 4 Loaded /prefs/config.proto successfully

INFO | ??:??:?? 4 Loaded saved config version 22

INFO | ??:??:?? 4 Load /prefs/module.proto

INFO | ??:??:?? 4 Loaded /prefs/module.proto successfully

INFO | ??:??:?? 4 Loaded saved moduleConfig version 23

INFO | ??:??:?? 4 Load /prefs/channels.proto

INFO | ??:??:?? 4 Loaded /prefs/channels.proto successfully

INFO | ??:??:?? 4 Loaded saved channelFile version 23

DEBUG | ??:??:?? 4 cleanupMeshDB purged 4 entries

DEBUG | ??:??:?? 4 Use nodenum 0x2923a3b3

DEBUG | ??:??:?? 4 Expand short PSK #1

INFO | ??:??:?? 4 Wanted region 3, using EU_868

DEBUG | ??:??:?? 4 Coerce telemetry to min of 30 minutes on defaults

DEBUG | ??:??:?? 4 Use GPIO09 for button

DEBUG | ??:??:?? 4 Use compiled/slipstreamed tzplaceholder

DEBUG | ??:??:?? 4 Set Timezone to GMT0

DEBUG | ??:??:?? 4 NeighborInfoModule is disabled

DEBUG | ??:??:?? 4 Rescan for I2C keyboard

DEBUG | ??:??:?? 4 Scan for I2C devices on port 1

DEBUG | ??:??:?? 4 Scan address 0x1f

DEBUG | ??:??:?? 4 Scan address 0x55

DEBUG | ??:??:?? 4 Scan address 0x5a

DEBUG | ??:??:?? 4 Scan address 0x5f

ERROR | ??:??:?? 4 Could not open / read /prefs/ringtone.proto

INFO | ??:??:?? 4 Init External Notification Module

INFO | ??:??:?? 4 Use Pin 36 in digital mode

DEBUG | ??:??:?? 4 SX126xInterface(cs=42, irq=47, rst=38, busy=46)

DEBUG | ??:??:?? 4 SX126X_DIO3_TCXO_VOLTAGE defined, using DIO3 as TCXO reference voltage at 1.800000 V

INFO | ??:??:?? 4 Start meshradio init

INFO | ??:??:?? 4 Radio freq=869.525, config.lora.frequency_offset=0.000

INFO | ??:??:?? 4 Set radio: region=EU_868, name=LongFast, config=0, ch=0, power=27

INFO | ??:??:?? 4 myRegion->freqStart -> myRegion->freqEnd: 869.400024 -> 869.650024 (0.250000 MHz)

INFO | ??:??:?? 4 numChannels: 1 x 250.000kHz

INFO | ??:??:?? 4 channel_num: 1

INFO | ??:??:?? 4 frequency: 869.525024

INFO | ??:??:?? 4 Slot time: 77 msec

INFO | ??:??:?? 4 Set radio: final power level=22

INFO | ??:??:?? 4 SX126x init result 0

INFO | ??:??:?? 4 Frequency set to 869.525024

INFO | ??:??:?? 4 Bandwidth set to 250.000000

INFO | ??:??:?? 4 Power output set to 22

@garthvh
Copy link
Member

garthvh commented Dec 17, 2024

@caveman99 this is indeed not working, my lark no longer is detected.

@MALAONE1
Copy link
Author

Yes, there seems to be a problem. Is there any information about it yet?

@caveman99
Copy link
Member

i changed the detection code to not mistake it for the RAK GPS. I don't have a lark myself, i can test with @MALAONE1 directly.

@caveman99 caveman99 self-assigned this Dec 19, 2024
@caveman99
Copy link
Member

caveman99 commented Dec 19, 2024

umm, you have an INA219 at the same board? that won't work. we only support one device per I2C id on the same bus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants