Mitsubishi 3000GT & Dodge Stealth Forum banner

MMCd New Features

231K views 1K replies 146 participants last post by  RealMcCoy 
#1 · (Edited)
MMCd Logger New Features and Sensors Archive Latest Information

16-4-05 Posted V1.8g (see below)

Starting this thread to review MMCd bugs and discuss possible new features. I would also like to see if there are other 3SI members interested in doing SW development. (Dev environment is free and takes less than an hour to set up.)

My goal is to periodically summarize feedback / posts on this page.

NEW SOFTWARE FEATURES
1. Auto Logging on Event (cbatters - done)
2. Peak - Hold (cbatters - done)
3. Upload / Convert to CSV (Shawn ????)
4. Address data scaling issues in log files
5. Big Number Mode (TurboBob?)
6. Graphical Gages
7. User Scaling/Config for Custom Inputs
8. User configuration for graph scaling (colors/scaling/offset)
9. User config for all sensors (colors/scaling)
10. User defined log rates / prelog / postlog
11. User defined graphical display time resolution
12. User defined alarm tones
13. Graphical alarm alert

Other suggestions...

HSLogger Project
Interface for adding additional inputs to the MMCd logger. New inputs include:

o Boost (x1) (Using either 2.5 or 3.0 MAP sensor)
o Wideband O2 (x1)
o Oil Pressure (x1)
o Fuel Pressure (x1)
o Intake Manifold Air Temp (x1)
o 0-15V input (x1) (Fuel pump voltage)

o EGT (x1)

o Other
o Vehicle speed (1) and derived calculations
- MPG
- 0-60 timing
- AWD HP

Models / Pricing
Planning to offer three different models of the HSLogger.

HSLogger Base - Fixes baud rate / RS232 level issues to allow compatibility with ALL Palm devices and includes Speed/Odometer input for performance / MPG calculations. You can also log boost with the unused EGRT input. (~$100)

HSLogger Exp - All of the Base unit features plus six 0-5V inputs (Pressure/Boost/Wideband O2 etc from existing sensors/gages - any 0-5V signal) (~$175)

HSLogger Deluxe - All of the Exp unit features plus higher resolution for low level inputs with signal conditioning for direct connection to sensors. Deluxe version has an "analog front end" that provides amplification, filtering, sensor excitation for direct connection to EGT Thermocouples, oil/fuel pressure senders, etc. (~$250)

I believe the Base unit is is competitively priced based on quality passive cables for $75 from Mirage or $150 for PocketLogger SW + Cable. (In my not so humble opinion, MMCd now runs circles around the PocketLogger SW.)

LINKS
Dmitry's Site http://mmcd.meditprofi.ru/
Protocol Info http://www.syndicate.evilsoft.org/projects/DSMDatalogger/Datalogger_Protocol.html
Boost Logging http://www.3si.org/forum/showthread.php?t=202062&highlight=mmcd
Intake Temp Thread http://www.3si.org/forum/showthread.php?t=217333&page=1&pp=10
Intake Air Temp Research http://www.3si.org/forum/showthread.php?t=98661&highlight=plenum+temperature
Horsepower Calculation http://www.newcovenant.com/speedcrafter/calculators/rollinghorsepower.htm
Boost Controller Thread http://www.3si.org/forum/showthread.php?t=222166
Injector Cleaning Service http://cruzinperformance.com
BlackStone Oil Testing http://www.blackstone-labs.com
Intake Leak Testing http://www.3si.org/forum/showthread.php?t=200417
Inline Spark Tester http://www.3si.org/forum/showpost.php?p=2433324&postcount=25
Rolling Resistance http://www.3si.org/forum/showpost.php?p=3137280&postcount=203
O2 Sensor Wiring / Test http://www.3si.org/forum/showthread.php?p=712579&highlight=sensor+wiring+green+yellow#post712579
Air Filter Restriction / MPG - http://www.3si.org/forum/showthread.php?t=294215&highlight=dirty+air+filter
Data Loggin FAQ - http://www.vfaq.com/TMO/
PocketLogger FAQ - http://www.hywell.org/plhelp/data.html
Online Manual - http://www.ecanfix.com/users/manualcd/gift/3s/



LATEST VERSIONS
MMCd V1.8g - http://www.3si.org/forum/attachment.php?attachmentid=49809
MMcd V1.6n - http://www.3si.org/forum/attachment.php?attachmentid=39998
MMCd Tools (SPoulson) http://mmcdtools.sourceforge.net/
MMCd Tools - Bugfix (.2c) http://lancache.com/images/MMCdTools-0.2c.exe

