VEMS Bigger Map Sensor Bug?

[black]

Hi,

I replaced the internal 400 kPa map sensor by a 700kPa internal.

I changed the ECU calibration like VEMS Wiki tells -->

http://vems.hu/vt/help/v3/v3_ecu_calibration.html

700 : set "MAP range unit"> 510 and MAP range=778 kPa --> done ans sensor is working fine - tested up to 650kPa on VEMS Gauge

Problem, now I see all map values in VEMStune are half and Top Limit in Tables is 255

When I try to set bigger values than 255 in VE or Ignition table I get an error message --> "VEMS value is incorrect or out of range"

??? What is the issue - did I miss something??

regards

3.6 board, 1.2.10 firmware

update - when ECU is connected, all tables can be set up to 510kPa... but not more than 510kPA

When I log and save a logfile - all pressures are up to 510kPa in this logfile... ECU disconnected

But when I save a config file from the ECU, disconnect the ECU and load the config to VEMStune all MAP values are half in this file

[vems]

Did you change "Table kPa unit" to 4? It's right below "MAP Range Unit" You didn't mention that in your description of the problem.

It's always advised to submit a Sharing Center report from the help menu when you run into problems and include a config and log(s). Then you can provide the URL to either your reseller, or even publicly if you wish so it's easier to help you out.

Thanks much,
Jason

[black]

VEMStune help sais: "Table kPa Unit This is usually set to '2' for standard MAP sensors."

Setting it to 4 when ECU connected is limiting the MAP Sensor Range to 510kPa (should be 1020 like it is on setting it to 2)

When VEMS is connected to VEMStune - all kPa Units are shown right up to 700kPa

When loading the saved config without VEMS connected, all kPa Units are half value...

When opening a logfile without VEMS connected, all kPa units are shown right up to 510 kPa but 510 is still the Limit for Tables

Update

I save the config file from ECU to VEMStune (all KpA right in VT but limited to 510 in Tables)

I disconnect ECU from VEMStune (all kpA still right in VT but limited to 510)

I close VEMStune

I open VEMStune and load the config file again (ECU still disconnected)

All kPa Units are half value now and 255 is max

I edit the kPa AXIS in VE table f.e. 200 (should be 400) to 225

I save the config file

I connect ECU

I upload the saved config file to ECU

All kPa units are shown right... at the place I edited 200 to 225 is now shown 450 in VEMStune when ecu connected...

So this is a ECU offline issue... and an 510 Limit issue even though range is set up to 1020

[black]

calibration

after setting map range unit to double, VEMStune must be restarted to set values higher then 510 in range (after restart, max is 1020)

[black]

Update

when trying to set up a config file and ECU disconnected!

First setting map range unit from normal <510 to double >510

Saving config file and closing VEMSTune

ECU still diconnected

Opening VEMSTune an loading config file

Trying to set range from 510 to 1020 --> getting error message... --> "value out of range"

so one is only able to set up range up to 1020 when ECU is connected


short summary:

ECU is connected
Map Range Unit set to double >510
Table kPa Unit = 2
Burn
Save
Restart
Map Sensor Range (Slope) set to 778 (limit is 1020)
Burn
Save

Now VEMS can show MAP up to 700kPa on Gauge
Limit for Map in Tables is 510 --> error
Logs are shown correct up to 700kPa

Setting Table kPa Unit = 4
Limit for Map Sensor Range is 510 now
Limit for Map in Tables is 255


ECU offline

loading the saved config file to VEMSTune - ECU offline

Map Range Unit is double >510
Table kPa Unit = 2
Map Sensor Range (Slope) is 778 (limit is 1020)

All Tables show MAP values half
Limit in Tables is 255kPa
Limit in Menus is 255kPa

typing 240 in Top of VE Table

Loading this file to ECU (connected) and all values are shown correct (480) but limit is 510 in tables








PS
I have to look at the Sharing Center report function in VEMStune...