Such data connections could easily be relegated to a wireless connection. You have to remember that these are going to be delivering a lot of power. Putting a data connection in the same bundle would be like wrapping your HDMI cable around your washer and dryer. Not the wisest thing to do.
"Say you're charging your car and someone next to you is too. How do you make sure your charger doesn't start talking to that car and vice-versa?"
say your wifi laptop is next to someones wifi laptop, how do you make sure your router doesnt start talking to that laptop and vice versa? the point is, that problem has been solved a long time ago. protocols
Andres: My laptop doesn't get confused with another because I am typing on mine, not the other.
But people don't want to have to type stuff on their car each time they plug it in. Merely connecting the cable has to do the work.
Really, you're making a huge mistake here, drawing parallels that aren't parallel.
The problem is you need to be able to associate a given wireless device with the physical device that is plugged in. WiFi doesn't solve this or encounter this.
The only way to do this would be to have the device somehow communicate over the wire an identifier and then the charger could match the identifier over the wire with the identifier over the air and know they are the same device. Well, if you can communicate info over the wire, why bother with the wireless?
Why wouldn't it work just like a remote key dongle you use to unlock your car? Each car has a unique, changing key that matches the charger. Say you plug your key into the charger for a moment, it grabs the code, and BAM! instant, private communication.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
It would be better if there was a 7 point or more:
3 for power and ground, and 4 for a USB-like connection to tell you things like car status, power, etc.
Such data connections could easily be relegated to a wireless connection. You have to remember that these are going to be delivering a lot of power. Putting a data connection in the same bundle would be like wrapping your HDMI cable around your washer and dryer. Not the wisest thing to do.
Oh wow I just had a senile moment.
Why use wireless when a wire will do?
Say you're charging your car and someone next to you is too. How do you make sure your charger doesn't start talking to that car and vice-versa?
I'm sure the cable has some kind of data on it.
>Putting a data connection in the same bundle would be like wrapping your HDMI cable around your washer and dryer. Not the wisest thing to do.
A shielded twisted differential pair would probably be fine in this cable.
"Say you're charging your car and someone next to you is too. How do you make sure your charger doesn't start talking to that car and vice-versa?"
say your wifi laptop is next to someones wifi laptop, how do you make sure your router doesnt start talking to that laptop and vice versa?
the point is, that problem has been solved a long time ago. protocols
Andres:
My laptop doesn't get confused with another because I am typing on mine, not the other.
But people don't want to have to type stuff on their car each time they plug it in. Merely connecting the cable has to do the work.
Really, you're making a huge mistake here, drawing parallels that aren't parallel.
The problem is you need to be able to associate a given wireless device with the physical device that is plugged in. WiFi doesn't solve this or encounter this.
The only way to do this would be to have the device somehow communicate over the wire an identifier and then the charger could match the identifier over the wire with the identifier over the air and know they are the same device. Well, if you can communicate info over the wire, why bother with the wireless?
Why wouldn't it work just like a remote key dongle you use to unlock your car? Each car has a unique, changing key that matches the charger. Say you plug your key into the charger for a moment, it grabs the code, and BAM! instant, private communication.