Dear Jan,
I further test with CDMA config script, rtping -s 1500 and ping -s 1500. No
problem occurs.
Regards,
Chun Yeow
On 10/31/07, Yeoh Chun Yeow <[EMAIL PROTECTED]> wrote:
>
> Dear Jan,
>
> Here the result for the ping -s 65000 from At91 to the Slave. It seems
> alright.
>
> Regards,
> Chun Yeow
>
> [EMAIL PROTECTED]:/usr/rtnet] cat
> /proc/rtnet/rtcfg/rteth0/CLIENT_172.16.6.174
> state: 3 (READY)
> flags: 02
> stage 1 size: 66
> stage 2 filename: -
> stage 2 size: 0
> stage 2 offset: 0
> burstrate: 0
> mac address: 00:C0:8B:08:81:AB
> ip: 172.16.6.174
> [EMAIL PROTECTED]:/usr/rtnet] cat /proc/rtnet/rtcfg/rteth0/station_list
> 00:C0:8B:08:81:AB 02
> [EMAIL PROTECTED]:/usr/rtnet] ./sbin/rtifconfig
> rteth0 Medium: Ethernet Hardware address: 14:09:07:05:05:02
> IP address: 172.16.6.203 Broadcast address: 172.16.6.255
> UP BROADCAST RUNNING MTU: 1500
>
> rtlo Medium: Local Loopback
> IP address: 127.0.0.1
> UP LOOPBACK RUNNING MTU: 1500
>
> [EMAIL PROTECTED]:/usr/rtnet] ifconfig
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask: 255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:416 (416.0 B) TX bytes:416 (416.0 B)
>
> vnic0 Link encap:Ethernet HWaddr 14:09:07:05:05:02
> inet addr:172.16.6.203 Bcast: 172.16.6.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MTU:1496 Metric:1
> RX packets:861 errors:0 dropped:0 overruns:0 frame:0
> TX packets:861 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1219028 ( 1.1 MiB) TX bytes:1227470 (1.1 MiB)
>
> [EMAIL PROTECTED]:/usr/rtnet] ping -s 65000 172.16.6.174
> PING 172.16.6.174 (172.16.6.174): 65000 data bytes
> 65028 bytes from 172.16.6.174: icmp_seq=0 ttl=64 time=321.9 ms
> 65028 bytes from 172.16.6.174: icmp_seq=1 ttl=64 time=281.8 ms
> 65028 bytes from 172.16.6.174: icmp_seq=2 ttl=64 time=283.1 ms
> 65028 bytes from 172.16.6.174: icmp_seq=3 ttl=64 time=285.5 ms
> 65028 bytes from 172.16.6.174: icmp_seq=4 ttl=64 time=280.3 ms
> 65028 bytes from 172.16.6.174: icmp_seq=5 ttl=64 time=283.2 ms
> 65028 bytes from 172.16.6.174: icmp_seq=6 ttl=64 time=288.9 ms
> 65028 bytes from 172.16.6.174: icmp_seq=7 ttl=64 time=275.7 ms
> 65028 bytes from 172.16.6.174: icmp_seq=8 ttl=64 time=293.5 ms
> 65028 bytes from 172.16.6.174: icmp_seq=9 ttl=64 time=275.0 ms
>
> --- 172.16.6.174 ping statistics ---
> 10 packets transmitted, 10 packets received, 0% packet loss
> round-trip min/avg/max = 275.0/286.8/321.9 ms
>
>
>
> On 10/30/07, Jan Kiszka <[EMAIL PROTECTED]> wrote:
> > >
> > > Yeoh Chun Yeow wrote:
> > > > Dear Jan
> > > >
> > > > Can you explain the tdma configuration of "slot 1 0 1/1 1500 1"?
> > >
> > > First of all, this was early-morning nonsense, must rather read:
> > >
> > > slot 2 0 1/1 1500 0
> > >
> > > Translation: Create a TDMA slot, ID 2 (first arg), offset 0 us
> > > relative
> > > to each TDMA Sync (second arg), period 1/1, i.e. use every TDMA cycle
> > > (third arg), 1500 byte payload (fourth arg), and join this slot with
> > > the
> > > one of ID 0 (fifth arg). For more details, see README.rtmac (hmm, it's
> > > is failing to mention the fifth argument, too bad...).
> > >
> > > >
> > > > And how should I configure the cycle (previously in the rtnet.conf ,
> > > I set
> > > > the TDMA cycle to 2000 and TDMA offset to 500) and the slave?
> > >
> > > Please check the README first, it should explains this.
> > >
> > > >
> > > > Is it ok for me to use the default configuration in tdma config
> > > script?
> > >
> > > As a basis, yes.
> > >
> > > >
> > > > I have ensure that AT91 acts as the master and it is able to ping
> > > the slave
> > > > using rtping after the completion of TDMA setup. So is this enough?
> > >
> > > To be safe, apply the above configuration and run a test with larger
> > > ping frames (ping -s ...). Maybe the time for returning some
> > > transmission buffer from the hardware back to the OS is actually so
> > > short here that a TX queue is not needed. But my feeling is not yet
> > > that
> > > optimistic.
> > >
> > > Jan
> > >
> > >
> > >
> >
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users
