13 Nov 2006 12:29
Re: IrDA speed
Hello, I've been very busy last few days, so I didn't manage to test the things you wrote before. Her goes. Alan J. McFarlane wrote: > > Has all the testing been done with one machine alone as the IrDA Primary > (i.e. the machine that did the IrDA discovery and started the > connection)? That's what the traces you've included appear to show. > That could be the cause of the asymmetric behaviour that you're seeing. > Hopefully this wouldn't be too hard for you to verify. I've additionally tested both cases: Where each machine takes primary role once, and the other is the only one as secondary. What happens is next: 1) When MCS7780 is acting as primary (sends SNRM) and SMSC-IIRC2 acts as secondary (responds with UA), transferring file from primary to secondary is very,very slow (few kBs). Here primary acts as sender and sends the data in cmd packets for secondary to receive. Transfering file from secondary to the primary is approx. ten times faster (about ~40 - 70 kBs). Here primary is receiving data in rsp packets from secondary. 2) When SMSC-IIR2 is acting primary (sends SNRM) and MCS7780 is acting as secondary (responds with UA), transferring files from primary to secondary is very,very fast (~330kBs)! Here primary is acting as sender and sends the data to the secondary in cmd packets for secondary to receive. Transferring file from secondary to the primary is as slow as in case 1), where MCS7780 as primary sends the data to the SMSC-IIRC2 as(Continue reading)
800 times
> bigger in fact. What's the Maximum Turnaround Time value in effect?
In prior tests max_turn_time was set to 500ms on both stations. Now I've
changed irlap.c to accept user defined max_turn_time. Ethereal dump
shows max_turn_time that station supports ranges from 500ms - 100ms.
Changing this on MCS7780 machine didn't change a bit. While modifying
this on SMSC-IIR2 machine it somewhat increased transmission speed from
few KBs to steady ~30 kBs. I've also put the irdadump packets from
ethereal to the site:
RSS Feed