[Rick1-10]

Has anyone ever thought about using something like this with their Procede? (link below) It's basically a wireless serial port. The thought is you could send new maps and read data, while in the car. It would/could even open up PDA software development!... IDN just a thought.. I don't even have a Procede yet but soon.......

http://www.wcscnet.com/HdwBTRS232.htm

[RiXst3r]

link doesnt work for me

[normtrum]

link won't work for me either. gud idea though.

[OpenFlash]

I like. But luck with the link here either.

[ADHD]

YES i have researched and came up with a belkin for 200$..
I was about to buy it but found a sick laptop for 450 when i was there so my plans got altered!!
I instead modded the cable to run through to my glove box!! bought the serial/usb cable and im running!!! BUT my cable is shown I would like to find a cheaper solution to this!!

here is some links i found:
http://www.dpactech.com/wireless_pro...ial-bridge.asp
http://www.ipenabled.com/gc-wi232.html

[dolby]

The link worked for me this morning.


Basically it a RS232 to Bluetooth to RS232 converter for $129 (I think that was the price)

It requires 5-9v to operate, which is easy to make.

The big problem I see is the fact it is wireless. Having a transmitter that close to the ECU and PROcede could cause some RF problems. Bluetooth follows the inverse square law for RF transmission too.

I will probably connect a slightly longer weather resistant RS232 plug to the PROcede to hang outside if the ECU compartment if I find myself connecting the computer very often.

dolby

[Sim Simma]

So does interference with the ECU make this a no go? Has anyone tried or had any luck with this? Would be a great addition to the PROcede. I was able to find one for about $99. http://www.brainboxes.com/category/bluetooth.aspx

[Walked U]

Oh shit that looks like a really good idea.

Off the topic tho. I have a mda pro (smart phone) that i basicly put all my work stuff on and was going to put the procede maps and programing on to it. ( the phone has windows )

If there was a blue tooth to serial connector that would be awsome. This way i dont have to carry my laptop around with me and just load maps through my phone.

[e.n335]

I'm doing a litte project with similar hardware. Did a bunch of testing, it will work. Now I have to wait for the PROcede to do the final test and DIY. See Vishnu Support Forum

[ADHD]

Originally Posted by eugen.niederreiter

I'm doing a litte project with similar hardware. Did a bunch of testing, it will work. Now I have to wait for the PROcede to do the final test and DIY. See Vishnu Support Forum

I see yoru thread over there! why not just buy one of those and put it in the ecu box and use the bluetooh feauture on your computer!!

[e.n335]

Originally Posted by ADHD

I see yoru thread over there! why not just buy one of those and put it in the ecu box and use the bluetooh feauture on your computer!!

Connectivity stability issues. I don't know how

