All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] position of multiple bluetooth dongles
Date: Mon, 14 Feb 2005 07:13:46 +0100	[thread overview]
Message-ID: <4210419A.6030400@gmx.ch> (raw)
In-Reply-To: <200502101825.15870.cijoml@volny.cz>

Hello Michael

thank you a lot for this information.
Another question regarding this topic:

Does it help/make any difference if the two dongles have a distance of 
~11cm? Does this lead to equivalent/less interferences?
I have no idea about how radios send out their signals. I could imagine 
that if they spread their signal and there's another dongle just above the 
sending one that sends out a signal too, the interference is much worse 
than if they have a little distance, because the point of the problem is 
not right at the source.

Will rfcomm ensure the correctness of received data? something like a 
checksum and automatic retransmission of data if a brocken packet is 
recognized?

regards
Marco Trudel


Michal Semler wrote:
> BT 1.1 dongles may interference...
> BT 1.2 only when comunication with 1.1 devices - 1.2 devices can never 
> interference
> 
> Michal
> 
> Dne čt 10. února 2005 18:13 Marco Trudel napsal(a):
> 
>>Hello everybody
>>
>>Maybe someone knows this:
>>If two bluetooth dongles are used (a class1 and a class2), could it lead to
>>signal interfereces/problems if they're just above each other and both have
>>to send a lot of data at the same time?
>>
>>With "right above each other", I mean this:
>>http://www1.ch2.conrad.com/m/7000_7999/7100/7160/7162/716282_LB_00_FB.EPS.j
>>pg (dongle cases are removed).
>>
>>
>>kind regards
>>Marco
>>
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>_______________________________________________
>>Bluez-users mailing list
>>Bluez-users@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/bluez-users
> 
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2005-02-14  6:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 17:13 [Bluez-users] position of multiple bluetooth dongles Marco Trudel
2005-02-10 17:22 ` GUILLON Gabriel
2005-02-10 17:38   ` Marcel Holtmann
2005-02-10 17:25 ` Michal Semler
2005-02-10 17:41   ` Marcel Holtmann
2005-02-14  6:18     ` Marco Trudel
2005-02-14 19:24       ` Marcel Holtmann
2005-02-14  6:13   ` Marco Trudel [this message]
2005-02-14  9:02     ` Michal Semler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4210419A.6030400@gmx.ch \
    --to=mtrudel@gmx.ch \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.