UltraBorg Missing from i2cdetect

Submitted by djjeffrey on Sun, 03/10/2019 - 13:51

Forums:

I can not detect the ultraborg via i2cdetect. this is the second ultraborg i have bought and cant see either of them. I though it must be the first board that was faulty and decided to bite the bullet and buy another thinking i must have fried it. I have a thunderborg hooked up after the ultraborg i.e pi connects to ultraborg then connects to thunderborg and i can see the thunderborg at 15. the power for the whole system it via a battery connected to the thunderborg so im 100% sure i have the correct connections and the cables are fine.

I've followed the sites trouble shooting instructions. I have tried adding 10K pullups to the 3v3 rail.
New Pi's and fresh installs. Still cannot detect either of the UltraBorg Boards
Using Pi3B+ with the latest raspbian installed.
Driving me a little mad as its cost me £32 for the boards and a day or two of messing about.
I understand there is a away to recode the Ultraborg PIC and was wondering if I needed to go down that route?

But it must be something i'm missing in the setup. any help would be much appreciated.

Thanks

piborg's picture

piborg

Sun, 03/10/2019 - 15:06

Something else attached to either the UltraBorg or the GPIO might be causing problems and preventing communication.

The first thing to do is check the UltraBorgs on their own with nothing else attached to them or the GPIO port. This includes any servos / sensors that you might have attached to the UltraBorg.

Could you show the output from running sudo i2cdetect -y 1 with each UltraBorg on its own.

djjeffrey

Sun, 03/10/2019 - 20:26

Hi Thanks for the response.
Nothing else connected to either the bus or the board.
With either ultraborg (one at a time) using i2cdetect -y 1 I get blanks though out the reg addresses.

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

Had a look at the voltages of the bus and confirmed the bus works with my Thunderborg.

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

I've given up on the UltraBorg (for now), spent the afternoon coding for 4 UltraSonics to install on my DiddyBorg.

Was thinking of making my own ultraborg perhaps with a ardunio nano? or even trying to re code your one with the info you wonderful folk have kindly shared in other places, but that would probably take me months so any help getting these ones working would be awesome. some more info on my set up below.

/etc/modules

# Kernel modules needed for I2C add-ons, e.g. ThunderBorg
# Kernel modules needed for I2C add-ons, e.g. UltraBorg
i2c-bcm2708
i2c-dev

/etc/modprobe.d/raspi-blacklist.conf
is a blank file

/boot/config.txt

dtparam=i2c_arm=on
dtparam=i2c1=on
dtparam=i2s=on
dtparam=spi=on
#dtparam=i2c_baudrate=100000

tried different baud rate at some point - did not see UltraBorg but could see ThunderBorg
I know some of the dtparm's dont need to be on but i did not pick up the UltraBorg before or after but still picks up the other i2c devices.
even tried setting the 

core_freq=250

no effect

lsmod

Module                  Size  Used by
rfcomm                 49152  4
bnep                   20480  2
fuse                  110592  3
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
evdev                  24576  2
hid_logitech_hidpp     36864  0
spidev                 16384  0
brcmfmac              307200  0
brcmutil               16384  1 brcmfmac
hid_logitech_dj        20480  0
cfg80211              573440  1 brcmfmac
rfkill                 28672  6 bluetooth,cfg80211
snd_soc_bcm2835_i2s    16384  0
snd_soc_core          188416  1 snd_soc_bcm2835_i2s
snd_compress           20480  1 snd_soc_core
i2c_bcm2835            16384  0
snd_bcm2835            32768  1
snd_pcm_dmaengine      16384  1 snd_soc_core
snd_pcm                98304  4 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_bcm2835,snd_soc_core
snd_timer              32768  1 snd_pcm
spi_bcm2835            16384  0
snd                    69632  7 snd_compress,snd_timer,snd_bcm2835,snd_soc_core,snd_pcm
fixed                  16384  0
uio_pdrv_genirq        16384  0
uio                    20480  1 uio_pdrv_genirq
i2c_dev                16384  0
i2c_bcm2708            16384  0
ip_tables              24576  0
x_tables               32768  1 ip_tables
ipv6                  425984  28

I noticed that i2C_dev and i2c_bcm2708 both have a 0? is that something to look at? they are included in the modules

Thanks again

piborg's picture

piborg

Mon, 03/11/2019 - 17:35

Are you in the UK?

I ask because it would probably be easier for us to diagnose what is wrong and fix the UltraBorgs from our end. If you are in the UK we would be happy to pay for the postage cost both ways :)

Subscribe to Comments for "UltraBorg Missing from i2cdetect"