"De"-nginer

OK - I'll branch and begin posting my stuff. Thanks.

BTW, I think I'm going to order a Mega today. That stereo plug has now bitten me again - I unplugged it and now I have an "angry dashboard" again (BRAKE, ABS & VSC lights all lit). Also, I seem to have lost power on the OBD socket (but that might have happened prior to the stereo plug issue). The hi/lo CAN signals are still good though (dev board still working).

I really like the idea of having a DuinoMite as a head unit for simple graphical display on VGA and the ability to send and receive CAN messages. I'll do the heavy lifting (bridging and control algos) with the Atmel Dev Board. Maybe I'll shift to the Microchip CAN solution, rather than Atmel, for the final implementation. I have a MicroChip two CAN port dev system my brother's lending me. (He used it when developing his electric motorbike - he's now restoring a vintage Jensen so he won't be working on vehicle data systems for a while!!)

Lots of choices.

 

You should post your eMEGA experience on some forums like The Back Shed and others. it would help the maker to change it and others are warned. Maybe there is some fix.

 

I'm waiting for access to what I thought was the official forum: Ken Segler Designs Forums • Index page I was going to post there.

 

A picture of my OBD2 plug to Duinomite MEGA CANport plug is attached. Also my latest Canview basic file.

 

thanks for that image

 

Canview .bas?

-Htc Tapatalk ( sorry for auto spell correct )

 

I am building a Canview V4 equivalent using a Duinomite Mega which uses a VGA 7" LCD screen and a keyboard. I am programming it using Dmbasic. As Norm seems to have stopped making any more Canviews I am making my own and making it open source. It allows me to make it more applicable for a Lithium pack. Maybe I should call it Canview V5.

DUINOMITE BASIC COMPUTER

 

Here is some more.

 

A that one Yes
Also canbus interface
I did think about using it in the past as my elcheapo bms but did not do it

-Htc Tapatalk ( sorry for auto spell correct )

 

Looking good - some nice improvements to the code and your cabling looks good.

I ordered a Mega and it should be here this week. I'm also going to try porting the CAN stuff into MMBasic 3.2. Not sure how successful I'll be - but if it works then it will give us more structured programming opportunities. If I get it working I'll need to send it to Geoff G to distribute as his license disallows me distributing it.

 

After communication to Norm of http://www.hybridinterfaces.ca I realised that using the PIDs that are being requested between ECUs does not occur often enough to be used for monitoring. Some PIDs need to be requested more often for the purpose of monitoring and some PIDs are not sent at all unless requested by a device like a Mongoose cable used by Toyota technicians. Norm suggested to use the PID list found in the following thread Welcome to Google Docs
It seems to have a wealth of info - thanks Norm. I have attached a copy of the Gen2 Torque PID list to this post. Just need to figure out how to get my Duinomite Mega send a PID request.

 

Excellent find. Do you know what the letters within the Equations stand for?

 

I recognize some of those equations. The ECUs return a PID that only makes sense to another ECU. We need to apply the equation to get a value that makes sense to us. There is a whole thread dedicated to Prius Gen 2 Torque PIDs which needs reading Gen2 Prius: Custom PIDs for Torque (Android App) with formulas | PriusChat

 

Oh man, you are using the wrong connector, never a shorting communication device like a mini-plug.
The right choice for the Can is a Phoenix connector, these come in male and female sections and difficult to come apart by vibration.

 

Lopezjm2001.

For exemple, in order to receive the MG temp, you would send 07 E2 02 21 C3
Then you will receive one response with 8 bytes, this is the first frame. It will be 07 EA 10 aa bb cc dd ee ff gg
Just after send a 07 E2 30.
Then you will receive all the following frames. They will begin with 07 EA 21 , 07 EA 22 ....

(EA = E2+8)

 

Yeah, you live and learn... I'll send feedback to the board maker... In the meantime it's off to get a mini 7.5A fuse for the OBD / DLC3 and hopefully I haven't buggered anything up. Sigh...

 

Well, there are two ends for the cable, the mini plug (3.5 mm) can stay in the board as is, the one you need to modify is the interface to the actual OBDII in the car, easy manageable by any Soft Eng.

 

Thanks. So 07E2 is the header (E2=ECU ID), 21C3 is the mode(2) and PID(1C3), 02 = the number of bytes to follow.

EDITED: E2 = ECU ID, 02 = number of bytes to follow

 

E2 is the #2 ecu. You may talk to #0 and #3.
Why 02 ? That is a good question . I send it since several years ago. It work fine but may be it is not necessary. Could 2009Prius or someone else answer ?