01-23-2023, 04:44 PM
(01-23-2023, 04:09 PM)Tim Curtis Wrote:(01-23-2023, 03:54 PM)Mark Dirac Wrote:(01-22-2023, 10:56 PM)Tim Curtis Wrote: Thats very odd. The symptoms suggest a network or possibly a uSD card issue.Thanks Tim.
You could try a 20 sec ping test from PC to USBridge (or vis versa) to see what the ping stats look like.
I'll not have a chance to run & copy pings today.
- I've created a new SD card ('cos the original one was crappy) - a brand new SanDisk Ultra. Problem is worse if anything.
- The problem only happens with Chrome for Windows. It doesn't happen on Chrome for Android!
The result below suggests the issue is isolated to the Windows PC.
Code:"The problem only happens with Chrome for Windows. It doesn't happen on Chrome for Android!"
You might want to check if any Chrome extensions are interfering with Browser throughput.
Good idea, but not extensions - I only have three extensions:
1. AdGuard AdBlocker, which was always disabled for moOde's URL, and is now disabled for the whole PC.
2. Google Translate, which I have disabled.
3. Chrome Remote Desktop, which I have also disabled.
Yes, Windows PC, or perhaps the way it's networked. (It worked with 7.4.1 release of moOde.) Windows and Android connects over wifi to eero router. Then ethernet to USBridge. eero router connected via ethernet to ISP's ADSL router.
Pings from Windows to USBridge:
Code:
C:\Users\markj>ping -n 20 moode.local
Pinging moode.local [192.168.5.51] with 32 bytes of data:
Reply from 192.168.5.51: bytes=32 time=2ms TTL=64
Reply from 192.168.5.51: bytes=32 time=2ms TTL=64
Reply from 192.168.5.51: bytes=32 time=2ms TTL=64
Reply from 192.168.5.51: bytes=32 time=2ms TTL=64
Reply from 192.168.5.51: bytes=32 time=3ms TTL=64
Reply from 192.168.5.51: bytes=32 time=2ms TTL=64
Reply from 192.168.5.51: bytes=32 time=12ms TTL=64
Reply from 192.168.5.51: bytes=32 time=2ms TTL=64
Reply from 192.168.5.51: bytes=32 time=3ms TTL=64
Reply from 192.168.5.51: bytes=32 time=10ms TTL=64
Reply from 192.168.5.51: bytes=32 time=3ms TTL=64
Reply from 192.168.5.51: bytes=32 time=2ms TTL=64
Reply from 192.168.5.51: bytes=32 time=2ms TTL=64
Reply from 192.168.5.51: bytes=32 time=20ms TTL=64
Reply from 192.168.5.51: bytes=32 time=7ms TTL=64
Reply from 192.168.5.51: bytes=32 time=4ms TTL=64
Reply from 192.168.5.51: bytes=32 time=3ms TTL=64
Reply from 192.168.5.51: bytes=32 time=2ms TTL=64
Reply from 192.168.5.51: bytes=32 time=3ms TTL=64
Reply from 192.168.5.51: bytes=32 time=3ms TTL=64
Ping statistics for 192.168.5.51:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 20ms, Average = 4ms