WM918 Connection issues in WD

[optrex]

I have a WM918 connected to Ubuntu 9.10 via a physical serial port.
The serial port works and I can run other equipment off it in Ubuntu without issue.
The WM918 connects using virtualbox and an XP client to both Cumulus and VWS and works fine with /dev/ttyS0 being directed to COM1 in the serial pass through.
The linux version of WD (10.37L) will not pick up the data stream from the WM918, with the exception of about a hour last night (it stopped working again after a save and exit). I got it working just by changing and swapping settings. Eventually it picked up from COM 1 (as it should)

The COM port is fine, it even picks up as connected using the 2500 option in WD, but for some reason WD is not responding. I have tried the other OS settings to see if that helps. I have tried releasing the COM port etc, without success. I can start virtualbox back up and everything will work fine again on other software. The WM918 console is mains powered.

I've read through a lot of other historical 918 threads and they all say its not WD, its the Linux setup. I think I've done enough to rule this out as the COM port works in other applications on the Ubuntu platform and the weather data comes through in other software. Would appreciate some help and suggestions please

Thanks in advance

[Weather Display]

with the exception of about a hour last night

so it does work,yes?

[optrex]

it has worked, once yes. So there is hope

[Weather Display]

then you just need to repeat the settings/serial properties, etc , you had when it was working

[optrex]

then you just need to repeat the settings/serial properties, etc , you had when it was working

Oh dear   I'm sorry but can't believe that's a serious reply to a support question.
Do you not think that given the detail that was put in the original post that I've tried that already?

I got it working just by changing and swapping settings. Eventually it picked up from COM 1 (as it should), but it stopped working again after a save and exit. To avoid any doubt I have tried a similar approach several times since but it has not been effective.

[BigOkie]

Oh dear   I'm sorry but can't believe that's a serious reply to a support question.
Do you not think that given the detail that was put in the original post that I've tried that already?

I got it working just by changing and swapping settings. Eventually it picked up from COM 1 (as it should), but it stopped working again after a save and exit. To avoid any doubt I have tried a similar approach several times since but it has not been effective.

Have you thought about changing permissions on the Com port via chmod?

Something possibly like chmod 766 /dev/ttyS0 (or whatever TTYSx your comport is)?

[optrex]

Hi BigOkie,

Thanks for the reply. I have followed the instructions for udev on the ubuntu platform as listed in the wiki http://wiki.weather-watch.com/index.php/Linux_Weather_Display_Manual
I can confirm that the COM ports are 777 as is the WeatherD file.


Within WD in the WS2500 tab, I get the following:

Loaded all time records
Connecting com port
trying to open comport 1 8
Com port connected OK

[BigOkie]

Hi BigOkie,

Thanks for the reply. I have followed the instructions for udev on the ubuntu platform as listed in the wiki http://wiki.weather-watch.com/index.php/Linux_Weather_Display_Manual
I can confirm that the COM ports are 777 as is the WeatherD file.


Within WD in the WS2500 tab, I get the following:

Loaded all time records
Connecting com port
trying to open comport 1 8
Com port connected OK

One other thing to keep in mind is that Brian is providing the Linux version free of charge, so he won't be able to update it as frequently as that which puts bread on his table.  I used the Linux version for about two years, but decided it was way too much of a hassle (would lock up about every day requiring a restart; I don't fault Brian for that, it's the nature of Linux when you're writing specifically for Windows).  I guess that the multiple flavors of Linux and versions of GTK/QT don't help Brian in his coding much.  I put XP SP3 on a machine and bit into my wallet for the Windows version and can say I'm glad I did.

I'm afraid other than the previous suggestion of the comport permissions that I can't be of much more help given that the only two stations I've ever owned are a Lacrosse 2310 and my current, Irox/Honeywell TE923W.

I hope you can get a resolution.

[optrex]

I'm afraid other than the previous suggestion of the comport permissions that I can't be of much more help given that the only two stations I've ever owned are a Lacrosse 2310 and my current, Irox/Honeywell TE923W.

I hope you can get a resolution.

OK, well many thanks for your help so far.

[Weather Display]

Oh dear Sad  I'm sorry but can't believe that's a serious reply to a support question.

I sure hope you are not here to cause trouble on this forum Optrex
it was working but is not now then that is likely to be a permissions issue after restarting WD (assuming WD is set to the correct station type)


I am seriously thinking of dropping the linux version due to attitudes (like it cant be a problem at my end (but there is so many different combinations of distros/settings/setups that its a nightmare to support (might work OK for me an others but not for other people) displayed on the linux section over the years, and instead concentrate on the Mac version, which has only the one OS flavour and same hardare

[Weather Display]

for the record, just did a test here with my WM918 and the linux version
no problems, data works after going setup, save and exit, on the next restart, every time

(using a USB to serial)

so there is no problem to fix here for the WM918 station connection

[optrex]

Thanks for the test Brian, out of interest what COM port is assigned to your USB to serial adapter?

[Weather Display]

I set it as it says to set in the com port setup if using USB
i.e
/dev/ttyUSB0

and using the default Distro built in USB to serial driver

[optrex]

Hi Brian,

Yes I appreciate the use of that setting when using a USB to serial adapter, but as I understand that I dont need to enter /dev/ttyS0 in that field as I am using a physical COM port

What I am trying to ascertain is which COM port you selected during your test. If you are going through a USB to serial adapter, then you are not using COM1. I noticed in previous comments that people have been advised to get a USB to SERIAL and it has worked in many instances, but you shouldn't need to do that.

I am thinking along the lines of there being a communication error from within the WD programming when using COM1 with a WM918 that may not be apparent when using another COM port. I am thinking along these lines because:

1) WD detects COM1 as open when looking at the WS2500 settings, but does not receive data
2) The COM1 port works correctly across other hardware
3) The COM1 port works correctly across other software
4) All external testing programs and comand line returns indicate there are no issues, with comminications or permisisons on COM1
5) The combination of COM1 and WD is the only thing that does not work as intended (on my setup)
6) WD is detecting other equipment using other COMS (ie it picks up the data output from my LD250 on COM2)

As a test I will use the same physical port but assign it to /dev/ttyS2 in Ubuntu when I get home then select COM3 from within WD. If that works out OK, then I think that will give a clear indication as to where any issues lie.

[optrex]

I sure hope you are not here to cause trouble on this forum Optrex
it was working but is not now then that is likely to be a permissions issue after restarting WD (assuming WD is set to the correct station type)

Ok, we're posting over each other, so I will wait and see how things go during my tests before commenting again on the technical aspects.

I am here for support of a product Brian, nothing else. I have invested a lot of my time to test and provide feedback to get your product working correctly for myself and maybe to the benefit of others. All I am after is detailed support related responses to my questions. If you felt you answered my support based post to the best of your ability, given the information supplied, then that's fine.