Comet system forum

Visitor · 13-11-2008 06:19:11

It will start sending SOAP messages only after the SOAP parameters are inspected and saved via the telnet interface. None of the parameters are changed - just saved again. Needless to say, we can't use this in a production environment to monitor systems without a fix.

Has anyone else seen this problem? Is there a firmware upgrade?

From the web interface about page:

* Firmware version: 4-5-1.14
* Web version: 2.00

Ralph.

HonzaD · 13-11-2008 07:54:20

Hi Ralph,

New firmware is available. Please download actually firmware and T-Sensor configuration software (then run T-Sensor with "/service" parameter, main menu->Service->Update firmware...) . If a problem occurred check SOAP configuration with T-Sensor software. Have you only one sensor, or you have problem with more devices? After power failure flashing Ethernet LED by selected SOAP sending interval?

FW: P85xx 4-5-1.16
T-Sensor: TSensor ver. 2.3.0.0

New P85xx firmware fix some SOAP issue (mainly sending SOAP outside LAN), but your problem I have never seen before.

John

Last edited by HonzaD (13-11-2008 07:55:24)

Visitor · 25-11-2008 05:52:01

Hi John,

To answer your questions, there is only one unit with one probe. There is traffic every 5 seconds or so but that may be due to SNTP, WWW and email traffic which all work. The IP address for SOAP delivery is external and the SOAP message interval is 30 seconds.

Retested this problem the last couple of days and found it difficult to reproduce. I found other ways to stop the SOAP messages such as disconnecting the Ethernet connection for 15 seconds when power is reconnected (DHCP failed and the P8511 doesn't seem to retry when Ethernet is reconnected) and disconnecting the Ethernet for 3 minutes (SOAP messages don't recommence after Ethernet is reconnected).

So then then I updated the firmware to version 4-5-1.16 and web version 2.02 using Tsensor program as suggested. Figured out that the URL used for SOAP access no longer includes the configured IP. Adjusting the "SOAP address" parameter fixes that.

Now the issue where "disconnecting the Ethernet for 3 minutes stops the SOAP messages" seems to be fixed also. Just the "disconnecting the Ethernet connection for 15 seconds when power is reconnected stops the SOAP messages" remains, which is not so serious.

Thanks for your assistance.

Ralph.

HonzaD · 25-11-2008 09:05:18

Please try set static IP adders - disable DHCP. I hope static IP fix your problem.

If you power sensor with enabled DHCP, device try connect to the DHCP server. Because you have disconnected Ethernet connector this procedure fail and set "default" IP address - see DHCP protocol RFC (something like 169.254.x.x).

John

Last edited by HonzaD (25-11-2008 15:06:35)

Visitor · 09-07-2009 10:04:58

Well the unit mentioned above is finally installed in a production environment and it has a problem where it will stop sending SOAP messages after an interval between 1 and 24 hours. The P8511 never sends another message until the SOAP message transmission interval parameter is saved again (using the TSensor program this time). We have repeated this 3 times now and waited more than 24 hours for the transmissions to restart.

