Uniscan Visa 1.83 Interface build

[uncle_sem]

here says someone got working visa with dosbox, vspe and usb-serial adapters
View topic - Uniscan Euroscan Visa 1.83 fully working on UK cars
anyone know how to do it?

compaq evo n600c, XP SP2, silicom double serial, dosbox 0.74: uniscan runs and recognizes adapter ok (both ports connected to silicom card). connection to car - not checked.
same + Eterlogic VSPE, "serial1 nullmodem server:127.0.0.1 port:5555", "serial2 nullmodem server:127.0.0.1 port:6666" - led for l-line blinks, but adapter not recognized.
so i guess it's fake or miracle.

[manocao]

i tried dosbox this way:
serial1=nullmodem server:127.0.0.1 port:5555 transparent:1 rxdelay:0
serial2=nullmodem server:127.0.0.1 port:6666 transparent:1 rxdelay:0
vspe with two serial ports: com1 port 5555 and com2 port 6666 in tcpserver mode
i use two usb-serial adapters (one is ch340 chip based and the other is prolific2303 chip based)
i tried on xp with uniscan visa 1.83, when i select car, ecu and fault code, L-line led blinks ok trying to wake up ecu for some seconds (although my 1993 corsa-b c14se doesnt have L-line) then K-line led should start blinking but it doesnt (different unsupported baudrate?)
i tried usb-serial adapters in different usb ports (the same adapter as com1 and then as com2), l-line led always blink, if i unplug adapter from interface it stops blinking, when i replug it continues blinking so tcpserver mode is working, interface communicates through usb-serial adapter with visa software


maybe it will never work:

"You cannot run Uniscan software from any version of Windows even in a command window due to com port referencing in the Uniscan software not being Windows compliant.
I have not heard of anyone who has managed to get the Uniscan to work with a USB to serial lead, DOS does not recognise these adaptors.
I have it running on a desktop with 2x com ports and dos/windows 98 installed and also on a laptop with one onboard com port and 1x ruggedized 16bit PCMCIA to serial card made by SOCKET.
16 bit PCMCIA cards are harder to find but you can still buy them, they are marketed more towards commercial buyers who are still using powerful DOS software in industry, also some people use them to get a second com port for weather station software running in DOS.
32bit PCMCIA cards will not work with Uniscan."

source: http://www.obd-codes.com/forums/view...p=14979#p14979

[manocao]

here are two debug files created with dosbox-debug.exe in megabuild6 for com1.
MEGAUPLOAD - The leading online storage and file delivery service
with directserial, only cycles=auto works (cycles=max makes visa 1.83 crash at the beginning).
with nullmodem server (and vspe), cycles=max works faster
com2 still blinks ok but com1 does nothing
please take a look to debug files, maybe you find the communication problem.
dosbox-debug.exe gives a lot of info, i can see what dbcodici.exe is doing/calling at every moment, it is great!

ps: the problem about visa crashing in dosbox with directserial was the configuration cycles=max
when i select cycles=auto, it runs very slowly (3000 cycles) but doesnt crash at all

[manocao]

here is a capture video and pics while debugging visa 1.83 with dosbox
maybe it can help understand how it works dealing with com ports and help us find out how to make it work with usb-serial adapters in xp

video:
MEGAUPLOAD - The leading online storage and file delivery service

pics:
MEGAUPLOAD - The leading online storage and file delivery service

here is an example, see ""multiplex unhandled call..." message while trying to communicate with k-line


here are some relevant messanges from dosbox debugging txt files:
see baudrates (5, 430, 440, 9600, 19200) and word lenght (5 and 8 bit)
ftdi and cp2102 adapter chips support baudrate alias (selecting 600bps = i really get 440bps for example)

