Leonardo Pappagallo wrote:
> Hi Jan,
> 
> I have rtnet 0.8.3 with RTAI 3.1.
> I use a isolated rtnet network with a master and a slave.
> 
> My NIC drivers are:
> 1 Pc :rt_8139too
> 2 Pc :rt_eepro100
> 
> My tdma.conf is:
> 
> #
> # Examplary TDMA configuration file
> #
> 
> # Primary master
> 
> master:
> ip 192.0.0.229
> cycle 1000
> slot 2 50
> slot 0 350 1/2
> 
> # Slave A
> slave:
> ip 192.0.0.244
> slot 2 100
> slot 0 350 2/2

Depending on the overall system load of your nodes, 1000 us cycle period
can be too stressing in the worst-case scenario. This is no generic
rule, it highly depends on the processing power of your boxes and the
other real-time load of your systems. Every tried to evaluate this?

Also note that the offset of slot 2 between master and slave can be too
short for low-end and mid-range systems, causing troubles at least on
hub-based networks. Do you know the scheduling jitter of your hardware
under non-realtime load (latency test of RTAI)?

BTW, you don't need that offset for the master slot 2. It can be 0
because the first "slot" is the synchronisation frame issued by the
master node, and all slots of the same node with identical offset will
be transmitted one after the other.

> 
> **********************************************************************************************************************************************************
> 
> rtnet.conf:
> 
> #!/bin/sh
> #
> # This file is usually located in <PREFIX>/etc/rtnet.conf
> # Please adapt it to your system.
> # This configuration file is used with the rtnet script.
> #
> 
> # RTnet installation path
> prefix="/usr/local/rtnet"
> exec_prefix="${prefix}"
> RTNET_MOD="${exec_prefix}/modules"
> RTIFCONFIG="${exec_prefix}/sbin/rtifconfig"
> RTCFG="${exec_prefix}/sbin/rtcfg"
> TDMACFG="${exec_prefix}/sbin/tdmacfg"
> 
> # Module suffix: ".o" for 2.4 kernels, ".ko" for later versions
> MODULE_EXT=".ko"
> 
> 
> 
> # RT-NIC driver
> RT_DRIVER="rt_8139too"
> RT_DRIVER_OPTIONS="cards=1"
> 
> # IP address and netmask of this station
> #   The TDMA_CONFIG file overrides these parameters for masters and backup
> #   masters. Leave blank if you do not use IP addresses or if this station
> is
> #   intended to retrieve its IP from the master based on its MAC address.
> IPADDR="192.0.0.229"
> NETMASK="255.255.255.0"
> 
> # Start realtime loopback device ("yes" or "no")
> RT_LOOPBACK="yes"
> 
> # Start capturing interface ("yes" or "no")
> RTCAP="yes"
> 
> 
> 
> # Common RTcfg stage 2 config data (master mode only)
> #   The TDMA_CONFIG file overrides this parameter.
> STAGE_2_SRC=""
> 
> # Stage 2 config data destination file (slave mode only)
> STAGE_2_DST=""
> 
> # Command to be executed after stage 2 phase (slave mode only)
> STAGE_2_CMDS=""
> 
> 
> 
> # TDMA mode of the station ("master" or "slave")
> #   Start backup masters in slave mode, it will then be switched to master
> #   mode automatically during startup.
> TDMA_MODE="master"
> 
> 
> # Master parameters
> 
> # Simple setup: List of TDMA slaves
> #TDMA_SLAVES="192.0.0.205"
> 
> # Simple setup: Cycle time in microsecond
> #TDMA_CYCLE="5000"
> 
> # Simple setup: Offset in microsecond between TDMA slots
> #TDMA_OFFSET="200"
> 
> # Advanced setup: Config file containing all TDMA station parameters
> #   To use this mode, uncomment the following line and disable the
> #   three master parameters above (SLAVES, CYCLE, and OFFSET).
> TDMA_CONFIG="${prefix}/etc/tdma.conf"
> 
> ******************************************************************************************************************************************************
> 
> What do you think about?
> 
> Thanks,
> 
> Leonardo.
> 

Jan

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to