|Last modified 2006 MAR 31 18:27:04 GMT|
This is what I envision a prototype of the new trip computer might look like. Note the buttons are general purpose (their function being dynamically defined by the onscreen menu - unlike the OEM trip computer, where each button is single-function). If I can locate a good 4 or 5 position nav button (minimally, the points of the compass, plus optionally a select in the centre position), that may be located to the left of the display, and the buttons across the bottom will not exist. There may be more LEDs (for visual alert cues), although at the minimum, one LED would be standard for optional use by a car alarm.
Ever since I purchased my 1988 XJSC, the trip computer accuracy has been off. The fuel tracking seems fine, but the speed signal seems to be tweaked. If the TC can't track speed, then distance, average speed, and economy figures are all going to be inaccurate. That makes it virtually useless, though as I said, the fuel consumption (actual gallons) coincides with what I pump in, so it is useful. The clock works, the display, while difficult to read (a function of the components, not of some failure), works, and even though the speed signal isn't right, it seems pretty consistent in how much it is wrong (about 40% under).
Using a Fluke scopemetre to measure the signals, I've since determined that the +12V coming from the ECU isn't even near the voltage it should be. I haven't yet determined if the signal is correct at the ECU, or if by bypassing this signal and inputting a known good +12V (BTW, this signal is separate from the one providing the operating current for the TC), the TC might register correct figures.
In late SEP 2001, I took measurements from the (identical) trip computer in my 1985 XJ-S coupe, and considered making a small test apparatus with a dual 555 ic setup and a pair of switches. The idea here is to have two output signals from the box - one for fuel, and the other for speed. At one setting, these two would output constants that perhaps would equate to 10 lph and 100 kmph (use of metrics means that the same circuit should work on US and UK trip computers -- where the GALLON unit is different), and at another, they'd run 25 lph and 200 kmph (or whatever - the idea is to differ the readings). One could hook it up to the TC, reset the TC, then start the unit and let it run for 30 or 60 minutes. then turn the unit off and check the TC readings. If they're spot-on (or very nearly so), then it would demonstrate that the TC head unit is working, and if you have a reading problem, it must be in the signals coming from the speedo transducer or fuel management controller. Note that while I have not produced the test box (which can be constructed for circa US$10 in parts), the speed output signal should be capable of driving the dash speedo - not that I'd ever provide it to someone specifically for calibrating their speedo, but if you change your tyre size, this is something you'll need to fret with, and this sort of test box - if built with the correct parts and operating to tolerance - can provide you with a constant speed signal enabling you to adjust the speedo from a known value to a computed relative value. This would be fairly easy to do - do your math (say you've fit larger tyres to your car and need to increase the speedo reading by 2.5% - so when your original speedo setting claimed you were doing 200kmph, you're actually doing 205kmph) - then hook up the tester and set it to the 200kmph setting (one of the two speeds it should have) and adjust your speedo so that it reads 205kmph. You're done. If you require an instrument calibration certificate, you may have to have your speedo checked and set at a licensed shop (who would probably put your car on a rolling road tester), but for those that this doesn't apply to, the above procedure would probably work quite well.
Nevertheless, I'd been considering replacing the trip computer unit with a new one, of my own design. My idea is to replace the whole dash component with a new one having the same dimensions, but incorporating a backlit (blue) graphic LCD display, several buttons (in theory, not even as many as are currently used, because of how they'd be wired in), one or more LEDs, and a small speaker or piezo buzzer. The LEDs and speaker are optional - they're for future project use. At the heart of the unit would reside a PIC - programmable integrated circuit. In my searchings, I've found that there's a product which may best suit this project - the Tiny or BASIC Tiger stamp ICs produced by Wilke Technology. While I feel quite at home programming in assemblers, the nature of this dictates that future modifications should be something that anyone using it might be able to accomplish without having to become a software engineer. Because this PIC is programmed in a higher level language (their own variant of BASIC), it should be easier for people to pick up on. For this trip computer project however, I expect to do all the programming necessary to implement the functionality, so it isn't as if anyone will HAVE to learn how to program the device in order to build one of these - the code will be provided.
The Wilke product has direct I/O and serial support, right off of the interface pins of the device, which means a lot of complex external circuitry is unneeded. This is a GoodThing(tm), because it simplifies the circuit design and keeps the parts count down.
About the buttons - I mentioned that the new unit wouldn't necessarily require as many buttons as the original. This is because with the advanced display, we can use the buttons as navigation and menu selection, rather than as single-function switches. This plays a big role in future projects. Further, and while I've not yet purchased the development kit (about US$900 - a cost to be burdened by me to initiate development, whereas the actual processor cost is only US$60 in single-unit quantity), it should be possible to wire the buttons using parallel resistance (each button is in series with a resistor of a different specific value, but all buttons feed to one input on the IC), which would mean that all the buttons would utilise only ONE I/O line from the processor, leaving more lines open for other projects.
Initially, the trip computer and clock will be replaced by this project. Later, I hope to use this unit - display, switches, and logic unit - as a platform to which other projects can be added. Some of the initial projects I expect to implement include O2 readouts (a form of detecting what the engine fuel mixture is), temperature monitoring (separatley for the A and B banks, and with more accurracy than the dash gauge), digital tach (again, more accurracy than the dash gauge), door buzzer (to replace the obnoxious door alarm with something less annoying - and importantly - capable of being silenced), and a TH400 (GM) transmission "sport mode" kickdown option (as has been discussed on the Jag-lovers XJS list). I have a rather large list of other projects that could be implemented, including the possible replacement of the Cruise Control ECU (for the purpose of replacing a defective unit).
One of the beauties of this project is that a wide variety of suggested mods for the XJS normally require mounting of a switch someplace, or of a display, etc. Here, we have the basis for many such modification, without duplication of the components, and largely without having to find a place to cram something else.
While the display I expect to use will be graphic (capable of displaying images, not just characters), most of the initial projects that require any display functionality will be text only -- but having the graphic display means that when we do add something that normally would register best as a graphic (a temperature curve, tach, or even the O2 readings), the capability will be there, and can be implemented entirely within code -- no wiring changes whatsoever!
The LEDs and the speaker, which are new to the trip computer, can be used for alerting the driver to warning conditions (like temperature rising above the normal range, or O2 ranges beyond a threshold). Additionally, an LED could be used for your existing (or future) car alarm, or merely wired to the logic unit which could flash it when the ignition is off (giving the impression of an installed alarm).
Interested parties, especially those with electronics and PIC software development backgrounds are encouraged to contact me about participation in this project. Since I'm not expecting to produce this kit as a commercial venture, offers of financial support (in any amount) to defray the high cost of the development toolkit would be most welcome.
The sooner I purchase the development kit, the sooner this project starts becoming reality.
It is my plan to build a new housing for my own dash unit (which will be more of a clamshell design, allowing for easier - and complete - disassembly, along with a new facia panel, which I hope to veneer with wood. To this end, I expect to purchase a pair of the switch facias to either side of the trip computer from a Jaguar salvage house so that I can reface them all with matching wood grain (while retaining my originals in a box). My ultimate goal isn't just to have a working trip computer, and the foundation for future projects, but also to make one that looks more at home in the Jaguar than the original.
Since I cannot expect everyone to have the proper facilities to work with sheet metals (even though the housing isn't complex, it needs to be a snug fit), it is possible that we may use the cage (unmodified) from the existing trip computer to facilitate a no-hassles housing for the new display component. To do so requires popping the molex pins from their connectors, so that the harness can be slipped through the hole in the back of the cage (which is too small to permit passage of the connectors). Unless you elect to take this route, the original trip computer unit will simply be pulled from the dash and placed into a box for safekeeping, and will be unmarred by this project. If you do elect to use the OEM housing, proper disassembly will result in an undamaged and unmodified original unit, which can be returned to the housing using the reverse of the process.
While I haven't yet even produced my own housing (I'll get around to it when I have the development kit in hand and develop a better idea of component placement), I should be able to hand-produce a limited quantity of additional housings, which I'd pass along to interested parties for the cost of material and labor. The same will hold true of the display facia as well (although not necessarily with wood veneer, unless you're willing to bear the higher cost of that additional work).
Some of the various projects which have been conceptualized which could be handled by this new unit, listed in no particular order:
Listing of a particular idea isn't to say that when I get around to building this unit, I will ever implement that myself, but the idea is that all of these are possibilities which are facilitated by the use of a unit such as this.
Many of these signals don't need to be monitored all the time (fuel pulses would, but temperature, O2, and other such readings could be polled in round robin fashion, as they won't change rapidly, and are only displayed for informational purposes). Even the clock, which will be an independant RTC unit, won't be processor speed dependant, and needs only to be read when that is displayed onscreen, or when being used to log an event (BTW - with the trip computer knowing travelled distance, it should be able to log events not only with timestamp, but also with a digital odometer reading, the initial value of which would be entered by the driver).
The choice to place it down near the Cruise Control ECU (which is behind the aux fuse panel) is both because the current trip computer box is much to small to work with for some of the other available SBC solutions, AND because in the new location, it'd be more central to many of the wires that other projects might tie into.
Something that came to me recently as a possible workaround to any power-on time delays would be to trigger the unit from standby to pre-ignition power-on via the door switches (which drive the courtesy lamp delay) - since the unit would normally do a controlled power up and power down using the or accessory voltage line, this would be an alternate signal (isolated by diodes to as to not energize other accessories) which could often be expected within a window of several minutes of ignition (no, it wouldn't take THAT long to initialize, and I'm hoping initialization will be a non-issue anyway).
Presently, the images on this page below are strictly of the OEM trip computer unit, accompanied by brief descriptions and some notes. As the project progresses, additional images and data will be presented here.
Front panel of the removed trip computer.
View of rear of trip computer. To open the housing, you have to unthread the two small hex nuts on the back, remove the screws on either side, and unscrew something from the bottom near the rear (which anchors to the transistor heat sink visible in the upper left corner of the front PCB view). Then the faceplate can be pulled away (straight forward, as it has a pair of shafts which protrude straight out the back). The PCB can be brought out fairly easily (if it doesn't almost fall out, try gently feeding the wires into the housing, which should displace the board).
Closeup of the connectors. By convention, I refer to the one with the pins (the actual conductors) as the male connector, which is shown here on the left, with the red/brown/black leads.
I'm working on obtaining a small quantity of these connectors for the trip computer project, so that the original trip computer can be removed and stored intact (for those like me who don't like to butcher parts). This way, if you decide to try the project (for its other benefits), but actually have a WORKING trip computer, you won't be doing something that can't easily be undone.
These two images show the size of the connectors.
This should give you some idea of how cramped it is where the trip computer is situated - the unit is less than two inches deep - the trip computer isn't the size of a stereo, even though the faceplate is about the same dimensions. The PCB assembly inside is folded in half.
Our replacement Trip computer project will be housing a display and control buttons up where the trip computer originally was installed, but the new logic will actually be located down near the cruise control ECU (above the passenger footwell). Although a trip-computer only replacement would be possible to house entirely in the original casing, the potential for this same project to act as a platform for a variety of other improvements led to the decision to relocate the logic unit - the additional wiring and support circuitry necessary for some other projects would be a pain to route behind the centre dash area.
The front side of the PCB assembly. Lots of components. You can say goodbye to this complexity with the new trip computer, which consists of a few switches, an integrated backlit LCD graphic display panel, and a self-contained logic unit. Very little support circuitry will be necessary for the new unit.
Backside of PCB assembly. Nothing special, though it should be noted that when the PCB is folded over, some pins MIGHT contact. I wonder why they didn't place a sheet of mylar in between the PCBs (or perhaps, one is in there originally - this unit being displayed is a salvaged unit).
IC2, IC3, and IC6 apparently are units which fail (as evidenced by the fact that the backside of this PCB has these components resoldered). Note that this is a scrapped nonop trip computer graciously provided by Walter Petermann (THE guy to go to if you want your OEM Jaguar electronics repaired).
Sean B. Straw
EMail to: Sean.Straw+Jaguar@mail.professional.org