romulator problems
Posted: Sun Mar 20, 2005 3:24 pm
Hello All,
I've been a hondata user for a number of years now and have recently had some problems with Romulator. I have an s200 system with datalogging and all. I hooked up romulator, created my rom that I needed in Romeditor V3.5xx. I use usb->serial cables to connect to the hondata box and Romulator. I've never had problems with them before. I connect to the Romulator on COM3, datalog on COM4. Romulator connects just fine in the settings menu. I tweak my rom image as such and successfully download my rom to romulator. The car throws a check engine light and my s200 box is blinking slowly. The manual says a slow blink is improperly inserted chip/emulator or bad rom. Well, it's not either. Can't connect to the s200 box thru hondalogger either.
So, I decide to burn the exact same rom image to a chip and I turn the key and no check engine light, s200 has a solid light and I can datalog in hondalogger sucessfully. I've never had any problems thru the tons of cars I've tuned before but this has me stumped. I can successfully connect to Romulator and download an image to it just fine but something is obviously amiss. Anyone got any ideas? I hope it's not a case of a bad Romulator. Does hondata repair/test Romulators for customers?
I have a feeling xtronics will say it's fine. If I use the xtronics software to load the .bin file to the romulator it says successful but I still get the check engine and unable to datalog problem. What gives? I have the exact same setup I've always had with the laptop, usb->serial cables and all. I'm really stumped.
TIA,
steve
I've been a hondata user for a number of years now and have recently had some problems with Romulator. I have an s200 system with datalogging and all. I hooked up romulator, created my rom that I needed in Romeditor V3.5xx. I use usb->serial cables to connect to the hondata box and Romulator. I've never had problems with them before. I connect to the Romulator on COM3, datalog on COM4. Romulator connects just fine in the settings menu. I tweak my rom image as such and successfully download my rom to romulator. The car throws a check engine light and my s200 box is blinking slowly. The manual says a slow blink is improperly inserted chip/emulator or bad rom. Well, it's not either. Can't connect to the s200 box thru hondalogger either.
So, I decide to burn the exact same rom image to a chip and I turn the key and no check engine light, s200 has a solid light and I can datalog in hondalogger sucessfully. I've never had any problems thru the tons of cars I've tuned before but this has me stumped. I can successfully connect to Romulator and download an image to it just fine but something is obviously amiss. Anyone got any ideas? I hope it's not a case of a bad Romulator. Does hondata repair/test Romulators for customers?
I have a feeling xtronics will say it's fine. If I use the xtronics software to load the .bin file to the romulator it says successful but I still get the check engine and unable to datalog problem. What gives? I have the exact same setup I've always had with the laptop, usb->serial cables and all. I'm really stumped.
TIA,
steve