@HorsePlay No probs ;) It was a great vid! Had to sub since the content looks great!
Glad you liked it, thought I had to do them some justice.
Managed to pull their images from the little splashes FM put up during the stream.
~~~~~~~~~~~~ Soft & foofy ~~~~~~~~~~~~
~~~~~~ Unlicensed Onewheel Nurse ~~~~~~
~ Types a lot for someone who hates reading ~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
One of the huge trees on my daily route appears to have lost an entire branch that gashed itself on the way down :(
Impressive to look at mind you, hope the tree survives.
I'd imagine it's extremely old given the trunk is almost the width of a car.
Been a phenomenal amount of great things happen this week!
Moreover in case anyone missed it @HanahsDax finally made it to 1000 days of unbroken riding. Although not officially noticed by the leaderboards due to the XR falling victim to a hardware failure the V1 in all it's glory carried the torch... or rather Dax to that milestone.
Currently FM are experiencing server issues which has been ongoing for over 24 hours. Because of this today's info is technically yesterdays. Fingers crossed the resolve the freeze and everyone retains their positions.
@HorsePlay Awww I feel the pain, been there a few times. Loving the comments :)
I think there will be clustering on the server, it looks like it's hosted on an AWS server (Amazon). IP has been changing a few times, not sure if that's just load balancing or related to the work being carried out.
Would be an honour to be given access to the big "reboot" button but I'm happy being an end user xD
Got the stress of maintaining hosted telecoms for the dayjob and even then I'm not "senior engineer" (thankfully lol).
@HorsePlay Don't think streaks will be lost thankfully :) Funnily enough the issue started around the time I was logging my streak, was there at the start and gone before I finished the ride.
Mine never updated before the midnight cutoff yesterday yet the streak still shows as it did before the deadline so I suspect the leaderboards are in a "Read-Only" state. I imagine they got the servers back up since I can see them again but for whatever reason they entered a safe mode to protect data and left it there to work on today or just missed it (which happens, I've been there lol)
RFTR was insane. I thought the women's was tense but the boys turned it up a level! Chat was lovely too, first time catching these live and I don't regret staying past 3am both nights to catch it lol.
@stinkyface Knew 6am maths was a bad idea, yep I was doing wattage as if wasn't shared. All good then :)
In the same boat with my metre, blew that fuse testing some mains years ago and haven't bothered replacing it.
How low have you gotten the voltage by now?
@blkwalnutgrwr Nice one! Shame I missed it but thanks for sharing the screenie~
Seems like you and Frank are going to be racing eachother up the ranks now ;)
Swapped the resistor, issue persists!
So that means the ST1480AB chip might be dead. Good thing it's replaceable.
Having to order from China because Mouser, Digikey and Farnell are all out of stock for this chip with an expected wait time of November. Found one on eBay so ordered that. Gonna take a while since shipping seems to be economy.
While I had the board out I gave it some more poking with the multimetre. Traced back the pins on the other side of the chip, they all lead back to the ARM chip (stm32f103VB) as suggested by the datasheet for the ST1480AB. The actual via's are under the chip so I spent a while probing everywhere coming up empty till I realised there were some under the chip I had to probe from behind.
Here's what that all looks like.
The other 4 (3 since 2 are connected) pins coming off the ST1480AB appear to go back to 3 I/O pins on the ARM chip. They'll be programmed in the firmware for reading the data. Assuming those are where the pins are meant to go then no break/short appears to be present.
So with that all in mind it brings me back to ST1480AB is bad or... the Arm chip. Fingers crossed it's the ST1480AB otherwise some sort of hack will be needed to tell the ARM chip to ignore battery info if at all possible.
I'd like to imagine it's ST1480AB that died and in turn caused the resistor to die, or the resistor died and caused ST1480AB to die... Either way it makes more sense that it's the problem. We'll have to see when this replacement comes in... a few weeks >.>
Edit: So looks like even if the main ARM chip is dead some people have managed to extract the firmware from this type of chip already. If this one is dead there could be a chance that I could extract the existing firmware and write it to a new chip that isn't faulty.
Here's a video of someone doing it to the same family of chip.