Pressure not updating

[Arnie]

Hi to all
For the last few days Cumulus has not been updating my pressure readings
Last night I re-set my WS2355 console then restarted Cumulus with the correct reading 1032.2
Now 12 hrs later the reading has not changed
I have attached the June log file

Any ideas anyone?

Thanks Brian

[steve]

Could you zip up the diags folder and attach it, and I'll see if there's anything in there. The pressure in your area does seem very stable at the moment, though.

[steve]

You're getting bad data readings, so it's ignoring them. Not just with the pressure:

6/21/2010 19:47:49.949 : Ignoring outdoor humidity: 110
6/21/2010 19:47:50.121 : Ignoring wind speed: -1000
6/21/2010 19:47:56.433 : Ignoring temp : outtemp = -1000
6/21/2010 19:47:56.433 : previoustemp = 13.1000003814697
6/21/2010 19:47:56.949 : Ignoring rel pressure: 32.3

It's also had problems reading the history data at start up (another symptom of the same problem, most likely), for the last two start ups:

6/21/2010 19:49:27.918 : WS2300 History Details: Data: 3B 40 00 00 00 00 00 00 FF 00
6/21/2010 19:49:27.918 : interval=60 countdown=5 numrecords=0
6/21/2010 19:49:27.918 : hr=0 min=0 d=0 m=0 y=2000
6/21/2010 19:49:28.136 : WS2300: failed to read pressure offset

6/21/2010 19:49:36.699 : WS2300 History Details: Data: 3B 40 00 00 00 00 00 00 FF 00
6/21/2010 19:49:36.699 : interval=60 countdown=5 numrecords=0
6/21/2010 19:49:36.699 : hr=0 min=0 d=0 m=0 y=2000
6/21/2010 19:49:36.902 : WS2300: failed to read pressure offset

It's clearly not 'external' interference, for the pressure to be affected. Loose serial cable or something like that? It's not a recent problem, you have similar problems in the files going back to early May. I'm not really sure what La Crosse owners do to solve corruption problems - try a different serial cable?

[Arnie]

Thanks Steve
Its a bit of a worry

I am connecting via USB so maybe I will try to connect to a 2nd computer using serial cable

[steve]

I am connecting via USB

Ah, right. I had assumed you weren't. That explains it.

[GraemeT]

Brian,
Get rid of the usb-serial adapter and use COM1.
Only then will you be rid of the dodgy readings for good.

[Arnie]

Thanks Graeme and Steve


I have 2 pc's, Cumulus and station were connected to No1 computer up to a few months ago.

Then updated this comp and realised I did not have a serial port after the upgrade so I then transferred the station and cumulus to No 2 computer

Since then I have lots of error msgs (errors 492 and 500)

On this comp I have 2 serial ports situated vertically above each other (I presume Com 1 and Com 2)
How do I find out which is Com 1 and which is Com 2?

Any clues please?

[Arnie]

The latest trial/error

Have connected console to top Serial port and set Cumulus to Com port 1

Then tried connected to lower Serial port setting Cumulus to Com 2

After rebooting Computer Console and Cumulus each time the result is the same

Cumulus is show correct readings for all except the Barometer Pressure, this is always 0000.0 hpa

However in the "Recent Extremes" section the Min Pressure is showing the actual pressure at the time I do the reset

[steve]

So you weren't actually using USB?

Please zip and attach the diags folder.

[Arnie]

Steve

My apologies for the misinformation originally

In fact I was using the serial connection but I had the USB button tagged in my Cumulus setup

Attached Diags folder

[steve]

You're still getting the problem with the 'bad' data. But at least at the moment it's just the pressure:

6/23/2010 11:15:12.140 : WS2300: failed to read pressure offset

6/23/2010 11:15:13.437 : Ignoring rel pressure: 33.9

Are you sure that you have set the pressure offset correctly?

[Arnie]

Steve

My Pressure offset is set at zero?

Is there a calculation that has to be done?

[steve]

The way you would normally do it would be to set your relative (sea-level) pressure using a known local reference, and then take whatever offset that happens to be. That way you correct for altitude and calibrate your barometer at the same time. At your altitude, the expected difference just allowing for altitude would be around 3 mb.

It's possible that in resetting your station, the memory locations holding the pressure offset have been corrupted in some way; it would be worth trying to set it - you could use zero, or 3, or you could try doing the calibration using a local reference, if you can find one and if pressure is stable there at the moment.

Is your console showing a sensible value for pressure?

[Arnie]

Thanks once more Steve

The console is showing 1031.0 at 26m Altitude
My nearest reliable weather station is at Bankstown Airport (BOM) showing 1034.4 at 6.5m

I do have a PWS very close at a much higher altitude, showing 1034.1 at 68.6m I don't know how accurate this station is

Your thoughts pls Steve

[steve]

I guess for now you can just set it to around 1034 - that fits with the theoretical 3 mb offset. It's not really important exactly what you set it to, I'm just hoping that the process of actually setting it will correct the corruption.