Hi All
I’ve been experimenting with xapflash with windows iServer (iServer F that comes with xapflash). My setup was:
192.168.1.250 – web server storing xapflash swf, config.xml, xapconfig.xml (iserver ipaddr set to 192.168.1.100)
192.168.1.100 – pc running iServer F
192.168.1.50 – PLC with custom xap stack
Everything worked like a charm. I was able to start IE on 192.168.1.100, point to http://192.168.1.250/xapflash.swf and control 192.168.1.50
Yesterday I received livebox, flashed it and seems it works. At least I can see it’s heartbeats and queries with xfxviewer. So I made changes to xapconfig.xml on 192.168.1.250 setting iserver address to 192.168.1.41 (static address for livebox). With this configuration I can still use web browser to connect to192.168.1.100 and open http://192.168.1.250/xapflash.swf but now I am unable to control anything – PLC at 192.168.1.50 does not receive any bytes on it's listening socket, althought when I push UI button I can see proper xapBSC.cmd message fired (with xfxViewer). Strangely enough swf client receives xapBSC.info messages and reflect them in the UI. So there is a "one-way" communication - PLC is visible by the clients, but no client commands reach PLC
Also, one thing I noticed - when I run iServer in debug mode it show that is receives xapBSC.cmd messages and then it does something called "filter compare" (not sure what's the correct function name, but it's from filter.c file) and this compare always results in match=0. So looks like it simply does not know where to route the message. And when xapBSC.info comes from the PLC iServer does the same stuff but always ends up with match=1 and then routes message to appropriate client IP. Maybe I just need to supply PLC IP in it's heartbeats (I am setting the "port" value only)?
Any help highly appreciated
Thanks in advance
Dmitry