Releases: BlueAndi/vscp-framework
Releases · BlueAndi/vscp-framework
VSCP framework v2.0.3
VSCP framework v2.0.2
Main release point is the changed recommended nickname discovery timeout from five to one second.
See 2024-05-22 https://github.com/grodansparadis/vscp-doc-spec/blob/master/vscp_specification_history.md
VSCP framework v2.0.1
Updates the library.json used by Platformio to include the ./src/events folder too.
VSCP framework v2.0.0
VSCP-framework repository was restructured. The new structure is improved for providing it as PlatformIO libraray or to include it as git submodule.
The following was moved to a dedicated repository:
-
VSCP bootloader (original in /vscp/bootloader)
-
CLI tools (original in /projects/pc)
-
My Projects (original in /projects/avr)
-
VSCP framework
- New Features
- Firmware device code added to register map, which was introduced with VSCP specification 1.13.0
- Improvements
dataNum
variable in the VSCP message renamed todataSize
. You may need to update at least your transport layer adaption.
- Bugfixes
- The process routine will return now TRUE until a extended page register read is complete #43. Thanks to Kamil!
- New Features
-
Examples
- avr90can
- VSCode and PlatformIO configuration added.
- avr90can
VSCP framework v1.3.0
-
Common
- vscphelperlib updated to v14.0.2 (note, the windows vscphelperlib is still v13.0.0).
-
VSCP framework
- Added CLASS1.ALARM VSCP_TYPE_ALARM_RESET event added.
- Added CLASS1.MEASUREMENT VSCP_TYPE_MEASUREMENT_REACTIVE_POWER and VSCP_TYPE_MEASUREMENT_REACTIVE_ENERGY events added.
- Added CLASS1.INFORMATION VSCP_TYPE_INFORMATION_PROXIMITY_DETECTED event added.
- Bugfixes:
- The event description (doxygen) fixed for all events, which used the frame references in the protocol definition.
VSCP framework v1.2.0
-
Common
- The AVR CAN library supports now the ATmega32/64/128M1 too. Thanks to onitake!
- The AVR CAN library contains some deprecated stuff, based on older days with winavr. One of them was updated. Thanks to onitake!
- The AVR CAN library updated to revision of 22th august 2016 of https://github.com/dergraaf/avr-can-lib
-
VSCP framework
- Added CLASS1.CONFIGURATION events. Thanks troky for updating the protocol definition!
- Added CLASS1.INFORMATION VSCP_TYPE_INFORMATION_INCREMENTED and VSCP_TYPE_INFORMATION_DECREMENTED events added. Thanks troky for updating the protocol definition!
- Added CLASS1.CONTROL VSCP_TYPE_CONTROL_INCREMENT and VSCP_TYPE_CONTROL_DECREMENT events added. Thanks troky for updating the protocol definition!
- Optional status parameter added to VSCP_TYPE_SECURITY_MOTION.
- CLASS1.DIAGNOSTIC events VSCP_TYPE_DIAGNOSTIC_CHARGING_ON and VSCP_TYPE_DIAGNOSTIC_CHARGING_OFF added.
- CLASS1.SECURITY events VSCP_TYPE_SECURITY_GAS, VSCP_TYPE_SECURITY_IN_MOTION, VSCP_TYPE_SECURITY_NOT_IN_MOTION and VSCP_TYPE_SECURITY_VIBRATION added.
- CLASS1.MEASUREMENT events VSCP_TYPE_MEASUREMENT_RADIATION_DOSE_EQ, VSCP_TYPE_MEASUREMENT_RADIATION_DOSE_EXPOSURE and VSCP_TYPE_MEASUREMENT_POWER_FACTOR added.
- CLASS1.MEASUREMENT event VSCP_TYPE_MEASUREMENT_ENERGY: Optional unit Wh added.
VSCP framework v1.1.0
- VSCP framework
- Bugfixes:
- CLASS1.DISPLAY Set LED fixed. Thanks troky!
- CLASS1.INFORMATION Node Heartbeat fixed. Thanks troky!
- Bug in uint32 function parameter handling in the event abstraction fixed. Thanks troky!
- Bug in vscp event module generation fixed in case of float function parameters. Thanks troky!
- Improvements:
- If in the decision matrix the zone/sub-zone match is enabled and the received zone/sub-zone is 0xFF (which applies to all zones/sub-zones), the decision matrix row will be considered. This way there is no need anymore to add a separate decision matrix row to handle 0xFF zone/sub-zone. Thanks troky for the hint!
- Features:
- Added Enter/Exit CLASS1.INFORMATION events. Thanks troky!
- Updated CLASS1.CONTROL protocol and generated the corresponding event abstraction modules. Thanks troky!
- The vscp_core_process() function returns now TRUE if a received event was handled, otherwise FALSE. This can be used for a faster handling of received events, e.g. call it in a loop as long as events are handled. But be aware about the watchdog. ;-)
- Bugfixes:
VSCP framework v1.0.0
- VSCP framework
- Bugfixes:
- Fixed CLASS1.CONTROL Timed pulse on/off to match specification. Thanks troky!
- Improvements:
- Optimized decision matrix (+ extension) access during normal operation.
First its checked whether the decision matrix row is enabled or not.
If its enabled, the whole decision matrix row is read at once from persistent memory.
Please update your vscp_ps_access.[ch] files accordingly!
#20
- Optimized decision matrix (+ extension) access during normal operation.
- Features:
- CLASS1.CONTROL, Type=44, "PWM" added. Thanks troky!
- With VSCP_CONFIG_START_NODE_PROBE_NICKNAME you define where to start with the nickname probing. Thanks troky!
- All VSCP type headers are generated now from vscp-protocol.xml and some of the types changed in its name. Please update your sources accordingly!
- All VSCP event abstraction modules are generated now from vscp-protocol.xml. Their file names changed to vscp_evt_...
Please update your sources accordingly!
- Bugfixes:
VSCP framework v0.9.0
- VSCP framework
-
Bugfixes:
- Fix of misspellings/typos, thanks to TomasRoj.
- VSCP measurement events fixed, because internal the parameters unit and index in the vscp_data_coding_getFormatByte() call were reversed. Thanks to troky!
-
Features:
- CLASS1.ALARM, Type=12, "Watchdog" added.
- CLASS1.INFORMATION, Type=80, "Updated" added.
- CLASS1.WEATHER/CLASS1.WEATHER_FORECAST Type=52, "UV Index" added.
-
VSCP framework v0.8.0
-
Examples
-
PC
- Fixed the GUID in the event, sent by the node. It must be always
a combination of interface GUID and the node nickname id at LSB byte. - Fixed the default option of supported events.
- Fixed the GUID in the event, sent by the node. It must be always
-
Projects
-
PC
- All projects adapted according to the possible usage of vscphelper library in debug or release variant.
-
VSCP framework
-
Bugfixes:
- CLASS1.INFOMRATION Type=77 month/year was in wrong position in the event data.
-
Features:
- CLASS1.INFOMRATION Type=78 and 79 added (rising and falling edge detection)
- CLASS1.INFORMATION Heartbeat event supports now extra data, see vscp_information_sendNodeHeartbeatEventEx().
- If your node shall send a custom heartbeat with user data and extended data,
enable VSCP_CONFIG_ENABLE_CUSTOM_HEARTBEAT in your configuration. Find the function prototype in
the vscp_portable.c module. Thanks troky!