JRA;64001 wrote: . ...... I don't want to volunteer him, but DJ has one and is a computer wiz...might talk to him to.
Mr.DJ;64063 wrote: "Wiz?" Ha!
Yea, I may pee all over it - Besides, my specialty is the mystical word of bits behind the PC connection to the internet.
Meat,
You know how busy my mornings can get, but if you haven't got it going by lunch I can try to help.
Does your pc (via bluetooth) connect to the laptimer?
The chipset in my laptop is very flaky with some devices, so I had to disable the driver in windows and use a third party (bluesolei).
***
For the Nerds: I did a bluetooth sniff and it showed l2cap requests didn't get response to the request packet (it had optional bits set). I'm not a network software engineer, so I dont know or care
***
The laptimer and other devices worked more consistently after install. I forwarded that to Starlane. You may want to shoot them an email and get their thoughts in case they have a better solution. Again, this is assuming you have a device negotiation/communication issue with PC and not a device configuration problem with software. Another thought is to disable any authentication between your laptimer and PC - get comm going first before you "lock it down." I'm sure we can get it to work or use my laptop to isolate the issue.
Now we get'n some where.Mr.DJ;64074 wrote: OK, Point taken, Ken
Does your pc "see" the laptimer ?
Nah man! I know that wasn't your intention nor how I took it. Just informing that I am available to members for things outside of getting our day started around lunch.JRA;64097 wrote: I'm with Ken.:notsure:
I wasn't trying to add to your work this weekend DJ, just saying you had one and maybe could offer some advice.
:dunno: I am assuming you are talking about rear tire traction, or maybe position of the sun during leap year in the Southern Hemisphere. But if you aren't then I have no clue of what you speak.Mr.DJ;64063 wrote: "Wiz?" Ha!
Yea, I may pee all over it - Besides, my specialty is the mystical word of bits behind the PC connection to the internet.
Meat,
You know how busy my mornings can get, but if you haven't got it going by lunch I can try to help.
Does your pc (via bluetooth) connect to the laptimer?
The chipset in my laptop is very flaky with some devices, so I had to disable the driver in windows and use a third party (bluesolei).
***
For the Nerds: I did a bluetooth sniff and it showed l2cap didn't get response to the request packet (it had optional bits set). I'm not a network software engineer, so I dont know or care
***
The laptimer and other devices worked more consistently after install. I forwarded that to Starlane. You may want to shoot them an email and get their thoughts in case they have a better solution. Again, this is assuming you have a device negotiation/communication issue with PC and not a device configuration problem with software. Another thought is to disable any authentication between your laptimer and PC - get comm going first before you "lock it down." I'm sure we can get it to work or use my laptop to isolate the issue.
JRA;64001 wrote: I don't want to volunteer him, but DJ has one and is a computer wiz...might talk to him to.
Well, it sure wasn't due to lack of effort or focus. You spent so much time in my pits working on it, using my starlane, using yours, using my laptop, yours, them a couple mroe hours after the track day was over...getting new updates, running 3 older versions....the amount of effort you put out was rediculous.Mr.DJ;65776 wrote: I FAILED..... must have cracked under the pressure oorguy: