No data with WMR918

[n7dq]

Another quick thought, is the serial port enable at the bios level?

Mike

[Coyote]

This may a little off the wall
is youconsole and Linux  machine times are the same I have The 968 and I confirm it does work
Another option is try a complete reset of the console
Coyote

[Yves]

before starting WD type in : export DEBUG=
then start WD.
Normally after WD is started you should see debugging messages sent by the libcom functions. Tell us what you see. I am afraid you'll get error "resources busy" or smthg like this. This is an issue we are trying to fix.

Yves.

[thegasman]

First of all, thanks everyone for taking the time to reply.

Mike - I totally get what you say about logically searching for the cause of the problem. As I see it, I know the hardware works as the same hardware works 100% with WD on XP. I'm 99.9% certain comm 1 is the correct comm port, and I only have one serial port on this laptop. Short of reinstalling XP and seeing which comm works I won't be 100% certain. I have ascertained that comm 1 is accessible to software under my Ubuntu install, and I can receive data on it at 9600 baud with minicom. Why logserial won't compile I don't know, but I can't see it will add anything to what minicom is telling me (i.e. data is being received on ttyS0 at 9600 baud).

Coyote - It's encouraging to hear<you have the same setup working. I'm not giving up yet!  I may reset the console, but I'm receiving data on the serial port OK!

Yves - I have tried as you suggested. Here are what seem to be the relevant bits of the output:
Opening the serial port /dev/ttyS0
Saving serial configuration
Serial port /dev/ttyS0 opened File desc = 16
setting speed to 9600
ser_read : Entering
ser_read error Resource temporarily unavailable
Read size -1 :
ser_read : Exiting

Thanks,

Martin

[Coyote]

JUst for the heck of it try another Comport number in setup I had kubuntu in the past had a different comport that the windows version had.

Coyote

[Yves]

Martin,

go in ./deploy
rename libcom
mv  libcom.so libcom.so.old
download libcom.zip attached
move it into deploy,
rename
mv libcom.zip libcom.so
redo the test with DEBUG set

[thegasman]

Yves,

Success! 
Well, partial success at least with your new libcom.

Here is the terminal output now:
Opening the serial port /dev/ttyS0
Saving serial configuration
Serial port /dev/ttyS0 opened File desc = 16
setting speed to 9600
Read  Size 80 : 6 0 82 1 48 7 9d c1 0 0 6 3a ff ff 6 0 82 1 48 7 9d c1 0 0 6 3a ff ff 0 0 2 60 1 24 0 7 8c ff ff 0 0 6 61 1 24 0 7 91 ff ff e 37 43 ff ff 1 0 0 90 44 4 0 0 0 0 1 1 99 72 ff ff 0 0 3 60 2 24 0 5 8c

I get temp, humidity, and pressure data in WD (no wind though), and the data quality light goes green. Data updates are very slow though, maybe every 5 minutes rather than every few seconds under windows. Also, it seems a bit temperamental, sometimes receiving data, and sometimes not.

What was changed in the update?

Thanks,

Martin

[Weather Display]

thats a large read size
it should be getting the data packets in smaller size chunks than that
also wondering what change you made too Yves?

[Yves]

I made no significant changes to libcom, Seeing the error I made a change in libcom to always call ser_readVp instead.
thegasman could you confirm you using an Oregon 918 on a raw serial port or on USB serial?

Yves

[thegasman]

Yves,

It's an OS918 (it also says WMR968 on the back) attached to the raw serial port (not usb). I'm using Comm 1 and WMR968 settings in WD.

Martin

[Weather Display]

make sure you are using  the  wmr968 station type (so that the barometer works correctly)

[thegasman]

make sure you are using  the  wmr968 station type (so that the barometer works correctly)

Yes, that's what I'm doing.
Further trial with new libcom suggests that it is in fact only reading one set of data at startup, and that it is not updated. There are no errors in the terminal window though.
Where do I go from here? I don't understand the change Yves has made or what it means.

Martin

[Weather Display]

not sure whats happening
the wmr968 sends data , without needing it to be requested
although the DTR and RTS lines need to be set high (its possible that is not happening correctly through your serial port on that machine)

[thegasman]

although the DTR and RTS lines need to be set high (its possible that is not happening correctly through your serial port on that machine)

I have checked with statserial, and both DTR and RTS are high.
I now don't seem to be getting any data at all again, I don't know why, I haven't changed anything I can think of!
Having read some of the other threads in the forum, it strikes me that my issue appears similar to n7dq's 'datalogger sync issues'. However, as there doesn't seem to be a readily available solution it's looking increasingly like I'll have to reinstall windows on my laptop, where WD works 24/7. 
Maybe I'll dual boot and an eye on the Linux version.

Martin

[Weather Display]

no, it wont be the same as n7dq sync issues
different hardware, different commmands involved, nothing the same

its more likely some configuration /software/permissions/linux problem with the serial port, instead