a) The PROcede reader will support a virtual bluetooth COM port emulation
b) Other bluetooth devices ( cell phones, PDA's, etc. ) will harm such a connection

For example, when you update the firmware of the PROcede and the connection would break, the PROcede could be damaged and you will have to send it back to Vishnu to fix the problem. My solution is like a physical cable. It only accepts requests from the second device and is a real point to point connection. Even if you use it next to somebody who has the same or a different bluetooth solution, the connectivity would be bullet-proof. No other reason.

Cheers
Eugen

[ADHD]

Originally Posted by eugen.niederreiter

Connectivity stability issues. I don't know how

a) The PROcede reader will support a virtual bluetooth COM port emulation
b) Other bluetooth devices ( cell phones, PDA's, etc. ) will harm such a connection

For example, when you update the firmware of the PROcede and the connection would break, the PROcede could be damaged and you will have to send it back to Vishnu to fix the problem. My solution is like a physical cable. It only accepts requests from the second device and is a real point to point connection. Even if you use it next to somebody who has the same or a different bluetooth solution, the connectivity would be bullet-proof. No other reason.

Cheers
Eugen

ahhhhh makes sense!

[choatie88]

Are you saying that the adapter doesn't just convert serial -> bluetooth -> serial if you have two? The bluetooth protocol has a number of safeguards to prevent interference of this nature - otherwise you'd be able to hear someone else's conversation as they drive past you while on the phone...

[tintivilus]

Originally Posted by eugen.niederreiter

Connectivity stability issues. I don't know how

a) The PROcede reader will support a virtual bluetooth COM port emulation
b) Other bluetooth devices ( cell phones, PDA's, etc. ) will harm such a connection

I understand your concern, but it's usually not that complicated. I've used a handful of Windows bluetooth stacks, and they've all mapped bluetooth SPP devices to Windows COM ports -- Bluetooth serial adapters behave the same as USB serial adapters. Since USB->RS232 adapters are already well tested, concern (a) should be a non-issue, at least for most users. (b) can be negated by just only connecting one bluetooth device at a time; if multiple simultaneous BT-SPP devices are supported, they get mapped to different virtual COM ports.

I'd just be concerned about link stability for firmware flashing, but is it possible to "brick" a PROcede during re-flash, or do they have redundant firmware? If they're brick-able, I'd just use the bluetooth for maps and datalogging and use a hard cable when doing firmware upgrades.

...just my $0.02... best of luck with your project

[e.n335]

Originally Posted by choatie88

Are you saying that the adapter doesn't just convert serial -> bluetooth -> serial if you have two? The bluetooth protocol has a number of safeguards to prevent interference of this nature - otherwise you'd be able to hear someone else's conversation as they drive past you while on the phone...

It's cabable to do more. It provides software AT commands, connecting multiple devices, different operating modes, huge serial setting capabilities, different protocols, etc. It had to be an industrial certified device ( automotive use ). I don't say it has to be. I say I would do it like this and so I do.

Cheers
Eugen

[e.n335]

Originally Posted by tintivilus

I understand your concern, but it's usually not that complicated. I've used a handful of Windows bluetooth stacks, and they've all mapped bluetooth SPP devices to Windows COM ports -- Bluetooth serial adapters behave the same as USB serial adapters. Since USB->RS232 adapters are already well tested, concern (a) should be a non-issue, at least for most users. (b) can be negated by just only connecting one bluetooth device at a time; if multiple simultaneous BT-SPP devices are supported, they get mapped to different virtual COM ports.

I'd just be concerned about link stability for firmware flashing, but is it possible to "brick" a PROcede during re-flash, or do they have redundant firmware? If they're brick-able, I'd just use the bluetooth for maps and datalogging and use a hard cable when doing firmware upgrades.

...just my $0.02... best of luck with your project

Thank you for feedback. Again, I can only repeat myself: All I want to do is emulating the cable. Rugged, point to point. Not transparent to software. Usable with a simple DIY. Windows user level knowledge ( sorry for this, don't take it wrong ).

When you didn't use it for one year and you'll power it on, it will work.

Of course, more "fancy" solutions will be possible

Cheers
Eugen

[e.n335]

Originally Posted by Walked U

Oh shit that looks like a really good idea.

Off the topic tho. I have a mda pro (smart phone) that i basicly put all my work stuff on and was going to put the procede maps and programing on to it. ( the phone has windows )

If there was a blue tooth to serial connector that would be awsome. This way i dont have to carry my laptop around with me and just load maps through my phone.

You'll need special PROcede Reader PDA software releases for Windows CE or Windows Mobile, ... did you check availability ?

Cheers
Eugen

[sflgator]

I have to tell you...as much as a wireless solution would be great for updating the PROcede s/w, doing it by connecting a USB-Serial cable from your your laptop to the PROcede is fairly easy. I just updated my PROcede s/w to v1.4, and it literally took less than 10 min...~8 min. to take off the covers and 30 sec. to upload the PROcede v1.4 map.

With that said, I think a wireless update solution might be something that Shiv could implement on the PROcede in the future...it would be a nifty high-tech feature.

[e.n335]

@sflgator: Fair enough

Until this happens, I'll use my solution in advance

Cheers
Eugen

[leftcoastman]

I'm investigating a bluetooth solution - not just for updating but for data logging.

[choatie88]

A bluetooth serial adapter (i.e. eugen's solution) should work for data logging just as well as a normal serial cable would...

[stevenraybo]

Originally Posted by Rick1-10

Has anyone ever thought about using something like this with their Procede? (link below) It's basically a wireless serial port. The thought is you could send new maps and read data, while in the car. It would/could even open up PDA software development!... IDN just a thought.. I don't even have a Procede yet but soon.......

http://www.wcscnet.com/HdwBTRS232.htm

It is good products,

maybe you also could try this one.
http://www.aliexpress.com/store/905335