Communication-error

[kf4jbz]

Have 2 pijuices. First one worked out of the box. Updated firmware worked ok. Removed pijuice from pi for height testing of standoff’s and stacking headers to mount in smarti pi case. Removed all power sources before testing. Reinstalled pijuice got communication-error in GUI Battery, GPIO, fault. Second pijuice same GUI communication-errors out of the box. Using same pi2. Tried reboot, software/firmware update, and reinstalls, updates, upgrades, boot loader.

[tvoverbeek]

Are you sure you mounted the PiJuice correctly on the 40-pin RPi header? I myself have a few times misplaced the PiJuice (one pin off, or even missing a complete row) which obviously resulted in communication errors (=no I2C communication). Does i2cdetect -y 1 report the two addresses of the PiJuice (0x14 and the RTC at 0x68)?

[kf4jbz]

I am sure that both PiJuice#1 and #2 is mounted correctly. Tried i2cdetect -y 1. Will try to send a screen shot and copy of emails from Chris at PiSupply.
Thanks

[kf4jbz]

Should I try another rpi2? Any idea where the communication_error is coming from? i.e.,between the pijuice and the rpi, between software and pijuice, or other? The pijuice green/blue/red leds are working.

[kf4jbz]

Screen shots 4 Communication_error

[tvoverbeek]

Since i2cdetect does not show anything there is obviously no I2C communication between the RPi and the PiJuice. PiJuice software is not involved with i2cdetect.
Here is what to expect from i2cdetect -y 1 with the PiJuice mounted:

pi@rpi-stretch-full:~ $ i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- 14 -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                   

Have you checked if I2C is enabled after you reinstalled Raspbian?
If I remember correctly I2C is not enabled on a fresh (re)install.
On the desktop: Preferences->Raspberry Pi Configuration->Interfaces

[kf4jbz]

Changed the interface tab I2C to enable, checked I2C again no change no 14 or 68, checked pijuice settings same problem-communication_error. Any other changes to try?

[shawaj]

Have you rebooted after turning i2c on?

…

On Tue, 24 Jul 2018, 23:30 kf4jbz, ***@***.***> wrote: Changed the interface tab I2C to enable, checked I2C again no change no 14 or 68, checked pijuice settings same problem-communication_error. Any other changes to try? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#175 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADNCuqbXprqniRxt_GqDne8j-7L0Rirkks5uJ5_zgaJpZM4VblSo> .

[tvoverbeek]

@kf4jbz

Changed the interface tab I2C to enable

Hope you clicked OK after setting the enable checkbox.
You can check this in a terminal window with the following commands:

pi@rpi-stretch-full:~ $ ls -l /dev/i2c-1
crw-rw---- 1 root i2c 89, 1 Jul 24 22:19 /dev/i2c-1
pi@rpi-stretch-full:~ $

If /dev/i2c-1 does not exist the enable did not work
Also check the output from lsmod:

pi@rpi-stretch-full:~ $ lsmod
Module                  Size  Used by
rfcomm                 49152  6
bnep                   20480  2
hci_uart               36864  1
btbcm                  16384  1 hci_uart
serdev                 20480  1 hci_uart
bluetooth             368640  29 hci_uart,bnep,btbcm,rfcomm
ecdh_generic           28672  1 bluetooth
fuse                  106496  3
joydev                 20480  0
evdev                  24576  3
uinput                 20480  3
spidev                 16384  0
brcmfmac              307200  0
brcmutil               16384  1 brcmfmac
cfg80211              573440  1 brcmfmac
rfkill                 28672  6 bluetooth,cfg80211
snd_bcm2835            32768  1
snd_pcm                98304  1 snd_bcm2835
snd_timer              32768  1 snd_pcm
snd                    69632  5 snd_timer,snd_bcm2835,snd_pcm
i2c_bcm2835            16384  2     <==========
spi_bcm2835            16384  0
uio_pdrv_genirq        16384  0
uio                    20480  1 uio_pdrv_genirq
fixed                  16384  0
i2c_dev                16384  4     <==========
ip_tables              24576  0
x_tables               32768  1 ip_tables
ipv6                  434176  32
pi@rpi-stretch-full:~ $ 

The i2c-bcm2835 and i2c-dev modules should be loaded.

[kf4jbz]

New problem-rebooted after turning on I2C-get the rpi welcome, systems-host named.service in lower left corner and a blinking cursor. Does not complete boot up.

[kf4jbz]

Continue of boot up issue-have to remove all power and pijuice battery to clear screen and start over.

[kf4jbz]

Third try worked system booted. Yes rebooted after changing I2C to enable and no change to i2cdetect -y 1 no 14 or 68

[kf4jbz]

And yes clicked ok before reboot

[tvoverbeek]

Starts to smell like a corrupt SD card and/or a bad power supply.
I am out of suggestions now.

[kf4jbz]

Have 2 SD cards (16 GB Adafruit NOOBS and 8 GB Mike Richards Ham Radio NOOBS card from UK) Been trying everything suggested with one card at a time and getting same result. Process of elimination leaves the pi2. Other than the pijuice comms issue everything works. Running mains 5V 2.5 amp, rpi2, WiFi, bluetooth, 7 inch touch screen.

[kf4jbz]

Thanks for your help tvoverbeek

[kf4jbz]

Got another rpi2, pijuice now works. Chris at Pisupply close my ticket. The international shipping USA to UK cost more than second rpi2 at Amazon. Don’t know what is wrong with first rpi2, but everything on it works except with the the pijuice.

[ChristopherRush]

@kf4jbz If you open a Github issue then your support ticket will get closed.

[kf4jbz]

Questions
From the pijuice hat config battery menu-would you recommend a battery temp sensor hat compatible with pijuice hat?
Pogo pin-function?

[shawaj]

@kf4jbz - pogo pin is to restart pi when power plugged into the pi micro USB

There is already a temp sensor in the battery and on the board

[lbabaly]

Hello,

I had the very same issue, and in the end I had switch to another raspberrypi 3 B+.
Which RPI version did you have this issue?