Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

time division multiplexing

Status
Not open for further replies.

Tamas888

Junior Member level 3
Joined
Jun 28, 2010
Messages
25
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,445
hello
I need help.
How can I calculate TDMA out?
I mean I have a network with star topology and I also have fixed data rates ( for example 3 pieces of 2400bps channels and one 1760bps and so on..)
I want to divide the channels among the nodes, but I do not know how I can do it.
I want to simulate this network so the frequency band can be anything. For example I would use 915 Mhz ISM frequency and FSK modulation or another modulation. I do not know there is a difference between speeds of these modulation technologies.

Well, can somebody help me in this problem?

Thanks,

Tamas
 

Nobody else can help with this without full and accurate information on the
data each node must transmit and the total amount of time that takes(worst case).

By compiling the data you need to get help - you will have done the job yourself.

TDM is exactly what it sounds like.

Ontime and offtime per node.
The complications arise from having accurate data and the ability to know
when and how to turn each node on and off. There is also the issue of quiet time.

Don't overthink your problem. Just add up the number of bits you need
to send and receive per node (including overheads) calculate the time to send/recieve the data.

The idea is to maximise throughput - if node A is calculating - how much time can node B be given to transmit whatever it needs to send while A is working to enable
node A to have a send slot when it is ready without having to wait too long ... and so on.

Alternatively you could just chop up the time in even chunks and "round robbin" the nodes by making enough time available per node to do something useful.

The approaches you take depend on exactly what you are trying to achieve.

Hidden issues might be:
Work out how long it takes to switch nodes. Allow some quiet time for tolerances.
Multiply by the number of nodes.

Beware of multi-tasking nodes - can their OS cause random delays.

Add in any time you may need for transmission errors/re-transmits etc if you need to as a tolerance.

Its just a case of working out how long each task takes for your particular system
to ensure each node gets enough time to do its job within a given timeslot.

As I said elsewhere - you may find excel useful for doing this.

jack
 

    Tamas888

    Points: 2
    Helpful Answer Positive Rating
Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top