SENSORS
EGT Probes - http://www.teamrip.com/accessories.html
K Tc Probes - http://www.thermoworks.com/products/probe/tc_wire.html
Easy Fuel Pressure Install- http://www.3si.org/forum/showthread.php?t=213356&highlight=easy+fuel
VDO Pressure Senders - http://www.continentalimports.com/vdo_send_press.html
Fuel Pressure Sender - http://www.dakotadigital.com/Detail.cfm/-/Category=106/PartNumber=SEN-10-2/product.htm

DEVELOPMENT LINKS
PRC Setup for Windows - http://prc-tools.sourceforge.net/install/cygwin.html
Palm SDK for PRC - http://spp.palmos.com/iws/logon.do?...os-sdk-5.0r3-1.tar.gz&back=dl_sdks/sdk50.html
Handspring SDK -
Pilot Hack http://www.massena.com/darrin/pilot/PilotHackTutorial.htm
Palm Simulator - http://www.cs.trinity.edu/ftp/pub/w2k-software/Palm/Simulator/Palm_OS_5_Simulator_Rel.zip
Palm Simulator (PalmOS Site) - http://www.palmos.com/dev/tools/simulator/
Palm Emulator (PalmOS Site) - http://www.palmos.com/dev/tools/emulator/

FAQ - Tuning Information
MMCd Info - http://mmcdlogger.sourceforge.net/#Features
MMCd Tips - Remember to click on the "i" in the config dialogs for more info
TMO Faq - http://www.vfaq.com/TMO/Tuning-Tips.htm
PLogger Faq - http://www.pocketlogger.com/index.php?pid=params&type=dsm


Q1 - What do the letters mean in FLAG0 and FLAG2

Flag 02 status bits
A - Air conditioning relay
F - Fuel pump relay
B - Boost related ???

Flag 00 status bits
T - TDC sensor
S - Power Steering Pressure SW
A - AC switch
N - Neutral
I - Idle switch

Q2 - How do I view MMCd logs on a PC?

MMCd has built in support to upload logs using the Palms archive file capability by simply flagging the log files in MMCd. Files will automatically get uploaded to Palm User - Archive directory on the PC the next time you hotsync.

Simple solution for reviewing logs is to download the PalmSimulator which allows you to run MMCd on the PC. (Just drag MMCd program and log files to the simulator window.)

The other choice is to download MMCdTools which provides a conduit for xfer of logs files as well as conversion of MMCd log format to CSV.

http://mmcdtools.sourceforge.net/

SUMMARY OF CHANGES

KNOWN ISSUES:
Buttons/checkbox controls cause delays in log sampling rate

INVESTIGATION:
Min/Max button
User defined prelog / postlog times
Consider adding default Autolog triggers
Correct slug for EGRT WBO2 inputs - currently hard coded as MAP
Need to confirm Boost solenoid status display
Need to define/implement new log format (mS resolution / Integer / Long / Char )
Scaling for AFR input - Changed in 1.6N
Old 0-5V = 10.0 - 20.0 AFR
New 0-5V = 8.0 - 22.0 AFR
Configurable option for 3S versus DSM mode
- Timing
- Other differences?
 
See less See more
  • Like
Reactions: mike92stealthtt
#77 ·
cbatters said:
Easy enough to add the 3S setting but would like to confirm what the correction is for before adding it. (Perhaps the difference between ECU timing versus ECU + static engine timing.)
Clint
I went through my logs and compared values at 15 different timestamps within the log, both at idle and while driving and found the difference between the DSM mode and 3/S mode was *exactly* 12 degrees of timing every time.
 
#78 ·
Re: Alarm Alert

pocotheeskimo said:
I like everything so far. The peak is nice. If we could get a 4 parameter big number mode that would be cool too, but I'm still happy either way. (I'm not doing any coding so I can't complain =) ). Thanks Clint
If you like peak, you will love the AutoLog feature. No more missed events - no more boring logs to wade through.

I also added PRE-LOG to the latest version to capture a baseline BEFORE the trigger/alarm event. This is in addition to POSTLOG that keeps on logging after the even and then automatically turns off logging.


Clint
 
#79 ·
Steve3kgt said:
I went through my logs and compared values at 15 different timestamps within the log, both at idle and while driving and found the difference between the DSM mode and 3/S mode was *exactly* 12 degrees of timing every time.

My testing shows exactly 10 degrees, everytime. I wonder if there was a change in the PL software. My testing was done on the bench with an ECU.

I got my Pocketlogger software last September.

Bob
 
#82 ·
antero said:
I'm using the latest pocketlogger software (2.03). I'm not sure why some people are seeing 10 degrees, and others 12 degrees difference. Could it be there's some difference between pocketlogger software revisions?
Hmm, I have version 2.02 of the pocketlogger software...

