Do you still sell the hardware? I have purhased a used SnapOn Verus - that perhaps can connect to the Jimny from 1999 (it has worked on a 1994 Audi). I have 7 different protocols I can choose manually. But incase it does not work - we need a possibility to read different values while the engine is running.
Not yet, I'm having some issues with the firmware which isn't running properly on the production boards, I've spent all day on it today and will be working on it over the weekend as well. I still have some work to do on the PC software as well.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
I've now sold out of the SDL Interfaces so I'm putting in a lot of work on this. The interface firmware will be upgradable so I'm currently working on ensuring that the update routines are 100% bug free so no-one ends up with a useless interface after attempting an update. The main firmware is functional for both SDL and KWP protocols and I've also done a lot of work on the new PC software. I hope to have the first beta release in a couple of weeks, the hardware also has support for ISO9141-2 and CANBus - support for this will be added in a later release.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
According to GM factory manual for this year Metro Pin M of ALDL goes to ECU pin B12 and is labeled Serial Data Output. Now this particular ECU maybe does not
support SDL, but I have read in other forums (just can't find it now) of guys successfully connecting to these ECU's using RV and TunerPro, so I have some hope.
At this time I do not have another interface I can test with, but with the signal voltage pulled low no communication is possible.
I'm not certain if this is the cause of your problem, but, you should be aware that the Swifts of the era (and I suspect also the Metros), had the ALDL connector under the steering wheel, but it was not actually connected to the ECU, and, the ECU does not support SDL communications.
I'm having issues connecting to ECU 33920-61E11 (1994 Geo Metro California emissions) using SDL interface and ALDL adapter cable.
RV connects to SDL interface but no ECU id or data, just Bad Data Counts.
I have have hooked AES LineSPI between SDL interface and ALDL adapter for some scope probing.
I do have 12v on pin 16, ground on pin 5 and 5v on pin 9. Now as the USB is plugged in to PC the 5v is pulled down to 120mv and when CONNECT is selected the voltage toggles up to 4.9v x7 for about 6.4ms ten back down to 120mv for about 250ms and this cycle just keeps repeating.
I'm thinking this should be in reversed, SDL toggle voltage down x7 for 6.4ms and let it up for 250ms in order for ECU to respond.
Just Came across this thread, had been hasty to order the SDL interface cable for the indian suzuki cars, hopefully it would work on the gypsy tomorrow.
Pictures of the first interface, this will be my development PCB. There are a couple of parts missing which are for the oscilloscope add-on and one resistor missing because I ordered the wrong size part!
I need to make a jig so the cases can be milled to suit the connector, do some more software development and, most importantly, get some testing done on an actual vehicle. The processors need to be programmed before they are assembled on the PCB, I have parts coming for the programming fixture. Once all that is done and I'm confident that the reprogramming process is robust then I will be able to ship, I'm very wary of shipping an under developed product as I really can't afford t to have to recall interfaces from all around the world to 'unbrick' them.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
There hasn't been any real progress lately because of other priorities and because of building work, the window fitters should be finishing this week at which point I will be able to put my lab back together again. The building work has been much more disruptive than I was expecting, I have managed to do a little work on the software but I still haven't built an interface yet. Winter is almost upon us now and that tends to be the ime when most of my development work happens because it is too cold and wet outside to do other work.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
The new PCBs arrived today, I'm hoping that there are no errors. I'm a few parts short still but I should be able to get a few built with enough functionality to crack on with the software development.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
I've had a little bit of a redesign. I got frustrated with the lack of resolution of the scope function on the Suzuki SDT so I've redesigned the PCB so I can add an adapter for a dual channel scope. This capability isn't going to be in the initial release but may be added to the firmware at a later date. I stopped the original PCBs and the new boards are due in a couple of weeks.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Hi
I am trying to keep the cost down to £55 plus shipping. I don't have a date yet, I need to test the production units and produce a working version of the PC software. The firmware for the interface itself looks OK for a first release, I will add additional functionality to that following the first release of the PC software.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
I'm waiting for the PCBs to come in, they are on a long order time to keep costs down. I should have enough parts to assemble four or five units for test once I get those. The firmware for the interface works reasonbably well, I can reflash the nterface and talk to SDL and SDL-KWP ECUs. The PC software is making slow progress, I want to ensure that it is very modular so I will be able to add additional functionality later. My main priorities are to ensure that it supports multiple protocols and to improve the logging. I want to have a datalogger that works more like the TunerPro logger which allows you to replay data - I use that a lot to examine runs, changing the data displayed by the graphs to check different items.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
You can increase or decrease the idle speed to check that the ISC is functioning. The ECU will only let you do this if certain conditions are met, usually this is idle switch closed, vehicle speed is zero and there are no current fault codes, you can, of course, clear fault codes before starting a test. This is one of a number of tests that can be performed, how many tests are available depends on the vehicle, OBD2 vehicles have the most controls, primarily, because they have more to go wrong.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Hi, I just took a demo of launch diagun / master & came t know that rpm of maruti car can be increased or decreased with scanner, is it possible to manage the RPM's with scanner?
I have to create an ECU simulator for this project which opens up an interesting possibility. This interface will have support for SDL, KWP and CANBus so it will be possible to add additional software to allow the interface to be used as a protocol interpreter, reading data from a port configured for OBD1 and transmitting it in OBD2 format on another port. The only additional hardware that would be needed would be a Y-cable, with pin-9 wired where applicable. It is only possible to have two ports at a time so the interface would have to be configured via a PC/laptop as an OBD interface or as a protocol interpreter; as an OBD2 interpreter the full OBD1 capability wouldn't be accessible but it would add the possibility of hooking up to a Scangauge or similar. I have a V-Checker on order for development purposes, as its cheaper than the SG.
Thank you for your kind offer but I now have the data for the Indian market cars, so hopefully I shouldn't need an ECU. I have a crude prototype interface that will scan an ECU and I'm writing new PC software to communicate with the interface. I have discovered that all KWP OBD2 ECUs also have this protocol which is used by the Suzuki dealer scan tools so I am able to use Euro and US market ECUs for software development.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Are you suggesting that this could work as a "protocol converter" that would let something like a Scangauge communicate with the OBDI/SDL ECUs? It sounds too good to be true.
Yes, thats correct, in fact its a little bit simpler than I first thought because the microcontroller I intend to use has a dedicated CANBus interface so there will be three ports (2 serial and the CANBus) available at any one time. The PCB is designed for CANBus but its not fitted on the processor that I'm currently using on the prototype interface. How well it will work with SG or any equivalent will depend on which particular PIDs they require and whether they are available from the OBD1 interface.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Are you suggesting that this could work as a "protocol converter" that would let something like a Scangauge communicate with the OBDI/SDL ECUs? It sounds too good to be true.
I have to create an ECU simulator for this project which opens up an interesting possibility. This interface will have support for SDL, KWP and CANBus so it will be possible to add additional software to allow the interface to be used as a protocol interpreter, reading data from a port configured for OBD1 and transmitting it in OBD2 format on another port. The only additional hardware that would be needed would be a Y-cable, with pin-9 wired where applicable. It is only possible to have two ports at a time so the interface would have to be configured via a PC/laptop as an OBD interface or as a protocol interpreter; as an OBD2 interpreter the full OBD1 capability wouldn't be accessible but it would add the possibility of hooking up to a Scangauge or similar. I have a V-Checker on order for development purposes, as its cheaper than the SG.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Yes I will add that functionality in time as well as OBD2 compliance for ISO9141 and KWP2000 but I can't give any timescales for this. Today I was successful in getting the prototype tool to scan an ECU for the first time, its a little buggy and still needs a fair bit of functionality added but its still making progress, albeit rather slow as it has to be developed in spare time between ECU repairs and building SDL interfaces. I also need to develop new PC based software as it is not possible to make RhinoView multi-protocol compatible.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
I now have a prototype interface taking shape, the hardware design is done and software is being written and tested. This afternoon a box of 100 connectors arrived:
This interface will be built into the connector housing as before but will use a microcontroller to achieve the timing accuracy required by the KWP2000 specification.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
The version of KWP2000 that the ECU uses can be tested using an ELM tool and sending the AT commands described below:
at z at h1 at sp5 at sh 8111F1 (or 8101F1) 0100
If the ECU returns a 7F response to the 0100 command then that indicates that it is KWP2000 but is not OBD2. An ELM tool cannot be used to establish any usable communications with the ECU but I am developing a new tool that will be compatible.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
RhinoPower Ltd is working on an interface for ECUs that use the SDL/KWP interface, this is the format typically used on OBD1 Suzukis worldwide from 2001 up until approx 2010 when CANBus was introduced globally. SDL/KWP is a proprietary implementation of the KWP2000 protocol.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
