Hi all, just curious how the 4.7 firmware is working on any ptp 550 links?
We’ve been running it on a link since 4.7 was released and everything has been fine.
3 Likes
We only have one PTP 550 remaining in the field (the inability to tweak one radio pair, without tearing down the whole link, is a fatal flaw) but for us 4.7 went on to the PTP550 fine, and has been working fine since. 
2 Likes
Hi, yes, it’s working excellent!
2 Likes
Thank you all, appreciate it.
1 Like
Maybe another way to phrase the question for the PTP 550 folks, are you seeing any noted improvements of radio performance with the new 4.7 Firmware? If so, what are you seeing? Thanks all
There were some scheduler improvements in 4.7 made specifically for the e3k AC radios that resulted in slightly higher throughput and lower latency and jitter during periods of high utilization. While the PTP550 is AC-based, I’m not sure if these improvements made it over to that platform, or whether they’re even applicable for a TDD-PtP link.
2 Likes
Now, that is a great answer!!! Thank you for that! Now I would be curious about specific PTP550 results. I guess since we have not seen any instances of the new firmware breaking any links or damaging any links then the best thing for me to do would be to go ahead and load the firmware and run my own evaluation. I will do that later toady and update after a couple days, for anyone who may have any interest 
I don’t know if this will be helpful info or not. I didn’t do any ‘before’ tests on 4.6.2 just before we upgraded about 3 weeks ago, but here are some ‘after’ tests done just now on 4.7 firmware. This link is a short 1.4 km link, signals about -52, in 80MHz mode.
Latency while carrying about 240 Mbit of client data right now (2.52ms average)
PING 10.201.3.3 (10.201.3.3) 32(60) bytes of data.
40 bytes from 10.201.3.3: icmp_req=1 ttl=64 time=2.18 ms
40 bytes from 10.201.3.3: icmp_req=2 ttl=64 time=1.82 ms
40 bytes from 10.201.3.3: icmp_req=3 ttl=64 time=3.23 ms
40 bytes from 10.201.3.3: icmp_req=4 ttl=64 time=2.13 ms
40 bytes from 10.201.3.3: icmp_req=5 ttl=64 time=2.62 ms
40 bytes from 10.201.3.3: icmp_req=6 ttl=64 time=2.41 ms
40 bytes from 10.201.3.3: icmp_req=7 ttl=64 time=3.38 ms
40 bytes from 10.201.3.3: icmp_req=8 ttl=64 time=1.38 ms
40 bytes from 10.201.3.3: icmp_req=9 ttl=64 time=3.14 ms
40 bytes from 10.201.3.3: icmp_req=10 ttl=64 time=2.91 ms
— 10.201.3.3 ping statistics —
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 1.382/2.524/3.387/0.624 ms
The baseline client data on this link is about 240 Mbit, and the Wireless Link test shows about 500 Mbit in either direction.
We have had no issues for 22 days – it’s stable and working fine for our needs.
3 Likes
Is that link in TDD-PtP or ePTP mode?
Sorry, I should have said. This link is ePTP mode, using only one of the radios.