This is a little bit of kit I got to talk to the Webasto TT-V I salvaged from a scrap Jaguar S-Type, and converts USB-RS232 to the standard car diagnostic ODB connector. (These are a much cheaper option at £4 than the official Webasto diagnostic adaptor & loom which is over £90.
There’s really not much to this adaptor, the only signals that are routed to the ODB connector seem to be the +12v on pin 16, K-Line on Pin 7 & L-Line on pin 15. The main IC here is a CH340 USB-Serial interface, with some glue logic in the form of an LM339 quad comparator.
The reverse side of the PCB only has the power indicator LED.
This is a chip aimed at the automotive market – this is a low power voltage regulator for supplying power to microcontrollers, for instance in a CD player.
The TDA3606 is a voltage regulator intended to supply a microprocessor (e.g. in car radio applications). Because of low voltage operation of the application, a low-voltage drop regulator is used in the TDA3606. This regulator will switch on when the supply voltage exceeds 7.5 V for the first time and will switch off again when the output voltage of the regulator drops below 2.4 V. When the regulator is switched on, the RES1 and RES2 outputs (RES2 can only be HIGH when RES1 is HIGH) will go HIGH after a fixed delay time (fixed by an external delay capacitor) to generate a reset to the microprocessor. RES1 will go HIGH by an internal pull-up resistor of 4.7 kΩ, and is used to initialize the microprocessor. RES2 is used to indicate that the regulator output voltage is within its voltage range. This start-up feature is built-in to secure a smooth start-up of the microprocessor at first connection, without uncontrolled switching of the regulator during the start-up sequence. All output pins are fully protected. The regulator is protected against load dump and short-circuit (foldback
current protection). Interfacing with the microprocessor can be accomplished by means of a battery Schmitt-trigger and output buffer (simple full/semi on/off logic applications). The battery output will go HIGH when the battery input voltage exceeds the HIGH threshold level.
The other day I was given a random pile of car electronic parts from the scrap bin at the local garage, so I decided to do a few teardowns. This first one is a Temic Central Locking / Immobiliser module from a Mercedes van. Judging by the 125kHz stamped on the label, this also has RFID capability.
The casing just unclips, revealing the PCB. Surprisingly for an automotive module, there is no conformal coating on this (they’re usually heavily coated in protective lacquer to prevent moisture ingress).
The large IC from Motorola I’m assuming to be a microcontroller, but I didn’t manage to find anything from the markings. There’s not much else in here apart from some glue logic, and what I think is the 125Khz toroidal antenna in the top left corner.
As there was no other online example of someone converting a glow/nitro car engine onto CDI ignition, I thought I would document the highlights here.
The engine is currently still running on glow fuel, but when the required fuel lines arrive I will be attempting the switch over to 2-Stroke petrol mix. This should definitely save on fuel costs.
The engine in this case is a HPI NitroStar F4.6 nitro engine, from a HPI Savage X monster truck.
Above is the converted engine with it’s timing sensor. As The installation of this was pretty much standard, a complete strip down of the engine was required to allow the drilling & tapping of the two M3x0.5 holes to mount the sensor bracket to. The front crankshaft bearing has to be drifted out of the crankcase for this to be possible.
Detail of the ignition hall sensor. The bracket has to be modified to allow the sensor to face the magnet in the flywheel. Unlike on an Aero engine, where the magnet would be on the outside edge of the prop driver hub, in this case the hole was drilled in the face of the flywheel near the edge & the magnet pressed in. The Hall sensor is glued to the modified bracket with the leads bent to position the smaller face towards the back of the flywheel.
The clearance from the magnet to sensor is approx. 4mm.
Detail of the magnet pressed into the flywheel. A 3.9mm hole was drilled from the back face, approx 2mm from the edge, & the magnet pressed into place with gentle taps from a mallet & drift, as I had no vice to hand.
Initial timing was a little fiddly due to the flywheel only being held on with a nut & tapered sleeve, so a timing mark can be made inside the rear of the crankcase, across the crank throw & case to mark the 28 degree BTDC point, the flywheel is then adjusted to make the ignition fire at this point, before carefully tightening the flywheel retaining nut to ensure no relative movement occurs.
The slots in the sensor bracket allow several degrees of movement to fine adjust the timing point once this rough location has been achieved.
Definitely the tiniest spark plug I’ve ever seen, about an inch long. Some trouble may be encountered with this on some engines – the electrodes stick out about 2mm further into the combustion chamber than a standard glow plug does. This causes the ground electrode to hit the top of the piston crown. (This happens on the HPI NitroStar 3.5 engine). The addition of another copper washer under the plug before tightening should cure this problem.
Ignition module. Due to the depth of the plug in the heatsink head on these engines, I will have to modify the plug cap to straighten it out, as it will not fit in this configuration.
However, ignition modules are available from HobbyKing with straight plug caps, this makes modification unnecessary
The ignition & components used on this system were obtained from JustEngines.
Here is the project I’m currently working on. A completely wearable computing platform based on the Raspberry Pi & the WiFi Pineapple.
Above can be seen the general overview of the current unit.
On the left:
Alfa AWUS036NHA USB High Power WiFi Network Interface
512MB Model B Raspberry Pi, 16GB SD card, running Raspbian & LXDE Desktop. Overclocked to 1GHz.
On the right:
WiFi Pineapple router board
USB 3G card.
The WiFi, Pineapple & 3G all have external antenna connections for a better signal & the whole unit locks onto the belt with a pair of clips.
The Raspberry Pi is using the composite video output to the 7″ LCD I am using, running at a resolution of 640×480. This gives a decent amount of desktop space while retaining readability of the display.
The case itself is a Pelican 1050 hard case, with it’s rubber lining removed. The belt clips are also a custom addition.
Here are the connections to the main unit, on the left is the main power connector, supplying +5v & +12v DC. The plug on the right is an 8-pin connection that carries two channels of video, mono audio & +12v power to the display.
Currently the only antenna fitted is the 3G.
Closeup of the connections for power, audio & video. The toggle switch is redundant & will soon be replaced with a 3.5mm stereo jack for headphones, as an alternative to the mono audio built into the display.
Current state of test. Here the unit is running, provided with an internet connection through the Pineapple’s 3G radio, funneled into the Pi via it’s ethernet connection.
Running on a car reversing camera monitor at 640×480 resolution. This works fairly well for the size of the monitor & the text is still large enough to be readable.
Stay tuned for Part 2 where I will build the power supply unit.
This is the control unit for a Routemaster system, that downloads traffic information for the area local to the vehicle.
Here is an overview of the unit, in it’s aluminium box.
Here is the unit with the top cover removed, showing the pair of PCBs. The bottom PCB is the main control PCB, the top one holds an IC similar to a SIM card & part of the radio.
Here is the main PCB removed from the casing, contains the program ROM & microcontroller. for the system
Daughtercard view. This holds another programmed CPLD, the custom SIM-like IC & the RTC battery, along with some power conversion circuitry.
This is the radio receiver, looks to be AM, the large loop antenna can be seen at the bottom of the box.
Tip Jar
If you’ve found my content useful, please consider leaving a donation by clicking the Tip Jar below!
All collected funds go towards new content & the costs of keeping the server online.