G oog le BadWeB | Login/out | Topics | Search | Custodians | Register | Edit Profile


Buell Forum » XBoard » Archive through November 28, 2011 » No connection using bluetooth on Tunerpro RT? « Previous Next »

Author Message
Top of pagePrevious messageNext messageBottom of page Link to this message

Stuuk
Posted on Monday, October 31, 2011 - 11:22 am:   Edit Post Delete Post View Post/Check IP Print Post    Move Post (Custodian/Admin Only) Ban Poster IP (Custodian/Admin only)

Hi All

Back with a Buell again
Just got a 2005 XB12r Firebolt

Sold my 1125r last year and had my 1st firebolt 3 or 4 years ago.

Managed to make a ttl to bluetooth adapter for the buell primarily so I can do some wireless data logging using Tunerpro RT.

The adapter plugs into the buell's diagnostics socket and connects wirelessly to the bluetooth dongle on my laptop.

The laptop replicates this as com8.
The setup works great with ecmspy and ecm read but I cant get Tunerpro RT to connect.

I'm using the correct definition and buellplugin and Tunerpro RT recognises the hardware as BUEIB310 but wont connect and continually says DA not connected.

I understand some people have overcome connection problems by tweeking the payload size, body size and payload offset in the Tunerpro ADX editor.
Currently mine are set to 103, 103 and 0 respectively.

Is this worth trying and what numbers should I try?

Thanks

Stu
Top of pagePrevious messageNext messageBottom of page Link to this message

Xoptimizedrsx
Posted on Tuesday, November 01, 2011 - 08:53 pm:   Edit Post Delete Post View Post/Check IP Print Post    Move Post (Custodian/Admin Only) Ban Poster IP (Custodian/Admin only)

which adx?
mine or gunters?

also it will only connect if you go to tools then select release emulation.

the program is failsafe. as in it will only connect to one side at a time.

adx is one side
and
xdf is another side..

I use bluetooth on mine and have for a few years. works fine...
Top of pagePrevious messageNext messageBottom of page Link to this message

Stuuk
Posted on Sunday, November 06, 2011 - 11:35 am:   Edit Post Delete Post View Post/Check IP Print Post    Move Post (Custodian/Admin Only) Ban Poster IP (Custodian/Admin only)

This adx
DDFI_2_2003-2007.204162750

I'll try the tools tip but it connects straight away with a cable
Top of pagePrevious messageNext messageBottom of page Link to this message

Xoptimizedrsx
Posted on Monday, November 07, 2011 - 10:19 pm:   Edit Post Delete Post View Post/Check IP Print Post    Move Post (Custodian/Admin Only) Ban Poster IP (Custodian/Admin only)

did you go back in and get it to reconfigure to com 8 on tunerpro? Also was ecmspy closed if not it was taking the port and com ports only run on one program at a time.

mine work so I know it will do it. It's probably a setting somewhere.
Top of pagePrevious messageNext messageBottom of page Link to this message

Stuuk
Posted on Wednesday, November 09, 2011 - 06:38 am:   Edit Post Delete Post View Post/Check IP Print Post    Move Post (Custodian/Admin Only) Ban Poster IP (Custodian/Admin only)

Yeah I checked all that

It must be reading something as it detects the hardware as BUEID310

But DA still remains not connected

I'm using the toshiba BT stack on my laptop
Maybe this has something to do with it but like I said Ecmspy is connecting no problem via bluetooth

ps have you datalogged via bluetooth?
is the connection reliable enough?
Top of pagePrevious messageNext messageBottom of page Link to this message

Stuuk
Posted on Wednesday, November 09, 2011 - 08:40 pm:   Edit Post Delete Post View Post/Check IP Print Post    Move Post (Custodian/Admin Only) Ban Poster IP (Custodian/Admin only)

Ok got it working sort of.

Uninstalled toshiba bt stack and just used the microsoft stack.

However if TunerPro RT launches with the ignition on i.e. the ECM/BT adapter turned on once the ecm is detected as BUEID310 the DA wont connect and it looks as though the com port (now com 11) isnt available.

But if I do another detect hardware and turn the ignition off and wait for it to time out so it says hardware not detected then I turn ignition on again the da connects and I can see live data and datalog even though it says hardware not detected.

Its as though the hardware detection is opening the com port but keeping it open so the port isnt available to the rest of the program.

Its not making any sense to me but this is how its working

Anyway as long as it's capturing data it'll do...

Cheers

Stu
« Previous Next »

Add Your Message Here
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image

Username: Posting Information:
This is a public posting area. Enter your username and password if you have an account. Otherwise, enter your full name as your username and leave the password blank. Your e-mail address is optional.
Password:
E-mail:
Options: Post as "Anonymous" (Valid reason required. Abusers will be exposed. If unsure, ask.)
Enable HTML code in message
Automatically activate URLs in message
Action:

Topics | Last Day | Tree View | Search | User List | Help/Instructions | Rules | Program Credits Administration