exsilium / ruby-xbee / 34 / 2
56%
master: 56%

DEFAULT BRANCH: master
Ran
Files 19
Run time 4s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 55.294% (+5.0%) from 50.26%
2.0.0

push

travis-ci

exsilium 
APIModeInterface improvements, OTA application firmware upgrade, new frames

- API version pumped from 1.1.0 to 1.2.0 together with the gem version
- BaseAPIModeInterface and subclasses have been changed to assume :API mode by default - this was relevant only for Series 1 modules where AT/API mode could be switched on the run. As Series 2 modules have become more popular, calling the BaseAPIModeInterface assumes you are running Series 2 which is in API mode already
- API mode 1 (non-escaped) is set default instead of API mode 2 (with escaped control characters). Although API mode 2 is very useful in noisy environments and is superior (in my mind to API mode 1) Digi specification assumes AP1 (API mode 1) as default. Further more, the programmable XBee applications through the XBee SDK refuse to properly work if the module is in AP2 mode. As the starting point will always be AP1, seems to be more compatible between different modules and products, the default is changed from AP2 to AP1. You need to update your code if you relied on the fact that API mode would use escaping by default.
- Explicit Addressing ZigBee Command Frame (0x11) packet attributes added
- ZigBee Explicit Rx Indicator (0x91) (AO=1) packet attributes added
- ota_upgrade.rb sample OTA XMODEM based application firmware upgrade added based on the new frames
- Frame initialization silenced (you can enable via -W2 verbose mode if you really need it)
- Command sending silenced (-W2 for more verbose output)
- Hygiene around dependencies (Gemfile -> .gemspec)
- Tests updated based on information above

376 of 680 relevant lines covered (55.29%)

5.18 hits per line

Source Files on job 34.2 (2.0.0)