Corrupt Bluetooth data

[perboddum]

Hi

Have issued an error report on a mysterious BT problem with Vems BT adaptor.
I get wrong online values when using VemsBT module on my laptop and VemsDisplay.
I get correct online values when using a SocketBT (from socket.com) module on my laptop and VemsDisplay.

This is done with a laptop with buildin BT (and physical COM1 port) and Vemstune (latest version)
Log values and realtime data is different When using VemsBT and SocketBT and COM1
SocketBT is a serial BT module from Socket.com that I have used for many years in industrial applications with great success.
Both adaptors is supplied from Vems 5V on pin 28 to serial pin9

-----------------------------------------------
With SocketBT EGO value is fine and constant
With COM1 EGO values is fine and constant
With VemsBT EGO value is running up and down
-----------------------------------------------
With SocketBT EGO correction is changing
With COM1 EGO correction is changing
With VemsBT EGO correction is allways 100%
-----------------------------------------------
With SocketBT IsAccel works
With COM1 IsAccel works
With VemsBT IsAccel is ON all the time
-----------------------------------------------
With SocketBT IsKnock works
With COM1 IsKnock works
With VemsBT IsKnock is ON very often
-----------------------------------------------

The above is showing for display and logvalues.
This is only some of the online values I have seen. Wonder how many more there is wrong with the VemsBT connected.

When I use VemsDisplay on my phone i observe the same pattern with wrong values. Only the SocketBT returns the right values.
However VemsDisplay (latest version) cannot display l/100km (always display 255.0), no matter what you set fuel injector size to. Vemstune do display l/100km correctly.

I have attached 2 logfiles. One using the VemsBT and one using SocketBT. Here you can see the the above differences.

http://www.vems.hu/files/perboddum/BT/v3.3_u008223-SocketSerialBT.vemslog
http://www.vems.hu/files/perboddum/BT/v3.3_u008223-VemsSerialBT.vemslog

regards
Per

[perboddum]

News update

When using the SocketBT with Vemsdisplay several values in Vems ECU gets changed and flashed over time.
This makes the engine difficult to start and runs bad, until I connect my laptop via COM1 and download my latest config again.

If I use Vemsdisplay with VemsBT everything works fine, but EGO value + PulseWidt (and other values) is going up and down. Those values is stable in Vemstume on the laptop and in Vemsdisplay with SocketBT module.
Also several of the flags (Knock+accel and others) is totally wrong displayed.

Vemsdisplay runs on a Samsung Galaxy Note 3.

Per

[mattias]

I also discovered a problem. When connecting a specific Android unit (Samsung S4) with firmware 1.2.26 and VemsDisplay app version 3.3 the engine starts running rough and strange. Disconnect and all is fine. Connect with another Sony phone and all is normal.

http://www.vems.hu/wiki/index.php?page=IssueReports

[perboddum]

Bluetooth supply.

When I use external 5V supply everything works fine
When I use Vems ECU 5V (pin 28) it messes up the data on Vemsdisplay.

Could this be that the serial ground wire is used together with the 5V Vems ECU ??
When using the Vems ECU 5V you  use the serial pin5 as negative return for both serial data and 5V supply ground.
Or is the Vems 5V ECU supply not stable enough ??

It seems that it has something to do with the 5V power supply

[perboddum]

By the way use Vemsdisplay 2014-03-06.
Newer versions does not work properly (litre/km does not work)

Per

[mattias]

In my case, that doesn't really explain why it works on one phone and not another.

[perboddum]

Hi mattias

Vems Firmware=1.2.27
Today I tested this using Vemsdisplay 2014-03-06 and VemsBT....

Galaxy note 3
-----------------------
With ext. power everything works fine
With Vems 5V pin 28 power several of the values is fluctating up and down

Galaxy S3
-----------------------
With ext. power everything works fine
With Vems 5V pin 28 power the phone cannot connect

Per

[perboddum]

Hi

An update with the new VemsDisplay installed.

Vems Firmware=1.2.27
Today I tested the new Vemsdisplay 3.4 using VemsBT....

Galaxy note3 with VemsBT
--------------------------------
With ext. power everything works fine
With Vems 5V pin 28 power Phone can connect, but several of the values is fluctating up and down,EGO + others

Galaxy S3 with VemsBT
---------------------------
With ext. power everything works fine
With Vems 5V pin 28 power several of the values is fluctating up and down,EGO + others


Galaxy note3 and Galaxy S3 with SocketBT supplied with +5V by Vems pin 28
------------------------------------------------------------------------------------------
Both phones connects and displays correct data.
I got the SocketBT to work by enabling the "sniffer mode" option in the SocketBT setup software.
The "sniffer mode" scans BT status in between ordinary BT communication in order to determine things like connection state. Enabling this reduces the serial bandwidth a little.

Per

[NOTORIOUS VR]

News update

When using the SocketBT with Vemsdisplay several values in Vems ECU gets changed and flashed over time.
This makes the engine difficult to start and runs bad, until I connect my laptop via COM1 and download my latest config again.

That is scary... did you save the corrupted .cfg by chance?

[VEMS]

Hello Per,

This problem is not related to VemsDisplay in any way nor is it related to the Vems-BT; It works perfect when powered from external supply.

We have seen occasions where the total current requirement of the Vems-BT (and other items) is overdrawing the current capacity of the onboard (100mA max) +5V supply, are you feeding any other sensors or similar from pin#28 ?

Best regards, Dave

[lost]

Does onboard vems max232 chip is 3.3 TTL (rxd/txd) Level or its 5v?

Thats TTL level for communication, not powersupply for max232 chip

[perboddum]

Hi

I am quite sure that Vems board is 5V level (It has a Max232 chip)

[Sprocket]

We have seen occasions where the total current requirement of the Vems-BT (and other items) is overdrawing the current capacity of the onboard (100mA max) +5V supply, are you feeding any other sensors or similar from pin#28 ?

Best regards, Dave

This is interesting!

I am having problems with powering the Vems bluetooth adapter from the Rs232 Dsub9 socket on my brand new box. If you power up with the bluetooth adapter connected, the adapter stays dead until you unplug it, and then plug it back in. It works perfectly funt until you cycle the power and again the adapter remains dead until you unplug and re plug.

I could use an external power supply, but then what is the point of the 5v on pin 9 in the first place and then do i run into the problem quoted above using EC36/28 5v supply along with my other sensors

I'm about to create a report for it......

[Kamuto]

I'm always using lcd +5v supply, never had any problems with that