Re:F1 2014: All aboard the 'power train' - new rules explained
by kayoone on Tuesday December 03, 2013 @10:01AM
(#6840617)
as a huge F1 fan and software hacker id love to hear more, but i guess its all under NDA right ? :/
Re:F1 2014: All aboard the 'power train' - new rules explained
by pavanred on Tuesday December 03, 2013 @12:01PM
(#6841507)
I love F1 and am really interested to know more. But, as kayoone mentioned there probably would be a NDA.
If you have a blog, you should put your url out here.
Re:F1 2014: All aboard the 'power train' - new rules explained
by T-zex on Tuesday December 03, 2013 @08:58AM
(#6840228)
Wow! Have you developed the software for the ECU?
Re:F1 2014: All aboard the 'power train' - new rules explained
by pbo on Tuesday December 03, 2013 @09:28AM
(#6840414)
Actually I distribute power from the battery to other subsystems, so it's rather far from the ECU.
Re:F1 2014: All aboard the 'power train' - new rules explained
by zdrummond on Tuesday December 03, 2013 @11:39AM
(#6841323)
Can you do an AMA? I would love to hear more!
Re:F1 2014: All aboard the 'power train' - new rules explained
by pbo on Wednesday December 04, 2013 @05:18AM
(#6846025)
Even though the work environment is peculiar, the technical contents itself is far from exceptionnal, really.
If you'd like to read more about this kind of systems, this document could be a starting point: http://www.ti.com/lit/ml/slup232/slup232.pdf
It sums up pretty well the stakes and technical challenges with digital power supplies.
This kind of development is very demanding, because you can't afford to leave any bugs in your program but at the same time you're always shipping late because of tight schedules and often blurry specifications.
On top of that hardware and software development cycles are concurrent, so no target hardware available when you're writing your code.
In these conditions the only way I found to have something that works is to keep it very simple:
Also, no compiler optimizations.