Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
Need the latest SmartSDR or 4O3A Genius Product Software?
SmartSDR v4.1.5 | SmartSDR v4.1.5 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes
The latest 4O3A Genius Product Software and Firmware
SmartSDR v4.1.5 | SmartSDR v4.1.5 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes
The latest 4O3A Genius Product Software and Firmware
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Fragmentation with SmartSDR 2.3.9 and not with Smart SDR iOS? Coincidence?
Kari Gustafsson SM0HRP
Member ✭✭
I have with Goran SM6PPS tested remote connection over different access lines on the client side (500 km away) while maintaining 4G LTE on server/radio side (only option). Here are our findings. With fiber (100 Mbit) and 4G on client side we obtain no waterfall display due to as we understand fragmented UDP packages. The latency when pinging from client to radio side is low (20 ms).
However, when trying with Smart SDR iOS on the client side with 4G LTE on the radio site BUT over another 4G router (so both 4G routers are on the same cellular cell) we get the waterfall and everyhting works as expetected. Of course latency increases to 200 ms over this large packet "loop".
How come? This seem to point to smart SDR Windows that introduces this or? With earlier version (2.3.7) in may we did not notice any of this problem.
I know changes were made in the fragmentation issue in latest release.
Have anyone else noticed the same phenomenon?
However, when trying with Smart SDR iOS on the client side with 4G LTE on the radio site BUT over another 4G router (so both 4G routers are on the same cellular cell) we get the waterfall and everyhting works as expetected. Of course latency increases to 200 ms over this large packet "loop".
How come? This seem to point to smart SDR Windows that introduces this or? With earlier version (2.3.7) in may we did not notice any of this problem.
I know changes were made in the fragmentation issue in latest release.
Have anyone else noticed the same phenomenon?
0
Answers
-
When I had fragmentation issues it turned out to be a hardware setting in my NIC card.
I did post it here in the community the settings I changed. It was in my pfSense router so if you search you can find it.
Mike
0 -
Michael,
Could you explain more fully (for example the settings or pictures) and provide links.
Tnx, Jim0 -
Leave a Comment
Categories
- All Categories
- 386 Community Topics
- 2.2K New Ideas
- 653 The Flea Market
- 8.4K Software
- 155 SmartSDR+
- 6.5K SmartSDR for Windows
- 189 SmartSDR for Maestro and M models
- 437 SmartSDR for Mac
- 274 SmartSDR for iOS
- 264 SmartSDR CAT
- 202 DAX
- 384 SmartSDR API
- 9.4K Radios and Accessories
- 50 Aurora
- 291 FLEX-8000 Signature Series
- 7.2K FLEX-6000 Signature Series
- 967 Maestro
- 58 FlexControl
- 866 FLEX Series (Legacy) Radios
- 938 Genius Products
- 468 Power Genius XL Amplifier
- 344 Tuner Genius XL
- 126 Antenna Genius
- 306 Shack Infrastructure
- 215 Networking
- 466 Remote Operation (SmartLink)
- 144 Contesting
- 806 Peripherals & Station Integration
- 143 Amateur Radio Interests
- 1K Third-Party Software
