DO NOT UPDATE TO BRANCH=next KERNEL!!

Support for the UPS PIco HV3.0A, UPS PIco HV3.0 A Plus, UPS PIco HV3.0A Terminal Block products, sd also for updated hardware HV3.0B

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Postby Pimaster » Tue Feb 28, 2017 4:18 pm

cresfang wrote:
Pimaster wrote:You can increase the speed up to 70K, still working perfectly. Higher that 75 has a problem
I suggest to set it at 50 000, work well, and fast enough


Yess boss 8-)

I'm testing 50k right now as well ;)

EDIT: 50k gives me 0xff and all that errors... and reverting to 10k + reboot now giving strange fw ver: 69

UPS PIco Firmware....: 69
UPS PIco Bootloader...: 50
UPS PIco PCB Version..: 41


It is timing problem, and I2C setup on our side. They made the I2C clock calculation in a different way (proper one). Remember that we are running a huge interrupt service routing on each i2c byte (3 uS)
Warmest Regards
PiM
---
Designing with Mentor Graphics PADS - www.pads.com
Please read and follow the PiForum rules
http://www.forum.pimodules.com/viewtopic.php?f=13&t=196
---
Pimaster
Site Admin
 
Posts: 1611
Joined: Fri Sep 14, 2012 7:50 am

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Postby cresfang » Wed Mar 01, 2017 4:28 am

Pimaster wrote:It is timing problem, and I2C setup on our side. They made the I2C clock calculation in a different way (proper one). Remember that we are running a huge interrupt service routing on each i2c byte (3 uS)


so for now I'll stick to 10k, its working perfectly.... ;)
and for the fw ver issue, I just reset the UPS using UR button...
now it shows correct fw ver (24)....

tell me if you need any help... ;)
http://crescendo-fang.cf
User avatar
cresfang
 
Posts: 87
Joined: Mon Aug 29, 2016 9:43 am
Location: Garden of Time

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Postby jbaumann » Sun Mar 12, 2017 4:06 pm

Even though I own one of the 1.1 version of the UPS Pico, the problem was the same, and the solution works without a problem. Thanks a lot for the solution.

Regards, Joachim
jbaumann
 
Posts: 6
Joined: Thu May 26, 2016 7:34 pm

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Postby Pimaster » Sun Mar 12, 2017 8:04 pm

Hi,
I know. We have already solved it for the HV3.0 and for the HV1.0/1. We are planning to release new firmware for the HV1.1/0 just after we complete the HV3.0 moving the biggest part fo firmware to the old one. We are still not able to support the old HV1.1 forum due thousands not moderated posts, please be pationt little bit, until we activate this forum also.
Warmest Regards
PiM
---
Designing with Mentor Graphics PADS - www.pads.com
Please read and follow the PiForum rules
http://www.forum.pimodules.com/viewtopic.php?f=13&t=196
---
Pimaster
Site Admin
 
Posts: 1611
Joined: Fri Sep 14, 2012 7:50 am

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Postby tetzlav » Wed Aug 16, 2017 8:50 pm

just add
Code: Select all
dtoverlay=i2c-bcm2708

to /boot/config.txt to reactivate the old driver and the pico reads will working again... ;)
Last edited by tetzlav on Fri Sep 08, 2017 9:15 pm, edited 1 time in total.
tetzlav
 
Posts: 4
Joined: Sun Sep 27, 2015 10:50 am

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Postby Pimaster » Sun Aug 20, 2017 4:05 pm

thank you !!
Warmest Regards
PiM
---
Designing with Mentor Graphics PADS - www.pads.com
Please read and follow the PiForum rules
http://www.forum.pimodules.com/viewtopic.php?f=13&t=196
---
Pimaster
Site Admin
 
Posts: 1611
Joined: Fri Sep 14, 2012 7:50 am

Previous

Return to UPS PIco HV3.0A and HV3.0B

Who is online

Users browsing this forum: No registered users and 1 guest

cron