Ideas
+4
Completed
Modbus protocol
Theo Derks - NL (distributor) 12 years ago
in Applications / Studio (Server editor)
•
updated by Oksana (expert) 9 years ago •
15
Hi,
For the modbus protocol we must use an On-Press command, sending a '1' to the Modbus register, always followed by an 'On-Release-command', sending a '0'.
The questions: can you improve the Modbus protocol, so this will be done in the default On-Press command? So the On-Press command is sending the 1, followed by the 0? Or make a special command (only if the installer is using a Modbus protocol), with this function build-in? Because now, for every button that will be used in a project, the installer has to made 2 commands, and that's not logical, so it's better to build-in this in the protocol for Modbus.
This should be a great improvement for all Modbus users!
Thanks
Theo
For the modbus protocol we must use an On-Press command, sending a '1' to the Modbus register, always followed by an 'On-Release-command', sending a '0'.
The questions: can you improve the Modbus protocol, so this will be done in the default On-Press command? So the On-Press command is sending the 1, followed by the 0? Or make a special command (only if the installer is using a Modbus protocol), with this function build-in? Because now, for every button that will be used in a project, the installer has to made 2 commands, and that's not logical, so it's better to build-in this in the protocol for Modbus.
This should be a great improvement for all Modbus users!
Thanks
Theo
Answer
+1
var device = IR.GetDevice("Modbus TCP");
this.Pulse = function() {
device.Set(options.address, 1);
var unset = function(){
device.Set(options.address, 0);
};
IR.SetTimeout(500, unset);
};
like this? :-)
do make sure the time pressed can be configurable if you are going to integrate this. not all systems respond to a button press equally fast.
this.Pulse = function() {
device.Set(options.address, 1);
var unset = function(){
device.Set(options.address, 0);
};
IR.SetTimeout(500, unset);
};
like this? :-)
do make sure the time pressed can be configurable if you are going to integrate this. not all systems respond to a button press equally fast.
Like it but not for me ;-) don't use scripting with those functions.
But thanks!
But thanks!
+1
Hi,
This functionality will be useful for KNX too. To have a toggle button. It could also be achieved by adding a toggle option to trigger button.
Thanks,
Roger
This functionality will be useful for KNX too. To have a toggle button. It could also be achieved by adding a toggle option to trigger button.
Thanks,
Roger
Hello guys
But I worked with real Modbus installations different way, without pulses, it should not work this way by default.
And it is possible when you press the button too fast, controller can lost the Release event and just turn the address on.
So I think it would be better to make an option "Puls" when u drag the command. Available for Press, Release and Hold event:
send [ 1 ] for [ 500 ] ms and then turn it off
As a result:
What do u think about it?
But I worked with real Modbus installations different way, without pulses, it should not work this way by default.
And it is possible when you press the button too fast, controller can lost the Release event and just turn the address on.
So I think it would be better to make an option "Puls" when u drag the command. Available for Press, Release and Hold event:
send [ 1 ] for [ 500 ] ms and then turn it off
As a result:
What do u think about it?
+1
Hi Kaaty, i think your idea is the most flexible we can have; for all protocols....
Roger/Rens/Matthijs, do you have additional ideas to improve this idea? Otherwise the programmers can start with implementing it...
Thanks
Theo
Roger/Rens/Matthijs, do you have additional ideas to improve this idea? Otherwise the programmers can start with implementing it...
Thanks
Theo
Hi all,
I agree with Ekaterina this should be optional and not default. The proposed implementation should work but i would like to suggest an alternative:
I think this makes it clearer you are using a different action and leaves more options to include even more actions in the future.
I agree with Ekaterina this should be optional and not default. The proposed implementation should work but i would like to suggest an alternative:
I think this makes it clearer you are using a different action and leaves more options to include even more actions in the future.
yes we could implement "Send Puls" like a separated Action, it makes an interface less congested, but u have to
1. drag the command
2. choose an action
3. set value and delay.
3 steps instead of 2. But if we talk about all the users, this feature will be optional, so maybe it's ok?
Matthijs, Theo, what do u think?
1. drag the command
2. choose an action
3. set value and delay.
3 steps instead of 2. But if we talk about all the users, this feature will be optional, so maybe it's ok?
Matthijs, Theo, what do u think?
Hi Kaaty,
I prefer your proposal, but let the installers decide ;-)
They have to work with the Editor daily ;-)
Thanks
Theo
I prefer your proposal, but let the installers decide ;-)
They have to work with the Editor daily ;-)
Thanks
Theo
Good option i think, automatic failsafe, thats how i program it now.
but now i have to put the send numbers and the delay manually, with this option it's one time.
but now i have to put the send numbers and the delay manually, with this option it's one time.
Prefer the Kaaty option... think that works faster.
So my vote is for the Kaaty way ;)
So my vote is for the Kaaty way ;)
Customer support service by UserEcho
It was added in iRidium Studio