epmp 200 PtP 40M channel throughput?

I'm running a 40M channel in DFS on a 1.5 mile unobstructed path using epmp 200's in 5G. What performance should I be seeing?

I have clear spectrum, but according to the link speed test tool and flexible scheduling, even with a 60/60 RSSI and MCS15 I wasn't seeing over 86M/30M. I would think if these radios say they support 200M or a bit more, shouldn't I be seeing more on a clear unostrcutred path?

Would I gain anything by going to larger dishes and connectorized GPS sync radio? I'm trying to replace an AC link which seems to be puking when you put lots of traffic down it, especially when you try an 40M channel.


What Wireless mode is used TDD or ePTP ?

I would be really appreciate it if you could attach Monitor Wireless and Monitor Performance pages screenshots.

In the clear environment with 40M channel ePMP devices usually provides ~200 Mbps.

Thank you.

Will try to find this information, but I have to have two crews to do it again, one on the first tower and another on the second, which will take me some time.

Should I be using ePTP or TDD for this? Also, what should I be using for frame size? Anything else I should note?

@silverstr8p wrote:

Should I be using ePTP or TDD for this? Also, what should I be using for frame size? Anything else I should note?

If your goal is to have as low latency as possible over the link, and you aren't concerend with GPS sync, then use ePTP. If you need GPS sync, you can use TDD-PTP, and in some cases get slightly higher throughput over ePTP, at the cost of a little bit higher latency. When using TDD-PTP mode, for lowest latency, use flexible frames (this will negate any benefits from GPS sync however, so you're probably better off using ePTP). Use 2.5ms frames for lower latency at a cost of about 10% throughput. Use 5ms frames for slightly higher latency, with a bonus of about 10% throughput.

ALSO, what firmware revision are you using? If you're using ePTP, I'd strongly recommend that you use the 3.0RC27 beta, as we've seen some nice performance improvements using this build.


Okay, will try firmware update, I'm running 2.6.x. I read the release notes, do you know of any other 'gotcha's' with this release?

I don't care about GPS sync for this link, so I'll try the ePTP and see what I get.

Firmware 3.0RC27 is a beta release, but it's pretty mature at this point (RC builds are typically towards the end of the development cycle indicating a 'release canidate'), we're running it on a production PtMP sector and on a live ePTP link for some time now and have not run into any major issues.

I tried it and it seems like the firmware upgrade had a major impact. Before the speed test showed 80/30 or so, with the upgrade, the link speed test shows around 100/100, so huge improvement. I don't see any scheduling that you can set though, we typically used either 75/25 or flexible, does this new firmware have only flexible, or am I missing something?

ePTP mode is not GPS sync compatible and you cannot specify various frame options. The modeā€™s goal is to give the lowest latency and high throughput in a ptp link. You will need to use TDD-PTP if you want to use sync and set frame options.


I have an epmp 200 on each end, so I don't have a GPS sync option, but I want the bulk of my traffic (>75%) of my traffic to be download, so in this case, is there a way to dedicate that, or there a flexible scheduler that's built in, or is the link now just limited to 100M download no matter what?

ePTP uses a flexible schedular. Force 200 products have a gigabitĀ capable ethernet port. Maximum half-duplex throughput under ideal conditions and while using a 40MHz channel width should be close to 200mbps.

If you wish to use a fixed ratio, you'll need to use TDD-PTP mode.