williams805

iTrader: (2)

I just installed a GM 3bar.
As instructed by Rev via PM I hooked signal from MAP to PIN 11 (EXT_MAP). Hooked power and grounds to pins 22 and 3.

Changed settings in TS:
Barometric correction: Two independent sensors
Realtime Baro port: Main board
MAP sensor settings, Voltage input port: EXT_MAP (ADC 11)
Did not move any jumpers in MS3 (as instructed by Rev) I asked specifically about this and I quote:

If you want to use the onboard sensor as a baro sensor, then connect the signal wire to pin 11, and select "EXT_MAP" as the port to use for the main MAP sensor.
Leave the jumper inside the ECU to 1-2 "onboard", and set the Baro sensor port to onboard as well.

I think I know the answer here, but I should also jump the EXT_MAP on the board right?
No, the "ext_map" is only a pullup resistor enabler for 2-wire resistive sensors.

I get an error when keying on that says thereis a conflict and that pin is already being used by MAP. Anyone know what to do here?
If I change to anything accept "Initial baro reading" and Mainboard", I get an error.

Sav states above "It should be as simple as hooking up power and ground to an external MAP sensor, hooking the signal wire to the correct pin/wire on the DB37, moving one well-marked jumper inside the ECU, then activating the external MAP sensor in the settings."

I'm getting conflicting info.

Savington

iTrader: (31)

Rev uses two pins on the DB37 for MAP input pins, so you have two options for an external MAP sensor. One is the EXT_MAP pin, which can be used by an external MAP sensor or as a generic sensor input. The other is a jumper-accessed external MAP input which replaces the onboard sensor's signal.

If you don't want to use the onboard MAP sensor, you can use the secondary MAP pin and move the jumper to the 2-3 position. This bypasses the onboard sensor and lets you use the EXT_MAP input as a generic sensor input. If you want to use the onboard sensor, you have to leave the jumper in the "1-2 onboard" position and use the EXT_MAP input instead. It's a neat way to allow for external MAP sensors without using up an I/O pin.

If you're getting an error, it's because something else is set to use the EXT_MAP pin as an input - just figure out what that other thing is and disable/change it.

I recently added an AEM 3.5bar MAP sensor to Acamas and Rev advised me against using the onboard 2.5bar sensor as a baro sensor - he said the resolution is lacking a bit for use as a baro sensor. He suggested a dedicated 1bar MAP sensor, either a repurposed OEM baro sensor or an aftermarket 1bar sensor.

williams805

iTrader: (2)

When I open "Features list showing I/O", nothing else is using EXT_MAP. The wire wasn't even in the connector until today. The error either points to the MAP using the pin or Baro using the pin depending one what I turn on how I configure it in TS. Not sure what to do. I've PM Rev again to see if he knows whats up.

Thanks for updating about not using on board sensor for Baro.

Reverant

iTrader: (10)

Email me your msq file please.

williams805

iTrader: (2)

I don't know your email address.

Reverant

iTrader: (10)

EXT_MAP is declared as a generic sensor (be default in the basemap for this particular ECU) and analog input sharing is disabled. Either disable the generic sensor or enable input sharing.

Aerodyne

Sorry for reviving this thread, but I'm having the same issue with the can module, where it'll randomly stick at a certain AFR and ruin a VEAL session, and only restarting the car will fix it.
Did you guys ever find out what was causing this? Was this a firmware issue?
Thanks in advance.

Jesse99James

Hmm, the second issue sounds similar to what I experienced with an MS2 I bought from Reverant. I know it wasn't CAN based and I'm not here to bad mouth Rev, just stating that issues DO occur from time to time and a plug and play setup doesn't always worked as designed. My problem was the O2 reading would totally freeze every few days, dead lean. I had my brother, an engineer that designed fuse panels for GM and now builds wire harnesses for Polaris, check my wiring and everything was fine. I sent the O2 back to the manufacturer to test and everything checked out, I just couldn't get it working reliably. I was frustrated and couldn't figure out the issue, plus tuning cold start wasn't working very well either. The learning curve for many of us really is like hitting a brick wall even when stuff works reliably and properly. That experience changed my mind about turbocharging my '01.

*EDIT* Sorry, I just noticed this was a thread revival, no need to reply to my issue and beat a dead horse.