Hi,

I just purchased the Crome Dealer and have trouble setting up Crome. I'm having problem with setting up/Matching my "Real Time Programing" Baud to match "Tuner Comm" Baud and Laptop "Device Manager" bits per second. Everytime i changed my "Real TIme Programming" baud to 38400 and Test Connection it'll go back to 920000. So i decided to leave both "Real Time Programming" & "Tuner Comm" to 920000 and Test Connection on Tuner Comm and get error (\.\\COM12 failed to open) and (Could not connect to the ECU).


Another problem is in my Laptop under Device Manager my Bits Per Second does not have 920000 option, but a closest one of 921600. I try to set it to 38400 and go into Crome and change "Real TIme PRogramming" to 38400 but as i've said above it'll go back to 920000 as soon as i test connection.

 

Demon RTP, Ostrich and Burn2 all transfer at 920k - it's doing you a favor by changing it back. The 921 baud setting will still communicate just fine with both RTPs and the Burn2.

The DATALOG port transfers at 38400 - Tuner Comm baud should be at 38400.

Since nobody reads my manual and PGMFI is down, I'm just going to post this for the next person who searches for it:

Let's start with the Real Time Programming tab:
Plug in your RTP (or Burn2) first, then change the port settings in device manager to 920k (or 921k, whatever). Match whatever port number is shows from there (say port 12) in Crome, then upload a rom. If it's a Demon RTP good luck

Now the Tuner Comm tab:
Plug in your datalogger next, and change that port setting to 38400. Match THAT port number (say port 13), which will be different than the RTP port number, to the Tuner Comm settings. It "should" autopopulate, but it may not. And honestly the "test connection" button doesn't always work, I would load a rom to your chip or RTP first, add datalogging plugin if it's not a Gold rom, then just try live datalogging and see what it does - remember to remove J12 first

PS read the manual in my signature.