I²C RTC DS13072Z
Thread Starter
Senior Member
iTrader: (1)
Joined: Apr 2011
Posts: 1,332
Total Cats: 87
From: Columbia, SC
So, I decided to guinea pig a $2 RTC I2C module and see if anything happened. It let ALL the magic smoke out. Actually, it did nothing. And I'm kind of curious if someone would care to chime in as to why they think this is. I'm assuming it just has to do with the format of the string this outputs vs. what MS expects. Figure before it joins my box of random components, I'd make sure there isn't something I've overlooked.Details as follows:
DS13072Z (IC RTC CLK/CALENDAR I2C 8-SOIC)

Wired as follows:
GND -> H6
VCC -> H5
SDA -> H4
SCL -> H3
No response from the RTC settings in TunerStudio. If you click save time it goes to Jan 1, 2000 and starts counting.
(don't mind the ghetto-fabulous wiring job)

EDIT: I accidentally a 2 in title. my bad.
DS13072Z (IC RTC CLK/CALENDAR I2C 8-SOIC)

Wired as follows:
GND -> H6
VCC -> H5
SDA -> H4
SCL -> H3
No response from the RTC settings in TunerStudio. If you click save time it goes to Jan 1, 2000 and starts counting.
(don't mind the ghetto-fabulous wiring job)

EDIT: I accidentally a 2 in title. my bad.
That's not the correct component to use. Not all RTCs will work.
Furthermore, it it illegal to use an RTC module not authorized by the firmware developer, James Murray.
Furthermore, it it illegal to use an RTC module not authorized by the firmware developer, James Murray.
It's not illegal to hook up anything you want on your board.
It is illegal to breach the firmware's license agreement, which states that you can't use the knock sensing of the firmware if you don't have a licensed knock module/hardware.
It is illegal to breach the firmware's license agreement, which states that you can't use the knock sensing of the firmware if you don't have a licensed knock module/hardware.
Thread Starter
Senior Member
iTrader: (1)
Joined: Apr 2011
Posts: 1,332
Total Cats: 87
From: Columbia, SC
I find this whole situation interesting, and it honestly causes a lack of respect for the company. The thought of an ecu designed to be DIY and budget forcing you to use their RTC module with a 3250% mark up is laughable.
I know I will in inundated with comments about research costs etc, but adding an RTC module to any project you have control of the code for is fairly straight forward, something I have done a dozen times. There's no excuse for a legally binding contract requiring you to use such expensive parts.
No one forces you to use the RTC module.
If think its fairly straightforward to add the RTC code, why not hack the source and make the DS13072Z module you have work with the MS3? I never saw the MS platform as a budget platform, the open nature of the platform was what appealed more to me.
If think its fairly straightforward to add the RTC code, why not hack the source and make the DS13072Z module you have work with the MS3? I never saw the MS platform as a budget platform, the open nature of the platform was what appealed more to me.
Thread
Thread Starter
Forum
Replies
Last Post






