GrovePi doesn't work with the LED

nicolas.schilling113 · September 29, 2018, 12:32pm

Hello,

My installation of the GrovePi+ with my Raspberry Pi doesn’t appear to be working. I think I followed exactly the steps listed, but the sensor/led tests are not working and I get errors logged when using “test and Troubleshoot”.

Can you help ?

Thank you!

Nicolas

Check space left
================
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/root           13G    5.1G  7.2G  42% /
devtmpfs           460M       0  460M   0% /dev
tmpfs              464M     50M  414M  11% /dev/shm
tmpfs              464M     13M  452M   3% /run
tmpfs              5.0M    4.0K  5.0M   1% /run/lock
tmpfs              464M       0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p6      68M     22M   46M  33% /boot
tmpfs               93M       0   93M   0% /run/user/1000
/dev/mmcblk0p5      30M    398K   28M   2% /media/pi/SETTINGS

Check for dependencies
======================
python 2.7.13-2 install ok installed
python-pip 9.0.1-2+rpt2 install ok installed
git 1:2.11.0-3+deb9u3 install ok installed
libi2c-dev 3.1.2-3 install ok installed
python-serial 3.2.1-1 install ok installed
python-rpi.gpio 0.6.3~stretch-1 install ok installed
i2c-tools 3.1.2-3 install ok installed
python-smbus 3.1.2-3 install ok installed
dpkg-query: aucun paquet ne correspond à arduino
dpkg-query: aucun paquet ne correspond à minicom
scratch 1.4.0.6~dfsg1-5 install ok installed

find: ‘/proc/662/task/662/net’: Argument invalide
find: ‘/proc/662/net’: Argument invalide
find: ‘/run/user/1000/gvfs’: Permission non accordée
wiringPi Not Found (ERR)
find: ‘/proc/662/task/662/net’: Argument invalide
find: ‘/proc/662/net’: Argument invalide
find: ‘/run/user/1000/gvfs’: Permission non accordée
I2C still in blacklist (ERR)
SPI still in blacklist (ERR)


Check for addition in /modules
==============================
I2C-dev already there
i2c-bcm2708 already there
spi-dev already there


Hardware revision
=================
gpio version: 2.46
Copyright (c) 2012-2018 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warranty

Raspberry Pi Details:
  Type: Pi 3+, Revision: 03, Memory: 1024MB, Maker: Sony 
  * Device tree is enabled.
  *--> Raspberry Pi 3 Model B Plus Rev 1.3
  * This Raspberry Pi supports user-level GPIO access.


Check the /dev folder
=====================
i2c-1
spidev0.0
spidev0.1
ttyAMA0

USB device status
=================
Bus 001 Device 004: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
Bus 001 Device 005: ID 04b3:310c IBM Corp. Wheel Mouse
Bus 001 Device 006: ID 0424:7800 Standard Microsystems Corp. 
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M
            |__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
            |__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=lan78xx, 480M
        |__ Port 3: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
Raspbian for Robots Version
===========================
cat: /home/pi/di_update/Raspbian_For_Robots/Version: Aucun fichier ou dossier de ce type


Hostname
========
raspberrypi


Checking for Atmega chip
========================


avrdude: Version 5.10, compiled on Jun 18 2012 at 12:38:29
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "/etc/avrdude.conf"
         User configuration file is "/root/.avrduderc"
         User configuration file does not exist or is not a regular file, skipping

         Using Port                    : unknown
         Using Programmer              : gpio
         AVR Part                      : ATMEGA328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65     5     4    0 no       1024    4      0  3600  3600 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : GPIO
         Description     : Use sysfs interface to bitbang GPIO lines

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e950f
avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as DA
avrdude: safemode: efuse reads as 5

avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as DA
avrdude: safemode: efuse reads as 5
avrdude: safemode: Fuses OK

avrdude done.  Thank you.


Checking I2C bus for devices
============================

Checking I2C bus 0
==================
Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory

Checking I2C bus 1
==================
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- 04 -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

Checking for firmware version
=============================
GrovePi has firmware version: 1.2.7

RobertLucian · October 1, 2018, 8:37pm

Hmm, can you show us the code you are trying to run?

Thank you!

nicolas.schilling113 · October 3, 2018, 11:05am

Hello,

I am running the first python test script “grove_led_blink.py” (and the led does not).

RobertLucian · October 3, 2018, 9:44pm

Hi @nicolas.schilling113,

I don’t see any problems with the test report - those “errors” you see are actually expected.

With that being said, I wonder if there’s something specific to your image as you’re not actually using the official one - that’s not a bad thing, but it means something can “interfere” with yours.

So I’ve got a suggestion here: run curl -kL dexterindustries.com/update_grovepi | bash and then reboot and check again. Even more than that, I think you can flash the firmware if you didn’t so far, even though you got the right version in the report.

Also, it could be something as simple as plugging the LED in the wrong port on the GrovePi, so could we see a photo of your setup?

Thank you!

nicolas.schilling113 · October 5, 2018, 1:55pm

Hello,

I did the requested update operations without luck so far. Here is the photo

Thank you for your help

RobertLucian · October 6, 2018, 6:09pm

Hi @nicolas.schilling113,

That’s the first time seeing something like this.

Assuming you’re running the following script and that you installed the package again and flashed the firmware, could you change the port to other numbers (2,3,5,6,7,8) and also plug in the LED accordingly into the GrovePi? It’s weird that the GrovePi is replying the firmware address and yet the LED doesn’t blink as it should be.

github.com

DexterInd/GrovePi/blob/master/Software/Python/grove_led_blink.py#L36-L64


import time
from grovepi import *


# Connect the Grove LED to digital port D4
led = 4


pinMode(led,"OUTPUT")
time.sleep(1)


print ("This example will blink a Grove LED connected to the GrovePi+ on the port labeled D4.\nIf you're having trouble seeing the LED blink, be sure to check the LED connection and the port number.\nYou may also try reversing the direction of the LED on the sensor.")
print (" ")
print ("Connect the LED to the port labele D4!" )


while True:
try:
    #Blink the LED
    digitalWrite(led,1)		# Send HIGH to switch on LED
    print ("LED ON!")
    time.sleep(1)

This file has been truncated. show original

I wonder if it’s the LED, in which case, could you use another one and see if that works for you?

Thank you!

nicolas.schilling113 · October 8, 2018, 5:10pm

It’s now working OK.

not sure entirely, but I suspect it has to do with the fact, for some reason, that files are installed as root and I tried to run the script as user pi.
I did “sudo python” them and changed ownership of the test script, and now all (even those still owned by root) Scripts I have tested are working ok.

Thank you for your help

RobertLucian · October 8, 2018, 8:26pm

Hi @nicolas.schilling113,

I’m glad you have it up and working. On a second thought, I think the permissions with which smbus got installed had something to do with this. The only “mistmatch” can only come from the package that interfaces with the GrovePi, so this can justify the problem you had, although I’m not having this problem.

Anyway, that’s something to keep in mind.

Thank you!