2.0.0-beta.3
Pre-release
Pre-release
[2.0.0-beta.3] - 10.09.2024
- BREAKING: Renamed
ReadWriteRawMultiCommand
propertywriteData
tovalue
- Added
warning
event to listen for console warnings - Bugfix:
writeRawByPath()
didn't use thetargetOpts
parameter - Type
ClientEvents
renamed toAdsClientEvents
- Added automatic deletion of stale subscriptions / unknown ADS notification handles
- New setting:
deleteUnknownSubscriptions
(default:true
)
- New setting:
Thank you Christian Rishøj for contribution!
[2.0.0-beta.2] - 26.08.2024
- Changed
subscribeSymbol()
->subscribeValue()
- Bug fix: Fixing issue #144
[2.0.0-beta.1] - 24.08.2024
IMPORTANT: This is a major version update. There are lots of breaking changes!
Updating v1 -> v2 requires manual changes to your codebase!
See MIGRATION.md for all breaking changes and follow the instructions. This changelog does not have breaking changes listed for 2.0.0.
Changes
- Everything rewritten in TypeScript
- Everything is tested before releasing
- Lots of optimizations
- Lots of name changes
- New methods:
resetPlc()
,readWriteRawMulti()
,writeRawByPath()
,readValueBySymbol()
,writeValueBySymbol()
- New setting
disableCaching
: disables all symbol and data type caching - Added optional
targetOpts
argument in all methods- Possible to provide different target address (AmsNetId and/or AdsPort) than specified in the settings
- Caching is only available for the original target provided in settings
- The same client can be used for many different targets at the same time
- Added support for reading/writing
INTERFACE
data types - Added support for reading/writing empty
FUNCTION_BLOCK
s - Added support for reading/writing
BIT
data type - Writing a
STRING
orWSTRING
value that is longer than the target data type causes the string to be truncated.- Previously the string end character was lost, which caused "never ending string" and
<Value of the expression cannot be retrieved
in PLC online view. - E.g. writing 85 bytes of string to
STRING(80)
variable
- Previously the string end character was lost, which caused "never ending string" and
BOOL
andBIT
data values are now true if the value is anything else than 0- In TwinCAT,
BOOL
is true if the value is anything else than zero (see x_TO_BOOL) - Before, ads-client set the value to true only if value was true or 1, otherwise it was 0
- In TwinCAT,
writeControl()
accepts also string values foradsState