:::RHMT::: Real Home Made Turbo

General Category => Engine Management => Topic started by: walter on January 25, 2010, 06:21:35 PM

Title: Romulator problem
Post by: walter on January 25, 2010, 06:21:35 PM
i got already a romulator with keyspan http://www.tripplite.com/en/products/model.cfm?txtModelID=3909 (http://www.tripplite.com/en/products/model.cfm?txtModelID=3909) but i can't install it in my laptop, i havent drivers for Romulator , i installed drivers of keyspan but i needs software for romulator i guess, not sure what to do!!.

any help will be appreciate it a lot!.
Title: Re: Romulator problem
Post by: walter on January 25, 2010, 07:42:06 PM
8 views, no help  :-\
Title: Re: Romulator problem
Post by: Joseph Davis on January 26, 2010, 03:43:31 AM
There are no drivers for the ROMulator, it uses a RS-232 communications protocol.  Either the software you use supports the ROMultor across a COM port, or it doesn't.
Title: Re: Romulator problem
Post by: walter on January 26, 2010, 09:49:10 AM
does romulator should be connected to the ecu then? i tried the keyspan with romulator only in my home, not sure if im doing it right.

thx for help JD.
Title: Re: Romulator problem
Post by: Teg2boo on January 26, 2010, 12:01:23 PM
Why didn't you buy a Ostrich?
Title: Re: Romulator problem
Post by: Joseph Davis on January 26, 2010, 12:05:27 PM
Do the normal stuff associated with legacy serial connections - check baud rate, latency, see what COM port the software is looking for (typically a low number) and make sure the Keyspan cable is coming up under that COM port, etc.

If that doesn't work then get an Ostrich - they are so popular because not having to fuck around with USB-serial cables fucking rules.
Title: Re: Romulator problem
Post by: ratcityrex on January 26, 2010, 01:49:59 PM
not having to fuck around with USB-serial cables fucking rules.

True that!
Title: Re: Romulator problem
Post by: malichite on January 26, 2010, 05:29:22 PM
not having to fuck around with USB-serial cables fucking rules.

True that!
quoted for truth!
Title: Re: Romulator problem
Post by: Teg2boo on January 27, 2010, 12:51:59 AM
not having to fuck around with USB-serial cables fucking rules.

True that!
quoted for truth!
Title: Re: Romulator problem
Post by: Teg2boo on January 27, 2010, 12:52:28 AM
not having to fuck around with USB-serial cables fucking rules.

True that!
quoted for truth!

Self quote quoting quote.
Title: Re: Romulator problem
Post by: malichite on January 27, 2010, 07:50:00 PM
not having to fuck around with USB-serial cables fucking rules.

True that!
quoted for truth!

Self quote quoting quote.
quoted for being a quote of a quote of truth quotes quoted
Title: Re: Romulator problem
Post by: walter on January 29, 2010, 05:40:02 PM
i got another cable, expensive  >:(, samething but i found the drivers in official website and works. ill test it with TE now!
Title: Re: Romulator problem
Post by: walter on January 30, 2010, 09:10:26 AM
well i tried it and works but no 100% smooth, i got erros in some changes i make.

where is an example :

Quote
*** Loading RTP environment..
*** Programmer: 1 COM: 6 Settings: 115200,n,8,1
*** Looking for ROMulator..
*** ROMulator v1.50.  Found!
*** Synronizing ROM to ROMulator...
*** ROM Syncronized! You may now begin editing ROM characteristics.
*** Launch ON/OFF Changed: From: 0 - To: 1
*** Launch Control RPM Change: From: 4000 - To: 1200
*** VTEC Output Line Change: From: 0x23 - To: 0x1
*** VTEC RPM Change: From: 0 - To: 0
*** VTEC RPM Change: From: 0 - To: 0
*** Boost Cut ON/Off Changed: From: 0 - To: 0
*** Boost Cut MAP Change: From: 4000 - To: 2,8
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** RPM Change: From: 6906 - To: 1500
*** VTEC Output Line Change: From: 0x23 - To: 0x1
*** VTEC RPM Change: From: 0 - To: 0
*** VTEC RPM Change: From: 0 - To: 0
*** Boost Cut ON/Off Changed: From: 0 - To: 0
*** Boost Cut MAP Change: From: 1200 - To: 2,8
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** RPM Change: From: 1500 - To: 6900
*** VTEC Output Line Change: From: 0x23 - To: 0x1
*** VTEC RPM Change: From: 0 - To: 0
*** VTEC RPM Change: From: 0 - To: 0
*** Boost Cut ON/Off Changed: From: 0 - To: 0
*** Boost Cut MAP Change: From: 1200 - To: 2,8
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Launch ON/OFF Changed: From: 1 - To: 0
*** VTEC Output Line Change: From: 0x23 - To: 0x1
*** VTEC RPM Change: From: 0 - To: 0
*** VTEC RPM Change: From: 0 - To: 0
*** Boost Cut ON/Off Changed: From: 0 - To: 0
*** Boost Cut MAP Change: From: 1200 - To: 2,8
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** VTEC Output Line Change: From: 0x23 - To: 0x1
*** VTEC RPM Change: From: 0 - To: 0
*** VTEC RPM Change: From: 0 - To: 0
*** Boost Cut ON/Off Changed: From: 0 - To: 0
*** Boost Cut MAP Change: From: 1200 - To: 2,8
*** O2 Function Change: From: 1 - To: 2
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Launch ON/OFF Changed: From: 0 - To: 1
*** VTEC Output Line Change: From: 0x23 - To: 0x2
*** VTEC RPM Change: From: 0 - To: 0
*** VTEC RPM Change: From: 0 - To: 0
*** Boost Cut ON/Off Changed: From: 0 - To: 0
*** Boost Cut MAP Change: From: 1200 - To: 2,8
*** O2 Function Change: From: 2 - To: 0
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Launch Control RPM Change: From: 1200 - To: 3500
*** VTEC Output Line Change: From: 0x23 - To: 0x0
*** VTEC RPM Change: From: 0 - To: 0
*** VTEC RPM Change: From: 0 - To: 0
*** Boost Cut ON/Off Changed: From: 0 - To: 0
*** Boost Cut MAP Change: From: 1200 - To: 2,8
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)
*** VTEC Output Line Change: From: 0x23 - To: 0x0
*** VTEC RPM Change: From: 0 - To: 0
*** VTEC RPM Change: From: 0 - To: 0
*** Boost Cut ON/Off Changed: From: 0 - To: 0
*** Boost Cut MAP Change: From: 3504 - To: 2,8
*** Byte write error! No changes mande! (0x3F)
*** Byte write error! No changes mande! (0x3F)

what is the problem?  :-\
Title: Re: Romulator problem
Post by: Joseph Davis on January 30, 2010, 05:29:48 PM
It's hard to keep an asynchronous transmission timed correctly when you are converting from whatever speed the computer is putting information out on the USB bus, stepping from USB speed transmission to RS-232 via a $20 adapater that cost $3 to make, and having the ROMulator try to decypher it at the speed it thinks shit should be coming in.  I've run into this problem with UTECs, where I can make small changes but the sync errors from trying to upload whole maps trash things.

Also, ROMulators suck.