I2C not working pro...
 
Notifications
Clear all

I2C not working properly

32 Posts
2 Users
0 Reactions
334 Views
 ryf
(@ryf)
Active Member
Joined: 3 weeks ago
Posts: 14
Topic starter  

I don't see the I2c Adresses 0x68/0x69, I only see 6a..6f as in the attached Image.

I have an other I2C Device on Adress 0x38 which works without any issue, so i think the bus should be ok.
I cant find anything about pull-up resistors on the UPS Pico, i habe some on my other Device 0x38.

 

Any suggestions? 


   
Quote
 ryf
(@ryf)
Active Member
Joined: 3 weeks ago
Posts: 14
Topic starter  

After some time then from time to time the 0x68 / 0x69 are shown with i2cdetect, but even then Pico_status has an IO-Error (attached image)...

 


   
ReplyQuote
(@piadmin)
Member Admin
Joined: 6 years ago
Posts: 119
 

Posted by: @ryf

I don't see the I2c Adresses 0x68/0x69, I only see 6a..6f as in the attached Image.

I have an other I2C Device on Adress 0x38 which works without any issue, so i think the bus should be ok.
I cant find anything about pull-up resistors on the UPS Pico, i habe some on my other Device 0x38.

 

Any suggestions? 

Hi,

You need to decrease the speed of the I2C to lower rate, i.e. 25K. Please advise

The I2C pull-up resistors are on the Raspberry Pi PCB and not to be on the UPS PIco I2C also. 

Please keep me informed

Best Regards

PiM

 


   
ReplyQuote
(@piadmin)
Member Admin
Joined: 6 years ago
Posts: 119
 

Posted by: @ryf

After some time then from time to time the 0x68 / 0x69 are shown with i2cdetect, but even then Pico_status has an IO-Error (attached image)...

 

Hi,

Please decrease the speed of the I2C on the Raspberry Pi.

--------------------------

Decreasing the Raspberry Pi I2C rate

The Raspberry Pi I2C driver has a bug, well known – as a stretching problem. This because that Raspberries Pi are not waiting for the peripheral if it is not fast enough. It was not so important for the former interaction way, as the access to the I2C, was only if user requests data from the UPS Pico. The UPS Pico is requiring the stretching in most of the cases, as it is slower that Raspberry Pi.  The new driver is using the I2C as an interaction way with UPS Pico, therefore the possibility of missed access is important. To overcome this problem user, need to slow down the rate of the Raspberry Pi to lower one from the 100K as it is by default. We propose to slowdown to 50K or even less i.e. to 25. This will not affect any other peripheral using the I2C interface. This can be done by editing the config.txt and adding the following lines

                                 sudo nano /boot/config.txt

 

[PICO]

# Added for PIco

enable_uart=1

dtoverlay=i2c-rtc,ds1307

dtparam=i2c_arm=on

dtparam=i2c1_baudrate=5000

------------------------

Please check the manual PAGE 50

Best Regards PiM

 


   
ReplyQuote
 ryf
(@ryf)
Active Member
Joined: 3 weeks ago
Posts: 14
Topic starter  

I decreased the now the clock as suggested, but with no effect, I still don't see Adresses 0x68 / 0x69...

 


   
ReplyQuote
 ryf
(@ryf)
Active Member
Joined: 3 weeks ago
Posts: 14
Topic starter  

That's how it looks like on the i2c...


   
ReplyQuote
(@piadmin)
Member Admin
Joined: 6 years ago
Posts: 119
 

@ryf 

Hi,
Close to be impossible as all other I2C PIco addresses are visible. So, that means the I2C PIco interface is working well. Can you please do the following:

1. Remove (temporary) the other device 0x38 and check

2. Invoke factory defaults by buttons pressing and check again (still without the other device)

And then inform me about

Best Regards

PiM


   
ReplyQuote
(@piadmin)
Member Admin
Joined: 6 years ago
Posts: 119
 

@ryf 

Hi,

Please follow my recommendation on next post I sent and inform me about

My Best Regards

Pi Master


   
ReplyQuote
 ryf
(@ryf)
Active Member
Joined: 3 weeks ago
Posts: 14
Topic starter  

Hi PiMaster

 

Thanks for your reply.

What button do you mean for FactoryReset?
The second one called "UPS Pico HV4 Reset"?


   
ReplyQuote
(@piadmin)
Member Admin
Joined: 6 years ago
Posts: 119
 

Hi,

Page 96 in the manual (or close to this page number) depending to what version of manual you have.

1. Make sure your system is Cable Powered (prefer Raspberry Pi USB) 

2. Press the UR button

3. Keep pressed the UR button, and then (with still pressed UR button) press the key B

4. Release the UR button (but keep the key B pressed)

5. After some seconds (1-2) release the Key B

6. I do not have now on front of me a PIco system, but you should see some LED message (flashing)

After additional few seconds your UPS PIco is setup to factory defaults and ready to be used. Therefore if you made any wrong setup, it will be automatically corrected.

Keep me informed.

My Best Regards

PiM

 


   
ReplyQuote
(@piadmin)
Member Admin
Joined: 6 years ago
Posts: 119
 

NOTE: Please remember to remove ANY other hardware before we make it working properly. WHen we make it to work, you are free to add whatever you like !!


   
ReplyQuote
 ryf
(@ryf)
Active Member
Joined: 3 weeks ago
Posts: 14
Topic starter  

As soon as i have not connected the other Device (what works since years) the adresses appear and pico-status works!

When I reconnect the other Device (what really only uses 0x38) the two adresses desappear.

So I try to change the UPS to an alternate Adress by setting 0x6b @0x00 to 0x40, what happens (if i read back its set to 40), but after Reboot, the old Range from 6... is still running.

Do i have to safe the alternative Adress?


   
ReplyQuote
(@piadmin)
Member Admin
Joined: 6 years ago
Posts: 119
 

@ryf 

Hi,

This is not a problem of other device, seems that there is an address overlapping. Both devices are good.

The solution is to change the address range that PIco is using. 

Please do that changes in the PIco as also in the python script, then check it without your additional hardware, be sure that it is working and the add the old hardware - step by step. 

attached description form manual how to do that.

Please keep me informed

My Best Regards

PiM


   
ReplyQuote
(@piadmin)
Member Admin
Joined: 6 years ago
Posts: 119
 

Hi,

Have you solved it ?

Just to close the thread

My Best Regards

PiM


   
ReplyQuote
 ryf
(@ryf)
Active Member
Joined: 3 weeks ago
Posts: 14
Topic starter  

Not yet, but I try again tonight...


   
ReplyQuote
Page 1 / 3
Share: