Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Change address of KellerLD device

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
embedded-iot

Research direction

No files or tests are named. Review the Python driver's existing I2C address and CRC handling against the supplied smbus sequence, including programming mode and the new-address write. Done means the driver supports changing a KellerLD device address and pressure can be read afterward with the required CRC behavior.

Written by the indexing model from the issue text.

Description

It will be good if this fuction will be in your code.
I made it by this wa:
`
import smbus
import time

DEVICE = 0x40 # Default device I2C address
COMMAND_MODE = 0xA9
SET_NEW_ADDR = 0x42
SET_NEW_ADDR_HSB = 0x00
SET_NEW_ADDR_LSB = 0x01
bus = smbus.SMBus(1)

#Перевод в режим программирования
bus.write_byte(DEVICE, COMMAND_MODE)

time.sleep(0.01)

#Запись нового адреса
bus.write_i2c_block_data(DEVICE,SET_NEW_ADDR,[SET_NEW_ADDR_HSB,SET_NEW_ADDR_LSB])

time.sleep(0.01)`

After this to read pressure need to turn of CRC section.

Dominant language
Python
Stars
1
Forks
14
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bluerobotics/KellerLD-python

All issues in bluerobotics/KellerLD-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.