Forum Replies Created
-
Posts
-
There was a similar error when switching from version 6.3.X to 6.4.x, or even when switching to 6.3.X, some methods changed there. And it’s possible that your module version doesn’t match the kernel version.
Check the version history in the documentationNetFramework 4.8 and Dotnet 8 are different systems.
You need to install two components from dotnet 8 according to the installation description.
Current version 8.0.18https://dotnet.microsoft.com/en-us/download/dotnet/8.0
Hosting Bundle and .NET Desktop Runtime 8.0.18
Judging by the images from the Modpoll configuration documentation, everything seems to be the same, but your device simply does not respond to one of the commands.
Perhaps the manufacturer changed something in the new version and did not update the documentation.
If this command was supported, but you got the wrong address, the device would give an error response. Try polling one register from 0 using Holding RegistersAnother example of event generation from the driver
You probably need to make a derived driver for events from the device. Connect the DrvModbus driver as required. As a channel, make something like an indicator of the presence of an event to save the time of occurrence in the database. Maybe an event counter.
If the events that have occurred are sequentially arranged in the event buffer, and their sequence may be different, this is probably the best option. Creating a list of events should probably be done through for(foreach) and selecting them from the list of possible ones.and if the value is 5 but you read 10, will there be an error or just zeros? and how are the events arranged? are these consistent occurrences? how will you identify them?
The module does not support multi-channel like. Or no more than 2 in the 6th version. I haven’t watched it for a long time. You can create a Calculated channel for applying any scripts in which you will compare the required channels and only then apply the module to this channel.
1. ModDiffCalculator – One of the options that solves this problem.
2. Channel 1, to save the total reading every hourEveryHour(() => Data(327))
(Channel 327 – Total Energy from device)
Channel 2 –EveryHour(() => Val(360) - PrevVal(360))(Difference. Channel 360 here is Channel 1)There may be different approaches.
As the author noted, the delay in hourly formulas can be useful, but here it is necessary to combine the minute with the hour, and this usefulness went sideways 🙂
The reason turned out to be that the HourStarted formula was triggered after 30 seconds, as the hour arrived, and EveryMin was triggered at 0 seconds. The delay in the HourStarted formula is useful in some cases. You can update the Scripts table in the Calendar entry to make it work.:EveryMin(() => HourStarted() ? 0 : Val() + 1)These changes will be included in the project template in the next release.HourStarted() is running with a delay. The revision of the formulas has apparently not yet been included in the release.
Use a translator if you need to understand.