0.000 [ 454] Serial1: BASE 3f8, IRQ 4, initstring "realport:COM1 irq:4 dbgirq dbgreg dbgtr dbgaux"
0.000 [ 473] New COM parameters: baudrate 9600, parity none, wordlen 5, stopbits 1
0.000 [ 481] New COM parameters: baudrate 9600, parity none, wordlen 5, stopbits 1
0.000 [ 488] New COM parameters: baudrate 9600, parity none, wordlen 8, stopbits 1
0.000 [ 497] msr interrupt on.
0.000 [ 497] msr interrupt off.
27837.300 [ 31085] read 0xff from SPR.
27837.303 [ 31085] write 0x17 to SPR.
27837.304 [ 31085] read 0x17 from SPR.
27838.377 [ 31089] read 0x 1 from ISR.
27838.379 [ 31089] read 0x 1 from ISR.
27838.380 [ 31089] read 0x 0 from MCR.
27838.382 [ 31089] write 0x 8 to MCR.
27838.386 [ 31089] write 0x 1 to IER.
27838.387 [ 31089] read 0x78 from RHR.
27838.429 [ 31089] write 0x80 to LCR.
27838.429 [ 31089] New COM parameters: baudrate 9600, parity none, wordlen 5, stopbits 1
27838.430 [ 31098] write 0x 1 to DLM.
27838.430 [ 31098] New COM parameters: baudrate 430, parity none, wordlen 5, stopbits 1
27838.431 [ 31105] write 0x 6 to DLL.
27838.431 [ 31105] New COM parameters: baudrate 440, parity none, wordlen 5, stopbits 1
27838.432 [ 31111] write 0x 0 to DLM.
27838.432 [ 31111] New COM parameters: baudrate 19200, parity none, wordlen 5, stopbits 1
27838.434 [ 31119] write 0x 3 to LCR.
27838.434 [ 31119] New COM parameters: baudrate 19200, parity none, wordlen 8, stopbits 1
27838.520 [ 31128] read 0x 3 from LCR.
27838.521 [ 31128] write 0x 3 to LCR.
28103.377 [ 31370] read 0x 3 from LCR.
28103.378 [ 31370] write 0x 3 to LCR.
28103.394 [ 31370] read 0x 8 from MCR.
28103.395 [ 31370] write 0x 8 to MCR.
28103.396 [ 31370] write 0x 0 to IER.
28103.401 [ 31371] read 0x 8 from MCR.
28103.402 [ 31371] write 0x 0 to MCR.
29171.430 [ 32466] read 0x17 from SPR.
29171.499 [ 32467] read 0x 1 from ISR.
29171.500 [ 32467] read 0x 1 from ISR.
29171.501 [ 32467] read 0x 0 from MCR.
29171.502 [ 32467] write 0x 8 to MCR.
29171.506 [ 32467] write 0x 1 to IER.
29171.507 [ 32467] read 0x78 from RHR.
29171.537 [ 32467] write 0x80 to LCR.

75396.839 [ 79005] New COM parameters: baudrate 19200, parity none, wordlen 5, stopbits 1
75396.840 [ 79013] write 0x 1 to DLM.
75396.840 [ 79013] New COM parameters: baudrate 440, parity none, wordlen 5, stopbits 1
75396.841 [ 79021] write 0x 0 to DLL.
75396.841 [ 79021] New COM parameters: baudrate 450, parity none, wordlen 5, stopbits 1
75396.842 [ 79027] write 0x5a to DLM.
75396.842 [ 79027] New COM parameters: baudrate 5, parity none, wordlen 5, stopbits 1
75396.843 [ 79035] write 0x 3 to LCR.
75396.843 [ 79035] New COM parameters: baudrate 5, parity none, wordlen 8, stopbits 1
75396.855 [ 79044] read 0x60 from LSR.
75396.857 [ 79044] write 0x86 to THR.
75396.857 [ 79044] tx 0x86 ("here is a cross symbol, like saying dead") [FIFO= 1]
75646.857 [ 79276] tx interrupt on.
77846.857 [ 81476] tx buffer empty.
91764.502 [ 95394] read 0x 1 from ISR.
91764.503 [ 95394] read 0x 1 from ISR.
91764.505 [ 95394] read 0x 8 from MCR.
91764.506 [ 95394] write 0x 8 to MCR.
91764.509 [ 95394] write 0x 1 to IER.
91764.511 [ 95394] read 0x78 from RHR.
91764.605 [ 95394] write 0x80 to LCR.
91764.605 [ 95394] New COM parameters: baudrate 5, parity none, wordlen 5, stopbits 1
91764.606 [ 95401] write 0x 1 to DLM.
91764.606 [ 95401] New COM parameters: baudrate 450, parity none, wordlen 5, stopbits 1
91764.606 [ 95408] write 0x 0 to DLL.
91764.606 [ 95408] New COM parameters: baudrate 450, parity none, wordlen 5, stopbits 1
91764.607 [ 95417] write 0x5a to DLM.
91764.607 [ 95417] New COM parameters: baudrate 5, parity none, wordlen 5, stopbits 1
91764.609 [ 95425] write 0x 3 to LCR.
91764.609 [ 95425] New COM parameters: baudrate 5, parity none, wordlen 8, stopbits 1
91764.620 [ 95433] read 0x60 from LSR.
91764.622 [ 95433] write 0x86 to THR.
91764.622 [ 95433] tx interrupt off.
91764.622 [ 95433] tx 0x86 ("here is a cross symbol, like saying dead") [FIFO= 1]
92014.622 [ 95664] tx interrupt on.
94214.622 [ 97865] tx buffer empty.

