SreenathRavindranath / xbee-api

Automatically exported from code.google.com/p/xbee-api
GNU General Public License v3.0
0 stars 0 forks source link

Unknown radio type #15

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.used the code provided in the book "Building Wireless Sensor Networks"
2.Configured the coordinator and router accordingly.
3.Built the sensor network.
4.ran the code in Processing.

What is the expected output? What do you see instead?
the thermometers should appear and they should show the readings of the data 
sent from router to coordinator.

I see:

[2012-05-28 18:58:37,640] [Animation Thread] [WARN] 
[com.rapplogic.xbee.api.XBee] Unknown radio type (HV): 30

What version of the product are you using? On what operating system?
Xbee Pro Series 2 (s3b); Windows 7

Please provide any additional information below.

Original issue reported on code.google.com by noor.f...@gmail.com on 28 May 2012 at 4:06

Attachments:

GoogleCodeExporter commented 9 years ago
I guess the code was written before the Pro Series (S2B) were launched. It has 
no real effect on the code as such, but if you want to make the warning 
disappear, just add a "case 0x1e:" as below. The code is in the 
com.rapplogic.xbee.api package in the XBee class.

if (ap.isOk()) {
                switch (ap.getValue()[0]) {
                case 0x17:
                    log.info("XBee radio is Series 1");
                    break;
                case 0x18:
                    log.info("XBee radio is Series 1 Pro");
                    break;
                case 0x19:
                    log.info("XBee radio is Series 2");
                    break;
                case 0x1a:
                    log.info("XBee radio is Series 2 Pro");
                    break;
                case 0x1e:
                    log.info("XBee radio is Series 2 Pro (S2B)");
                    break;
                default:
                    log.warn("Unknown radio type (HV): " + ap.getValue()[0]);
                }
            }

Original comment by volle...@gmail.com on 24 Jul 2014 at 6:35