Search results

excellent news : the message's structure of your car looks very similar to mine.... Volt, Amp , Soc , Batt Temp, Speed, odometer are there according your odomometer counted 14075 kilometers... here is a link to get an analyse

ok, here is the result for this first capture it is the zip of an excel file. there is some garbage in the first second I forgot to remove... next capture: driving one or 2 minutes, and what is the status of the SoC on the board? also what is the external temperature?

excellent could you make another capture with realterm but ticking the time stamp YMDHS??? so we can check the periodicity of each PID , and also I will be able to use my excel analyser...

@gary: the following reports were obtained with what I call "the garage tool" (Interface & Software used by Peugeot) 1) SoC =99.5% (read 209 on pid 374) 2) SoC=14% (read 38 on pid 374) ; there was only one blinking bar and the SoC will not be allowed to drop much below we have...

you are right... SoC formula is (P1 - 10) / 2 checked on 3 points (and compared using the "garagetool").

I wil check 374 tomorrow.... pid200 contains 2 pairs p2_p3 & p4_p5 proportional to the speed with a better resolution & frequency. offset is 192*256

Hello I know for sure how to ask a "polite question" to the BMU (Battery Management Unit). I mean no christmas tree, in fact this is the exact question from the "garagetool". I know the structure for the answer (46 bytes) , but I have no idea, yet, of what is the use of each of these bytes...

YES & NO : never use a software made for gas cars with your iMiev. the diag plug on Electric cars does not speak the same language as on standard cars. I sent to gary the src of a small program I tested on mine for this interface...

bonjour, congratulation @gary for your clear report. answers to your questions on obdlink: 1) hex 2) exactly 3) using the initial sequence detailed before, the EoL is 0D realterm is a terminal program, for a dialog with an obdlink , you must know the COM port and the Speed. when you install...

here are some details (thx gary for translation) : MsgID 0x373 (frequency 100/sec): 1. The battery current (A) bytes 2 & 3 ( num 0-7), formula (B [2] * 256 + B [3] - 128 * 256) / 100 Extreme values observed: -164.18 + 76.54 2. Voltage: bytes 4 & 5 formula (B [4] * 256 + B [5]) / 10 V Excursion...

the car was moving , see sheet PID_412 where you have speed in kM/H

hello Sorry if I was not clear, the log above is from a peugeot iOn, it should be ( hopefully ) the same for an eMiev. this log is just a passive monitoring of CAN frames... (I started monitoring CAN on prius gen2 & gen3, but do not worry, I will not write about hybrid here). the biggest...

Bonjour, on my side, yes, I can log all the messages. to avoid bufferoverflow, you should change the default interface'speed from 115kbps to 500000bps (once only) a) connect to your interface with a terminal @115kpbs b) send the command "stsbr 500000" c) reconnect @500000bps see this thread...

Bonjour Gary so many questions... regarding hardware: first analysis were done using http://www.obdsol.com/obd-interfaces/obd-interfaces-standard/ with USB link on a laptop. Also, I used a self made interface with a mbed microcontroller. now, I am using this interface...

Bonjour from France, I have, since a month, a Peugeot iOn. this is a kind of iMiev with another brand name... I played a bit with the CAN bus and found some interesting data. have a look there and please confirm it works the same on the original iMiev. maybe you will use an online translator ;)