Folks, for those of you with microwidgets, I've made a complete rewrite of the star trek software.

This image was taken after testing it on my car this evening, with the throttle sensor deliberately disconnected...



It will offer a much larger range of ECUs than the original version. At the moment it's been tested on the coupe 16v (IAW P8) and nothing else; however at present it should also work on the IAW 16 - 900cc, 1000cc and 1100cc FIRE engines for MK1 Punto, Cinquecento, Seicento, Lancia Y and suchlike, and the IAW18 - 1242 MPI FIRE engines, Delta/Dedra/Tipo/Tempra 1.8, and Alfa 1300 boxer.

Next on the list is the coupe 20v/vt, and the widget (so you can get full detailed text results of the error store), after that we'll have to see. Sadly the VIS is not on my roadmap...

It's completely compatible with all previous versions of the microwidget - though to use with Bosch ECUs you'll need to make a slight modification, as with the widget. Not relevant yet since it doesn't do them yet!

This is very much pre-production code; I'm just exposing it for comments and bug reports, pretty please! Note that this won't work with anything since about 2001 - anything after that should be OBDII.

As I improve/bugfix/extend it, it will be in the same location:

http://www.nailed-barnacle.co.uk/coupe/startrek/startrek2.exe

Neil

Hi Neil

Do you have any plans for the 1.1 seicento (mpi)

Cheers
Sam

neil did you manage to get the microwidget working with the 20v/vt in the end ?

Not yet, SB, but I've got much better hooks in the software this time around. I think there's a much better chance of it working. It's the module I'm working on now; once that's in, it's a lot easier to get the 2.10.3 and 2.7 and 1.7 Bosch units talking. Biggest problem is cars to test on...

Sam, it should work for 1100 Sei, if it's a single point injector. It's on the list, IAW16 ECU. I don't have any reference for the MPI; it could be an OBDII type.

hi Neil,


Do you still want a crack at the Punto GT widget??

regards

Marco

im 99% sure the mpi is not OBD11 compatible if you need a 20vt or a sei to test on, im sure i can spare you a day with them mate

Cheers
Sam

was that meant for me?

no mate

Looks really good Neil. I must confess to being ignorant of the startrek/microwidget setup - does this mean that this software could also be used by connecting a widget (not micro) to a laptop?

If not, and you do get it going with the 20VT ECU, I'm going to have to investigate the microwidget further......

In order...

Marco, Punto GT is on the list, but the 20vt is obviously next.

Sam, it occurs to me that the MPI 1242 ECU may work on the Sei... thanks for the offer; you're a bit far for a day trip so let's see what happens first.

Matt, my firm intention is that the widget should talk to this software; that way it'll be able to talk to any of the coupes that have a widget, plus anything else directly. This was actually the original idea for the software; that the widget would mediate the comms and the computer the display. But it turned out not to be too difficult to add a display, and the widget was born...

im a little dense plus tired does that mean startrek2 will work with any widget as this would be great

if not could a micro widget be knocked up

as for the punto gt widget i can get donor ecus or a car if needed

Startrek 2 *will* work with any widget, or with a microwidget.

But it doesn't yet - I'm still working on it.

In about a month I start some heavy open university studying so it'll probably slow development somewhat...

aaah i was gunna test it today on my widget it looks like a really good gadget and some what like the nissan r34 gtr on board cumputer ideas ideas

a nice 16vt opening screen would be ace

anymore news on this?

At the moment, not yet. There's a little more development happened: it now uses a common front end and a big pile of ECU definitions hiding in an XML format, which simplifies things once it knows how to do one type of ecu - it can then do any from that family. But it's not finished, as I said, I have not only full time work, but a full time open university master's degree to study, and I have to prepare for the thesis next year.

At the moment I have no microwidgets available. I just used the last of my circuit boards and I don't want to get into ordering more at the moment. However, I have located an OBDII reader unit which I am currently investigating to see whether it will serve the same purpose with an adaptor cable.

Damn, that didn't work... meh.

i would be happey to put my name down for the new widget....my furby didnt go to plan lol

Unfortunately I'm up to my ears at the moment - I was hoping that a usb obdii adaptor might be used, but the first test was not successful; I need to find out how they've dealt with the read and write on the K line. If it's a software link, I might still be in luck.

Aha! I am the daddy!

I've modified the original startrek software so that it will work with this commercial OBDII reader: http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=300329765991

This part comes with an adaptor cable which takes the KL and power lines to connectors; adapting that to the remote power cable and fiat connector means it can be used with a *new* version of the original startrek software. It will *not* work with the original version available on my site at present; if you want to play, drop me a line.

You can of course simply run leads from the appropriate pins on the OBD connector; I've soldered in the proper plug - but the wires aren't as robust as the one's I've used on my own widget.

I'm about to mail the importer there and see if he can supply ready made cables with a little more strength

Neil

Do you get any additional control over the obd2 interface that you don't get with the microwidget ? (thinking along the lines of will it work 'better' with the 20vt ?

No, it turns out that the designer used an adaptor chip intended for OBDII which automatically loops back the K to the L line, so you see whatever you've sent and it expects the K line to be bidirectional with a single control on the L line.

The 16 uses send on the L and listen on the K; the 20 doesn't use the L at all and uses the K bidirectionally. The optical vag-com adaptors kicking around on the net use RTS to provide a negative supply and DTR for a positive feed for the optos; DTR is toggled to provide the slow baud intialisation byte.

This thing works the same as my USB adaptor with the link in, or the widget in 20 mode (again, with the link in) - anything sent on L is linked to K, so it's seen by both ends.

I need to have another look at the code for the 20. I may try something on command line for testing - interested in testing?

What I am going to do is make my software generically so it will work with either system; it looks like it's just an extra read is required immediately after the write.

Neil

pm sent

I wish i knew what you lot are on about.

Here's an easy one then: anyone with a 20vt close to Hemel want to volunteer for some tests?

im not close, but i will happily volunteer my car for the day

Thanks for the offer, Sam, let's see first if someone closer can help. No point burning petrol we don't have to!

Id volunteer but I'm a distance away, my regular return trips to a Watford data centre mean I know it's a long way down. But if no-one else can make it, would be happy to come down. Where are you, Sam? I would also add that Taffy20vt's code reader didn't like my car much...

I haven't really looked at this at all, just came across it on t'web. Dont know if it works or is useful or who/where it comes from originally:

http://forum.alfa145.com/index.php?showtopic=11560&mode=threaded&pid=125621

The first one is Furby's coupedignostics widget, I think.

I am rather up to my ears at the moment, hence no work. But I do now have a working USB/OBDII/Coupe adaptor.

I am rather busy, but did try the obd connector on the 20vt and didn't get anything. I will arrange to come over when i have some free time (I am off next week until the 7th so might be over your way at some stage Mr Barnacle).