This same bug should also apply to InsightHome and InsightFacility. I have documented this to Schneider and discussed it with them on the phone, but their call volumes are high and also migrating to a new phone system so getting a fix may take a while.
Setup: Mine is a Schneider CG (Conext Gateway) providing management GUI & Modbus network access to two grid tied XW-Pro's charging a big bank of batteries and AC coupled to a couple of SMA PV inverters.
IP network access from local management PC via LAN, implemented by configuring the CG in WiFi client mode. It maintains a continuous link to a 2.4GHz 802.11g generic router AP. Physical Ethernet jack on CG is always left disconnected.
CG / Setup / Network / Wi-Fi Access Point settings
Access Point | X | _ | (Indicator to the left = disabled)
SSID ConextGateway_xxxxxx
Server IP Address 192.168.100.1
.. / .. / Wi-Fi and Ethernet Settings
Ethernet connection
LAN DHCP | X | _ | (Indicator to the left = disabled)
IP Address 192.168.36.73
Subnet mask 255.255.255.0
Gateway
DNS Server 192.168.35.70
WiFi SSID Sunshine (Connected!)
WIFI DHCP | X | _ | (Indicator to the left = disabled)
IP Address 192.168.35.73
Subnet mask 255.255.255.0
Gateway 192.168.35.70
DNS Server 192.168.35.70
XW-Pro Power Shaving is enabled from 16:00 (start of grid premium rate) to 07:00 the following day.
Charging is blocked from 15:30 to 09:30.
A charge cycle is initiated every day by applying "Bulk" mode at 10:00 using a timer controlled Modbus write from a custom SBC application. Usually, both master/slave XX-Pros follow expected Bulk / Absorpstion cyles and fully charge the batteries every day.
Normally, LAN performance PC to CG is good, ping times 260 ms.
PROBLEM: At very random times, approximately 5 to 14 day intervals, the CG improperly ENABLES its Access Point mode! Our first indication is that network performance to the CG becomes very bad, ping times 800-1200ms, or totaly dropped. (Pings and network access to the colocated SMA WiFi clients remains fine.) My opinion is the CG internal WiFi processor was never designed to efficiently time share between both wireless client & AP modes being active.
AP active can be confirmed by doing a local WiFi scan from a PC and seeing the ConextGateway_xxxxxx SSID.
With some patience & effort to deal with the performance, it is often possible to log into the CG over the WiFi. Surprisingly, under Wi-Fi Access Point settings, the Access Point "switch" still indicates "disabled". The only "fix" we have is simply clicking the GUI menu "Apply" button (no need to make any config changes). Once done, the performance instantly recovers, and the SSID disappears from WiFi scan.
Note: Initiating a software reboot from the GUI menu (or even from the Modbus reboot register setting) does *NOT* fix the AP active behavior.
Also: This "acts" as if someone had pressed the "WiFi" button on the side of the CG. But our CG is inside a dry, secure outbuilding without others having access.
The big impact for us is that the custom SBC app is also using Modbus to continually adjust EPCMaximumCharge Power, so the batteries only charge from solar and send the excess to the grid. The WiFi performance hit totally disrupts that when the Bug is active. (Unfortunately no Modbus key register for AP mode disable.) The only thing the app can do is a WiFi scan for the CG AP and start flashing a warning to manually disable it.
I have seen others reporting the bug. Some even just use wired Ethernet seeing the AP getting enabled. Others just notice random WiFi performance issues. I figured it would be good to pursue that from one place on these forums.
Setup: Mine is a Schneider CG (Conext Gateway) providing management GUI & Modbus network access to two grid tied XW-Pro's charging a big bank of batteries and AC coupled to a couple of SMA PV inverters.
IP network access from local management PC via LAN, implemented by configuring the CG in WiFi client mode. It maintains a continuous link to a 2.4GHz 802.11g generic router AP. Physical Ethernet jack on CG is always left disconnected.
CG / Setup / Network / Wi-Fi Access Point settings
Access Point | X | _ | (Indicator to the left = disabled)
SSID ConextGateway_xxxxxx
Server IP Address 192.168.100.1
.. / .. / Wi-Fi and Ethernet Settings
Ethernet connection
LAN DHCP | X | _ | (Indicator to the left = disabled)
IP Address 192.168.36.73
Subnet mask 255.255.255.0
Gateway
DNS Server 192.168.35.70
WiFi SSID Sunshine (Connected!)
WIFI DHCP | X | _ | (Indicator to the left = disabled)
IP Address 192.168.35.73
Subnet mask 255.255.255.0
Gateway 192.168.35.70
DNS Server 192.168.35.70
XW-Pro Power Shaving is enabled from 16:00 (start of grid premium rate) to 07:00 the following day.
Charging is blocked from 15:30 to 09:30.
A charge cycle is initiated every day by applying "Bulk" mode at 10:00 using a timer controlled Modbus write from a custom SBC application. Usually, both master/slave XX-Pros follow expected Bulk / Absorpstion cyles and fully charge the batteries every day.
Normally, LAN performance PC to CG is good, ping times 260 ms.
PROBLEM: At very random times, approximately 5 to 14 day intervals, the CG improperly ENABLES its Access Point mode! Our first indication is that network performance to the CG becomes very bad, ping times 800-1200ms, or totaly dropped. (Pings and network access to the colocated SMA WiFi clients remains fine.) My opinion is the CG internal WiFi processor was never designed to efficiently time share between both wireless client & AP modes being active.
AP active can be confirmed by doing a local WiFi scan from a PC and seeing the ConextGateway_xxxxxx SSID.
With some patience & effort to deal with the performance, it is often possible to log into the CG over the WiFi. Surprisingly, under Wi-Fi Access Point settings, the Access Point "switch" still indicates "disabled". The only "fix" we have is simply clicking the GUI menu "Apply" button (no need to make any config changes). Once done, the performance instantly recovers, and the SSID disappears from WiFi scan.
Note: Initiating a software reboot from the GUI menu (or even from the Modbus reboot register setting) does *NOT* fix the AP active behavior.
Also: This "acts" as if someone had pressed the "WiFi" button on the side of the CG. But our CG is inside a dry, secure outbuilding without others having access.
The big impact for us is that the custom SBC app is also using Modbus to continually adjust EPCMaximumCharge Power, so the batteries only charge from solar and send the excess to the grid. The WiFi performance hit totally disrupts that when the Bug is active. (Unfortunately no Modbus key register for AP mode disable.) The only thing the app can do is a WiFi scan for the CG AP and start flashing a warning to manually disable it.
I have seen others reporting the bug. Some even just use wired Ethernet seeing the AP getting enabled. Others just notice random WiFi performance issues. I figured it would be good to pursue that from one place on these forums.