I looked at another older log and I was still getting exactly 12 degrees difference between DSM and 3/S mode.

I didn't know that there was a new version of the pocketlogger software... I'll install version 2.03 and see what the difference is between DSM and 3/S mode.

*edit*
Where did you get version 2.03? I went to the old yahoo pocketlogger group and could only find version 2.02. I checked the new pocketlogger forum but found no mention of where to d/l version 2.03
 
#83 ·
cbatters said:
The core of the expansion interface is a custom programmed microcontroller which takes care of the A/D conversion and the communciations translation. Not sure yet whether I am going to offer kits in addition to assmbled units.

I am thinking about three versions:

1. CommBridge - Solves baud rate / signal level issues so you can use any Palm device.

2. Base - CommBridge + 6 high level 0-5V inputs (from existing gages / sensors)

3. Deluxe - Base + signal conditoning / excitation for pressure senders and Tc inputs. (Saves ~$100 per signal.)
Clint
when do you plan to finish the interface?
what about more than 6 inputs? i think personaly i would need:
1x boost
2x egt
1x wideband
1x intake t.
1x fuel press
1x oil press
1x other

Beer.
 
#84 ·
Beer said:
when do you plan to finish the interface?
what about more than 6 inputs? i think personaly i would need:
1x boost
2x egt
1x wideband
1x intake t.
1x fuel press
1x oil press
1x other

Beer.
STATUS:

SOFTWARE NEARLY COMPLETE
Communciation and analog scanning routines are done. Was working on frequency input for vehicle speed this weekend. (I found a subtle timing bug in the chip I was using but figured out a pretty simple software work-around.)

ANALOG INPUTS
Looking at final design/configuration for base and deluxe versions of the product. The core microntroller I am using has 8 channels of high level analog input but one channel may be required for cold junction compensation on the thermocouples. (Working on the Tc input design now.)

Unit will have a minimum of 7 user accessible analog inputs.

TIMING/PRICING
Sometime later this week I will post a description of the expansion unit along with projected pricing to gauge level of interest. (Thinking about offering a regular price and then a discounted group buy price in lots of 25 or 50 units.)



Clint
 
#85 ·
UPDATE:

SPEED
I got the vehicle speed input working and it is pretty slick. RT/TT speed sensor has ~1.5' resolution (~3700 counts / mile). Need to test a base Stealth/GT3000 model that uses a mechanical speedometer cable/sender to see if it has similar resolution.

I implemented a fairly sophisticated normalized period sampling algorithm that provides rapid high resolution updates on vehicle speed.

Interface provides both speed and odometer data that enables MPG and performance monitoring (Acceleration (G), Deceleration(G), 0-60, 60-0, 1/8 mile, 1/4 mile and equivalent metric statistics)

Very, slick to have speed along with the other data in the logs.

I'll have to talk to SPoulson about adding reports like this in MMCd Tools to take advantage of the new speed data.




Last item on the development list is to finish the analog front end design for direct sensor connection.


Clint
 
#86 ·
That's pretty sweet! This keeps getting better and better.
 
#88 ·
Hey Beer,

Waiting for a couple chips to come in for testing. If the new design pans out, the deluxe version will have 6 high level inputs (0-5V) and an additional 6 programmable hi / low level sensor inputs.

Total of 12 inputs plus vehicle speed.


Clint
 
#89 ·
#90 ·
cbatters said:
Hey Beer,

Waiting for a couple chips to come in for testing. If the new design pans out, the deluxe version will have 6 high level inputs (0-5V) and an additional 6 programmable hi / low level sensor inputs.

Total of 12 inputs plus vehicle speed.


Clint
That is realy nice. When do you think it will be ready and whats the price you will be shooting for? How about DIY kit? (I can solder quite well) :)
 
#91 ·
morfinx said:
Ok this might be a stupid question, but I'm a little confused as to what the latest version of MMCD is, and where to download it :p

EDIT: I have a Handspring Visor, would this cable work? I mean I really just need a serial cable, but it's USB & Serial 2 in 1, should still work right?

http://cgi.ebay.com/ebaymotors/ws/eBayISAPI.dll?ViewItem&item=5703141185
MMCD VERSION
Links at beginning of this thread point to the various versions. You can download Dmitry's V1.5b or the more recent enhanced versions I have posted since November. The post includes a history of what features/bugs were added/fixed at each version.

INTERFACE /CABLE
The problem with all of the current data logger interfaces is that they only work on older palm compatible devices that suppport the non-strandard 1953 baud rate requried to communciate with the ECU.

This interface ommunicates with the Palm at standard baud rates (56K / 112K) so it can be used with any Palm compatible device.

In terms of syc cables, if the cable works with a serial port on the PC it will work with this interface.

