Comments on: WMR100N + Mac == True (soon)

By: Per

Per — Tue, 28 Jul 2009 17:20:41 +0000

Have done some experimenting and I was wrong. In my data stream there is one FF between individual measurements, and FFFF once every minute. All single FF are preceeded by 00, 01 or 02 – have no idea what they mean but they come after the closing checksum byte in all measurements.

By: Per

Per — Mon, 27 Jul 2009 10:29:13 +0000

I’m pretty sure, but I will have a look at your code and see if I might have missed something. My actual implementation looks more on frame identifiers and expected lengths than delimiters so it might be that I’ve overlooked something. And thanks for your comment!

By: Weber

Weber — Sun, 26 Jul 2009 23:49:38 +0000

Hi,

I have a Windows program (called WSDL) for the WMR100 on SourceForge. This program is keying off of two bytes of 0xff for the record separator — but your protocol page says you are seeing “0×00,0xff” instead. Are you sure about this? I haven’t heard anyone complaining that WSDL is having trouble with the new WMR100N…but I’d really like to know if O.S. is changing the protocols on us…?

– Weber

By: Per

Per — Sun, 21 Jun 2009 05:41:16 +0000

Excellent, a few more bits figured out. Have found several other projects but not this one, thanks!

By: Xander

Xander — Sat, 20 Jun 2009 18:56:07 +0000

Hi,

I found this project on sourceforge. It has extensive wmr100 record descriptions (look for WMR100DataParser.cs in the sourcepackage).

Enjoy!

By: Per

Per — Sat, 20 Jun 2009 07:23:03 +0000

Yes, the 1 length records do play part as long as they come in the 8 byte long USB reports in which the actual data is transported, one or two bytes for each USB report. WMR100 also sends 1 byte long USB reports which I have found no meaning in.

By: Xander

Xander — Sat, 20 Jun 2009 05:48:49 +0000

Thanks!

I don’t know if it’s because i have a rms300 (which alledgedly speaks wmr100 protocol becaue it works with that setting in other sw) but there’s a difference in the protocol used by it and your description.

The 01 length records do play a part, and the record seperator seems to be 0xff 0xff instead 0×00 0xff which your document describes. This way at least i get usable records.

By: Per

Per — Fri, 19 Jun 2009 17:46:42 +0000

OK, I have published a first draft of the protocol description.

By: Per

Per — Fri, 19 Jun 2009 16:36:49 +0000

Thanks, it was great. Celebrating midsummer with the traditional herring. Fell asleep after too many shots instead of working with my WMR100 thing…

By: Xander

Xander — Fri, 19 Jun 2009 12:38:42 +0000

Hope you enjoyed your lunch (nice cam )!