I have a very new Openspot 2 I am helping a local ham with and am very familiar with the Openspots. I own 6 OP1's and 1 other OP2 that is working perfectly. I have went down the checklist of normal things to check like Chanell's 1,6,11 or WPA and not WEP. 2.4G and not 5G, good SSID etc. etc.

This OS will just randomly drop a reflector connection, be it FCS or YSF. What is funny is that when first plugging the unit in it is much worse, cycling constantly, but after it warms up it gets more stable and will only drop a connection a few times an hour, depending upon traffic. The WI-FI receive signal strength is very constant at around -44. Below is a snippet of the log I retrieved during a failure. Any Mmore Ideas I can pursue?

23:29:19 fcs: pong received
23:29:20 net: enet link down
23:29:21 fcs: ping send error
23:29:21 fcs: init reconnect
23:29:21 spk: starting voice announcement
23:29:21 spk: playing locally: OSDC
23:29:21 spk: loading code pair OS
23:29:21 nvmm-csd: looking up callsign *****43BE5/0
23:29:21 nvmm-csd: ignoring special callsign *****43BE5/0
23:29:21 net: enet link down
23:29:21 net: reconnecting to previous ap
23:29:23 fcs: uninitialized
23:29:23 spk: loading code pair DC
23:29:23 wiresxtracker: sending disconnect
23:29:23 net: enet link up, ap mode: 0, ip lease still valid: 1, last associated match: ssid: 1 bssid: 0
23:29:23 net: no need for stack reinit
23:29:23 fcs: initializing
23:29:23 fcs: waiting for first pong
23:29:23 fcs: connected
23:29:23 fcs: ping sent
23:29:23 fcs: pong received
23:29:24 spk: sending terminator
23:29:24 nvmm-csd: looking up callsign *****43BE5/0
23:29:24 nvmm-csd: ignoring special callsign *****43BE5/0
23:29:24 spk: starting voice announcement
23:29:24 c4fmcalltracker: got header
23:29:24 c4fmpacket: header
23:29:24 dst: ********** src: FCS/INFO
23:29:24 dl: ul:
23:29:24 c4fmcalltracker: voice call started, dst: ********** dgid: 0 src: FCS/INFO id: 8242028c7234f2ea
23:29:24 nvmm-csd: looking up callsign **********
23:29:24 nvmm-csd: ignoring special callsign **********
23:29:24 nvmm-csd: looking up callsign FCS/INFO
23:29:24 nvmm-csd: callsign FCS/INFO not found
23:29:24 fcs: call started
23:29:24 fcs: invalid seqnum received, got 4 expected 3 (ft: 6), missing 1 packets
23:29:24 c4fmcalltracker: got terminator
23:29:24 c4fmpacket: header
23:29:24 dst: ********** src: FCS/INFO
23:29:24 dl: ul:
23:29:24 c4fmcalltracker: call ended, dur 0.1s ber 1.9% loss 7.7%