PRICING
Planning three models
ODB1 EXPANSION
Building three versions:

1. Base - Fixes baud rate / RS232 level issues to allow compatibility with ALL Palm devices and includes Speed/Odometer input for performance / MPG calculations. You can also log boost with the unused EGRT input. (~$100)

2. Expansion - Base unit plus six 0-5V inputs (Pressure/Boost/Wideband O2, EGT signals from existing gages - any 0-5V signal) (~$175)

3. Deluxe - Expansion unit plus low level inuts with signal conditioning for direct connection to sensors. Deluxe version has an "analog front end" that provides amplification, filtering, sensor excitation for direct connection to EGT Thermocouples, oil/fuel pressure senders, etc. (~$250)


Appreciate your feedback regarding pricing. I believe the Base unit is is competitively priced based on passive cables for $75 from Mirage or $150 from PocketLogger. (In my not so humble opinion, MMCd now runs circles around the PocketLogger SW.)

For group buys (in lots of 25 or 50 units) I should be able to trim some money off the deluxe unit price.)

BEER
As per earlier post, not sure yet if it makes sense to offer a kit based on the support / docmumentation requried.


Clint
 
#92 ·
cbatters said:
...In my not so humble opinion, MMCd now runs circles around the PocketLogger SW...
well, if it does everthing you say it does then thats NOT an opinion, its fact.
 
#94 ·
badass3000 said:
well, if it does everthing you say it does then thats NOT an opinion, its fact.
Feature / function wise MMCd is at the front of the pack. However, Pocketlogger has a different style of graphical presenation (more like Mirage/Palm'n'Stein) with a limited number of separate graphs/large digit displays that some people may prefer.



Clint
 
#95 ·
Steve3kgt said:
I'll buy one of the deluxe units, let me know when I can purchase one!

How did you implement the speed logging? Via the expansion unit?
No one has ever found a register in the ECU that correlates well to speed. (There is a register which seems to indicate whether the vehicle is in motion but it had very limited resolutioin.)

The good news, however, is that the speed sensor is available at the ALDL connector and is easily routed through the cable to the expansion unit.

Along with communciation and protocol translation, the base unit includes circuitry to debounce and precisely measure the period of the speed sensor.

The speed sensor outputs a pulse every 1.5' which provides adequate resolution for doing all kinds of slick things related to distance/time.)


Clint
 
#97 ·
Steve3kgt said:
Any new updates?

Keep up the good work Clint!
The next "update" you will see from me will be a log of speed and fuel pump voltage from the new interface. (Chasing down a few SW gremlins. Individual modules tested OK but there is some subtle interaction.)



Clint
 
#99 ·
Steve3kgt said:
Hows the expansion unit coming along? I'm really eager to buy one and try it out!
I have been fighting a couple bugs that were impossible to solve in the car so I ended up building an ECU simulator so I could do more effective testing/debugging on a bench.

I solved the vehicle speed problem that I had originally attributed to noise from the sensor on the car but it ended up being a subtle timing issue. (Every 1,000 readings or so I would see a 100 MPH jump in the speed.) After the fix, I was able to read 1,000,000 speed readings without a single error. MMCd peak/alarming/logging provides an effectual test environment.

Fighting one more nagging ECU communication issue (random bad data reading) and then I will be back on PCB layout / packaging.

Keeping you in mind for pre-production field testing.


Clint
 
#101 ·
cbatters said:
The speed sensor outputs a pulse every 1.5' which provides adequate resolution for doing all kinds of slick things related to distance/time.)
By my calculations, a pulse (four pulses per speedo rev, right?) should come every 1.2675 feet with 810 rev/mile tires (average mfr. spec) and a 2G speedo gear.

Did you calculate tire circumference from diameter or did you roll the car down the street to take your measurement? I'd like to measure actual rolling average, but I haven't yet.

Assuming 810 rev/mile tires (6.5185ft/rev) and a speedo gear that turns 1.2857 times per front diff revolution (2G speedo), you should see a speedo pulse every 1.2675 feet, NOT every 1.5'; that would be some pretty significant error -- like 18% error!

810 rev/mile becomes 6.5185 feet/rev (1/810 * 5280 ft/mile).

6.5185 ft/rev multiplied by the 2G speedometer gear ratio (28/36) becomes 5.070 feet/sender_rev.

Divide 5.070 feet/sender_rev by 4 pulses/sender_rev.

End up with 1.2675 feet/pulse


With the same tires and a 1G speedo gear (27/36), one pulse should come every 1.2222 feet.

Can anyone find a problem with my calculations? That should land you the most accurate speedometer information possible. Perhaps having a text box to input the tire rev/mile info would be a nice feature.

-Chris
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top