Andrea Forni wrote: > Andrea wrote: > >>> In second case I would understand if I can poll a node more than one time >>> in a cycle of TDMA. >>> >>> E.g. : >>> >>> # Primary master >>> master: >>> ip 10.0.0.3 >>> cycle 900 >>> slot 0 150 >>> slot 2 450 >>> slot 3 750 >>> >>> >>> # Slave A >>> slave: >>> ip 10.0.0.1 >>> slot 0 0 >>> slot 2 300 >>> slot 3 600 >>> >>> In this mode, slave send a message to master every 300us. I would understan >>> if this situation is feasible... I tried in the mode above (code in the old >>> mail), but it don't work... I read the documentation of RTmac and I see a >>> similar example, for this motif I ask you that.... > > > Jan wrote: > >> You mean it doesn't worked at the rate of 300 us, or it doesn't work at >> all? I.e. is this effect load-depended or could it rather be a generic >> communication problem (I had no closer look at your code yet)? What >> architecture/CPUs do you use for your nodes? > >> Jan > > > Hi Jan, > > I have a communication (slave send a message to master) only in the first > slot (slot 0) > and the next communication happens in a new cycle (in the slot 2 and 3 i > haven't a communication > like I'm not setting these in TDMA.conf).
I see. You either have to select all non-default slots explicitly at application level, or you have to form them to joint slots. The latter means that all joint slots share the same packet queue, otherwise, queues are separated and have to be addressed directly. The syntax for specifying joint slots in tdma.conf is: slot <id> <offset_in_us> <phasing>/<period> <size> <joint_slot_id> (note that all parameters need to be given in that order) E.g.: slot 0 0 1/1 1500 slot 2 300 1/1 1500 0 slot 3 600 1/1 1500 0 Jan
signature.asc
Description: OpenPGP digital signature