The SOAP message is sent via a wireless Internet link which is shared with general traffic. While the link is not perfect (as the Internet itself isn't) there are no power failures. This seems to be the same problem we had in testing where "disconnecting the Ethernet for 3 minutes stops the SOAP messages".

Was Comet able to reproduce this problem in the lab?

Firmware version 4-5-1.16 and web version 2.02

Ralph.

HonzaD · 09-07-2009 12:13:53

Hi Ralph,

I think you have a problem with your network infrastructure (some HUB/switch buffers overflow, etc.). We have a new firmware which improve compatibility with some "freaky" network devices. Maybe it can help.

Update to latest production firmware (web and firmware): http://forum.cometsystem.cz/doc/P85xx-4_5_1_20.zip
Latest SDK: http://cometsystem.cz/english/manuals/i … xx-apx.pdf

Important: New SOAP message from 4.5.1.20 devices isn't same as from older FW devices.

Code:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<InsertP85xxSample xmlns="http://cometsystem.cz/schemas/soapP85xx_v2.xsd">
<passKey>07940141</passKey>
<device>4352</device>
<temp1>23.1</temp1>
<temp2>23.1</temp2>
<temp3>22.8</temp3>
<temp4>22.9</temp4>
<alarms>lo,no,hi,hi</alarms>
<tempU>C</tempU>
<timer>10</timer>
</InsertP85xxSample>
</soap:Body>
</soap:Envelope>

John

Visitor · 17-07-2009 07:46:02

Firmware upgraded to 4.5.1.20, the new SOAP format noted, but still the same problem. In the last run the device transmitted for 9 hours 26 minutes before stopping. This is the longest so far.

People are using the same link for web browsing and email so the connection is there and it works. The P8511 is giving up when it encounters some problem and never transmits again.

Has Comet been able to reproduce this problem in the lab?

Ralph.

HonzaD · 27-07-2009 12:04:30

Hi,

I haven't been able reproduce this problem. Many customers uses SOAP protocol and this problems never been reported.

Probably you have something wrong, but I haven't idea what it is. Please check this steps:

1. Restore your P85xx to factory default via TSensor software.
2. Configure to your PC and P85xx static IP address (like: 192.168.1.1 and 192.168.1.2)
3. Connect your PC to a P85xx via cross Ethernet cable.
4. Configure P85xx (soap interval: 10s, source port: 81, destination port: 80, IP: 192.168.1.1 and target SOAP service)
5. Enable your SOAP service on port 80 and then check SOAP communication. Check RJ45 LEDs blinking if communication problem occurred (LED blink while SOAP message is sending).

John.

Visitor · 30-07-2009 07:00:03

Hi John,

The unit is installed in an industrial environment - not close to any IT lab. The testing you suggest was what we did for weeks before installing it and that had the problems above. Now testing on site show up similar problems.

1. Disconnect the Ethernet connector for 3 minutes and the SOAP updates stop and do NOT restart when the connector is re-inserted.
2. Disconnect the power for 3 minutes and the SOAP updates stop and do NOT restart when the power is re-connected.

Can you verify this behaviour?

Ralph.

HonzaD · 30-07-2009 09:07:50

Hi,

I check points 1., 2. and all is working properly. Do you try catch packets via some packet sniffer - Ethereal? Right LED stop blinking if you re-connect Ethernet connector (after 3 minuets)?
Do you have one or more devices? What kind of power adapter do you have?

John

Last edited by HonzaD (30-07-2009 09:09:56)

Visitor · 03-12-2009 12:18:17

Hello,

Just a oppinion for Ralph. I use 21 sensor H4531, mounted in electrical cabinets. Before to use Poe splitters, using normal power adapters, very often, once/day all sensors stop to send SOAP messages. I fix this by simply unplug and plug the power cord for each sensor. Now with PoE splitters, no problem, but anyway it is more easy to unplug the switch, and start again after 10 sec. Best regards. Marin Constantin

HonzaD · 03-12-2009 14:02:09

Hi,

Your H4531 devices stopped sending SOAP messages once/day, really? We are successfully passed test with uptime 1000+ hours without any SOAP failure. What is shown at IP/diag web page if problem occurred?

John

Visitor · 04-12-2009 16:41:47

Hello,

I do not know what diag page show, I fix this 1 month ago. Because I migrate to Poe solution, and the switch power passthru an UPS filter, since then no problem.
I know that, many of our automation PC simply freeze is the power supply has big variation & peaks. So this drive me to idea that the problem is the variation from power line not the sensor.

Best regards,
Marin Constantin

Last edited by Visitor (04-12-2009 16:42:41)

HonzaD · 07-12-2009 06:40:22

OK, for information about diag page see: http://cometsystem.cz/english/manuals/i … xx-apx.pdf on site 13.

John

Comet system forum

Temperature, Humdity,

Pressure Transmitters

and Data Loggers

#1 13-11-2008 06:19:11

P8511 won't send SOAP messages after a power failure

#2 13-11-2008 07:54:20

Re: P8511 won't send SOAP messages after a power failure

#3 25-11-2008 05:52:01

Re: P8511 won't send SOAP messages after a power failure

#4 25-11-2008 09:05:18

Re: P8511 won't send SOAP messages after a power failure

#5 09-07-2009 10:04:58

Re: P8511 won't send SOAP messages after a power failure

#6 09-07-2009 12:13:53

Re: P8511 won't send SOAP messages after a power failure

Code:

#7 17-07-2009 07:46:02

Re: P8511 won't send SOAP messages after a power failure

#8 27-07-2009 12:04:30

Re: P8511 won't send SOAP messages after a power failure

#9 30-07-2009 07:00:03

Re: P8511 won't send SOAP messages after a power failure

#10 30-07-2009 09:07:50

Re: P8511 won't send SOAP messages after a power failure

#11 03-12-2009 12:18:17

Re: P8511 won't send SOAP messages after a power failure

#12 03-12-2009 14:02:09

Re: P8511 won't send SOAP messages after a power failure

#13 04-12-2009 16:41:47

Re: P8511 won't send SOAP messages after a power failure

#14 07-12-2009 06:40:22

Re: P8511 won't send SOAP messages after a power failure

Board footer