CLI doesn't seem to work

[fiveseven808]

Here's what I get

$ lifepo4wered-cli get vbat
-1
$ lifepo4wered-cli get vout
-1
$ lifepo4wered-cli get VBAT
-1
$ lifepo4wered-cli get vin
-1

But I know the install must've been successful since I can now power on and shutdown my pi with the touch button just fine, The LED changes state when in bootup and shutdown process accordingly.

Any help would be greatly appreciated. Thanks!

Edit: More info

$ lifepo4wered-cli get meh
ERROR: Invalid variable name

Available variables for READ:
        I2C_REG_VER
$ lifepo4wered-cli get i2c_reg_ver
-2

[xorbit]

This may be a permissions issue. Which distro are you using? Does your user have permissions to access the /dev/i2c-1 device? Can you test if it works when you run the command as root or with sudo?

[fiveseven808]

I tried with sudo, same response. OS is standard Raspbian-Jessie. I believe standard user pi has permissions to use i2c-1 device. Any way to test?

$ sudo lifepo4wered-cli get vbat
-1
$

[fiveseven808]

I just tried it with a different SD card... same issue :\

[fiveseven808]

What is the range of i2c baudrates this thing an communicate at?

The problem was that I had set my i2c baudrate to 400000 because I'm using a display over it. It appears that this was causing the problem.

I forced the baudrate down to 32000 and the cli seems to work as intended.

Before I close the issue, would you be able to provide me with a range of I2c speeds that this device will be able to run at? Or will I need to determine this myself? Would it be possible to increase the possible i2c rates of this device?

Thanks! @

[fiveseven808]

Seems that the CLI is a little flakey. Any ideas?

$ lifepo4wered-cli set LED_STATE 3
3
$ lifepo4wered-cli set LED_STATE 1
-1
$ lifepo4wered-cli set LED_STATE 1
1
$ lifepo4wered-cli get vin
170
$ lifepo4wered-cli get vin
-1
$ lifepo4wered-cli get vin
-1
$ lifepo4wered-cli get vin
170
$ lifepo4wered-cli get vbat
-1
$ lifepo4wered-cli get vbat
3299
$ lifepo4wered-cli get vout
-1
$ lifepo4wered-cli get vout
-1
$ lifepo4wered-cli get vout
4914
$ lifepo4wered-cli get vbat_min
2854

[xorbit]

The LiFePO4wered/Pi and /Pi3 are designed to run at the default I2C 100 kHz clock. I have not tested it at higher clock speeds. The MSP430G2231 has a limited I2C peripheral that requires a lot of software interaction, which limits the maximum speed. Was the last log run at 100 kHz or less clock speed? How much communication is there with other I2C peripherals like the screen you mention? As you can see in lifepo4wered-data.c, I do 5 retries spaced 2 ms apart before I return with an error code. If your I2C bus is very busy, you may need to alter the number of retries or the delay between the retries in this file, recompile and reinstall. This is application specific, the default values work fine for most users as far as I know.