for full txt debugging files, see previous post

[manocao]

this is what dosbox author says:

The logs tell me that the program changes the rate to 5 baud, some sort of black magic. Looking at the timing it seems that the serial port does not accept that speed (but it does not complain). Are Tx and Rx bridged by any chance?
Changing the baud rate does not work with a com port server, so I think you can forget that approach.
---
Well you would need to find a serial port that supports the 5 baud. And even then I doubt it would work good in DOSBox since the timing is not emulated in real time.

[manocao]

what about this ftdi usb-serial adapter? it is supposed to support all baudrates for visa 1.83
http://cgi.ebay.es/FTDI-FT232-RS-232...item2a1158a5da

[manocao]

repeated post

[ashyt16]

Hi, I have been trying to get this piece of crap working for 2 years now. I can get the interface to connect to the ECU, but when it comes to selecting one of the options such as Parameters all I get is garbage and can't make sense of it. Then some sort of box pops up asking me to confirm.

I bought this box from China, so not sure if it works properly or not. The car Iam trying to connect to is a Rover with MEMS 1.6 and is covered by Visa_183.


Do I need the hacked software as the interface uses an Attiny 2313 Chip?

Can anybody help here?

[rehtnap]

which software are you using for starters. i had trouble first off with finding the right program. theres a choice of with atmel and without. cant rember which i use ill bang it on the fiat tomorrow to refresh my memory as to how the connect sequence goes and the prog i got to work reliably.

[ashyt16]

which software are you using for starters. i had trouble first off with finding the right program. theres a choice of with atmel and without. cant rember which i use ill bang it on the fiat tomorrow to refresh my memory as to how the connect sequence goes and the prog i got to work reliably.

Yeh that would be brill mate. The program I am now using is the cracked version from here by monocao. Without it the program doesn't work properly.
The original Visa 1.83 can connect to the interface no problem, however when it gets to the connecting to the ECU stage, all I get is a load of illegible data that is unreadable and then some sort of box with unreadable words and asking me to 'confirm' something. I now know through using the cracked version that this is the 'NO RESPONSE FROM ECU' message.

Why it only gives gobbledegook with the original version I have no idea.
I can post some screen prints if anyone is interested? Also what is this 'AVAILABLE UNITS 16884' that I have seen as I don't get that and what does it mean? If I select F5 for 'Software identification' it tells me I have '0 UNITS AVAILABLE'

Also yesterday I borrowed a very old Pentium 2 250mhz PC from work to see if that would work, but still no go. When checking the state of the ports with MSD.EXE the BAUD rate is only 2500?
When it comes to PC's and technical stuff I'm pretty savvy, but this thing has got me beat.

There has got to be at least one supplier that makes reliable working boxes of this interface.
I'm tempted to buy another from Ebay just to get this out of my head. I want to know one way or the other if I can get one of these to work because I have spent soooo much time trying to get it to work.

[hggh]

Hello!

Sorry my bad english! This prog read 92 ford escort EEC IV?

[paro44]

Hello!

Sorry my bad english! This prog read 92 ford escort EEC IV?

Yes, should work,at least for fault code reading (and deleting?). No live data, actuations or adjustments are available according to coverage list.

[hggh]

Thanks, and 18-19 or 17-48 diagnostic pin k and l line ?

Manocao please send yor uniscan interface schematic.
my email ( no addys ) many thanks!

[dernikov]

Question about "theres a choice of with atmel and without".
I have old Marea and Punto 3pin.
Which version works better from DOS with two serials.
I am confused why you need atmel. I thought that UNISCAN function is to only translate voltage leveles between TTL and RS232.
I will try this schematic
http://storage.fiat-bg.org/Diagnosti...scan_1.83C.pdf
can you tell me is it ok for 3 pin FIat.
Thanks for answer.

[dernikov]

Hi,
I have problem with FIAT BG schematic because i can't get SI9241AEY chip at local dealers.
Is it possible to replace SI9241AEY chip with lm2903 in fiatbg version of UNISCAN schematic. If someone have modified schematic can it post link.
Thanks