Как обычно... нажать левую кнопку мыши в районе левой границы выделяемого участка не отпуская протянуть до правой границы выделяемого участка, отпустить... двойной щелчек для восстановления начального масштаба. Спасибо
Поиск: ዘላለም ተፈራ የስነምህዳር ተመራማሪ፣ መምህር - 2656 Результатов найдено
OBD Car Doctor Android functionality Данные логирования (PRO)
inCarDoc
разместил это
10 сентября 2015
OBD Car Doctor Android functionality Данные логирования (PRO)
Alexspb
разместил это
10 сентября 2015
- Последний раз отредактировано 10 сентября 2015
Добрый день! Используя версию PRO записал и отправил сюда, на сайт, логи поездки на работу и с работы. Продолжительность поездки около 1 часа (в одну сторону). В Личном Кабинете все открывается, но графики совершенно нечитаемые. Это скрин
https://www.dropbox.com/sh/ycsmn8iqoudazaj/AAAmBjw3GWKG9qrF_DcGoWoUa?dl=0
Каки образом можно масштабировать картинку с графиком? Без такой возможности никакой информативности.
OBD Car Doctor Android functionality stuck at test protocol 3
inCarDoc
разместил это
25 августа 2015
- Последний раз отредактировано 25 августа 2015
Stuck on some protocol usually means that program does not receive any answer from ECU at specified time. That could be an issue with adapter or with ECU. If you could send us the connection log that might help to be more exact... Switch off then on bluetooth support in phone, plug off then on adapter.turn on debug logging on page Menu-Configuration-Logging, try to connect then send log from the Menu-Configuration-Logging with issue description and car details including year in letter Thanks
OBD Car Doctor Android functionality stuck at test protocol 3
superdml
разместил это
25 августа 2015
I have a 1996 Jeep Grand Cherokee 4.0L which suddenly wont produce spark to start the engine. I purchased a mini OBDII bluetooth interface and paired it with my samsung note 4. I purchased the pro version of OBD Car Doctor because it gives progress of connecting. The interface has a red light on it when plugged in even with the ignition off. I turn the ignition to accessory or on and try to run the Car Doctor. It proceeds to run several test protocols and stalls on protocol 3. I can't retrieve any info from the ecu. How do I get past this? I am trying to determine if the ecu is working ok then wiring and any electronics that might be in the distributor.
I also tried a standalone innovis obd reader and it got a few monitor not run codes and it had a yellow light. According to their technical support their tools are designed not to show any codes until the monitors all have the status of being run. That is useless of course. I had disconnected the battery at one point since the car was running which would cause that. As a side note I have confirmed the coil is ok and there is 5 volt voltage going to something in the distributor (2 out of 3 wires) but can't find any voltage going to the coil yet.
User feedback raw fuel consumption
Administrator
разместил это
25 августа 2015
Yes, all sounds correct. Looks like the observations have some systematic shift around 10%, but random is +-15 remains. I could expect possible influence sampling interval (the less, the better) and altitude (if valuable changes during the trip)... Grate thanks for your overall testing!!! Would be interesting to take and "play" with your data, thanks for the proposition, will contact soon.
User feedback raw fuel consumption
jacksonmacd
разместил это
22 августа 2015
Yes, too many parameters doesn't work well. I loaded OBD Doctor with 8-10 parameters and found that it skipped about 50% of the readings. I've had success recording 5 parameters, but may reduce it to 4 as recommended in the instructions.
As for accuracy of fuel calculation, I always doubt my own work as a first step! Here's the logic I use in the program:
- basic reading is the OBD "fuel consumption" parameter (i.e. fuel consumption rate in litres/hour)
- omit OBD records with null fuel consumption rate
- calculate number of seconds between successive valid readings
- calculate litres consumed during time period = [consumption rate]*[seconds]/3600
- sum the litres for all time intervals
Does that sound reasonable?
In addition, there are times when the engine is running but the ODB is not collecting data (e.g. short trips, incidental time when setting up RV, etc). I've accounted for these times in the calculation of total fuel consumed, but it's an educated guess. However, my gut feeling is that it does not account for the 15% discrepancy.
The discrepancy varies from about -25% to +3% for the different fill-ups. Doesn't look systematic to me. I might be able to correlate the discrepancy to road conditions (e.g. slope, speed), but I haven't done that yet.
Dunno whether you are interested, but I am using this data in a fuel-monitoring program tailored for RVs. It does some interesting stuff about linking GPS with OBD data. I am reaching a point that I will seek beta testers. Drop me a note at rvfuelmon@gmail.com if you want further information.
User feedback raw fuel consumption
Administrator
разместил это
22 августа 2015
You are right, engine ECU "knows" more parameter that it "maps" to OBD-II, but one should also take into account that attempt to collect multiple parameters over "data bus" will takes time and thus increase sampling intervals, and as a result could reduce accuracy... From the other hand OBD-II describes direct consumption parameter (015E), but unfortunately it's very rare implemented in real vehicles.
As for the 15% accuracy, sounds to big... please check if it really "random" that is +-, but not "systematic" error. The systematic error could be due to incorrect set of fuel density or some other permanent coefficients.
User feedback raw fuel consumption
jacksonmacd
разместил это
21 августа 2015
OK - I see what you mean. I captured the MAF, then plotted it against Fuel Consumption and found a linear relationship between the two factors. Also checked the difference between the calculated total fuel consumed and the amount pumped at the service station over 14 fill-ups in my RV. Some amounts were within +/- 5%, but most are about 15%, and 3 fill-ups were more than 25% different. The average discrepancy was 15%.
From my understanding of how the vehicle's computer manages fuel consumption and varies the fuel mixture according to current conditions, it only stands to reason that the computer knows the total volume of fuel that the engine has consumed. It's disappointing that the OBD doesn't report the amount of fuel consumed.
I will put some thought into applying some other factors to modify the relationship and try to get the calculated fuel consumption closer to the amount pumped at the service station.
User feedback raw fuel consumption
Administrator
разместил это
18 августа 2015
Not multiplying... divide - the mass proportion is 1 unit of fuel to 14.7 units of air. The precision of this calculation could be estimated as +- 5% or so. More precise calculation will need much more extra information as: variation of fuel-air proportion, temperature, exact density of the fuel... etc.
User feedback raw fuel consumption
jacksonmacd
разместил это
18 августа 2015
OK - I will check my vehicles to see if MAF is available.
Are you saying this is the method that OBD Car Doctor uses - i.e. to convert the MAF reading into fuel consumption by multiplying by a 14.7 factor? If so, is the same factor used for all operating conditions, or does it modify the factor depending on operating conditions?
I've had to apply a "fudge factor" to my calculations based on OBD data, trying to reconcile with the amount of fuel purchased at the service station. I haven't been able to accurately reconcile the two values. That's why I had hoped there might be a parameter of actual total fuel consumed. I have seen such a parameter on the computer systems for reporting data from industrial engines (e.g., bulldozers, excavators, etc), but it sounds like such is not the case for passenger automobiles.
I appreciate receiving the new information. Thanks.
