YAPiP - recreating pEEf's approach

I just read that thread - thanks! It certainly gives me insight into what's going on and how engine warmup happens.

I shouldn't actually need the spoof hardware because my new bECU+ (I think I might have stolen that name from pEEf) will now be choreographing the requests between hECU and eECU. This means that I can control the engine mode by whatever means I want (probably just employing different set points like the spoofer's are doing).

Do you know where they got the information to decide at where to put their set points? How did they decide to say an engine is "warm" sooner than the Toyota engineers' choice?

 

Where does the text listed after the numbers come from? Is that your interpretation or is it something that Canview is adding? If it's coming from Canview then maybe you could ask them what they know about these messages?

It looks good to me.

Good luck!

 

Well this is pretty funny...

I was dinking around with a friends DashDaq ODB2 tool and looking at the codes etc. I decided to reset the DTC's expecting them to come right back. Well they haven't come back yet...

Cheapest fix ever? ;-)

I know the codes will likely come back soon - but at least in the mean time I can get a feel for the car's normal operation.

 

Hi kiettyyyy -

Thanks for posting.

Why climb Everest? One doesn't do these things because one has to. However, if your board is reasonably priced and reasonably controllable then I might skip the summit and just hang around the basecamp... so to speak. But, chances are I'd rather climb to the summit.

Right now I'm just reading the "how to climb everest guidebook" and getting my gear ready.

Hmmm, perhaps I'm pushing this mountaineering metaphor way too far???

Yep I know that pEEf's does and I know, in general, which messages will need playing with. I don't know much about your system or the PIS design. Personally, I'm trying to come up with a system that removes the existing NiMH pack entirely - which the PIS system doesn't do (but pEEf's does).

Some questions:
How does your system differ from pEEf's?
What CAN messages are you reading and interpreting?
Will you open source that information? If you don't want to then that's fine - I totally respect your decision. However, I do plan on open sourcing what I do.

Again, if your solution is open enough such that I can go someway to advancing the total PHEV experience then it might be an interesting place for me to start. For example I can work on higher level algorithms to control the "warmup" issues I discussed earlier.

So many wheels to reinvent (or mountains to climb) - and so little time (dang day job get's in the way)!

 

That sounds intriguing! Yes, some simple maintenance may be in order. However, I do think the pack is probably damaged - it's just a question of how widespread that damage is. Maybe the pack will have some salvageable cells that someone else can use. No NiMH for me! (well, I'll be all NiMH for a while yet)

 

Actually the AVR UC3C-EK that I'm using has way more features than needed. So, theoretically, if we were to lay out a board for this it would be more like $150 (or less?).

While we're on the subject of "commercial enterprise" vs. "for-fun-not-profit" - a couple of observations:

1) I have no issue at all with the commercial vendors of the kits and them charging the prices they do. When you start such a venture then there's a LOT more to it than the hardware cost!
2) I can also see why a commercial vendor may be unwilling to share their special sauce. That's fine and is what I expect. However, in this sort of "hacker community" I think it's also a little misguided. The more we all share the better the knowledge base. The better the knowledge base the better the products. The better the products the bigger potential for sales. But, that's a personal choice and I'm not going to mind at all if folks don't want to share.
3) However, I do take issue (and it hasn't happened here - but I've seen aspects of it elsewhere), when commercial vendors who claim proprietary knowledge and then get bent out of shape when someone re-creates the wheel. Err, aren't we ALL standing on the shoulders of the Toyota engineers? Isn't EVERY system attached to the Prius working on the basis of reverse engineering? Haven't all of us "hackers" relied on information gleaned from boards like this that was shared freely?
4) For those who think that an open-source project "kills" the market - I'd suggest the opposite. Especially in the hacker space an open-source project helps nurture the market. There are plenty of real world examples of how folks have made a LOT of money by building product and services on top of open-source. Linux is the granddaddy of them all.
5) To make your fortune you don't have to be the only one with a widget, you don't even have to have the most feature rich widget. You just have to have the complete package that the customer values most highly. The most recent example of this: a 2 year old startup company called Instagram sold for $1BN. They're not the only photo sharing app out there - but apparently they're the one with the most perceived value... Wow.

OK - that was all a little preachy. Sorry about that. I don't mean to come across that way - I just find it an interesting topic.

Finally, much KUDOS to one particular vendor: Enginer. Jack reached out to me to offer encouragement and assistance. I'll be meeting him at the Michigan EAA show next weekend (9th June). I'll also be there with Current Motor - so stop on by if you want to say hi!