Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

button execution issue

I've been having issues with buttons that are tied to my emerson drive talking modbus ethernet. The issue being that when I press a momentary pushbutton, I get a double bump like I hit the pushbutton twice. It'll hold true every once in a while too. In the event log, it reads as followed

cwbutton1 adjusted to on by the control
cwbutton1 adjusted to off by the control
cwbutton1 adjusted to on at the source
cwbutton1 adjusted to off at the source

I'm running lookout 6.0.2. It only happens when I'm connected to a device over modbus ethernet. I'm guessing that I missed something in the setup somewhere.  Any help would be appreciated


Haj


Message Edited by Haj on 04-23-2008 08:53 AM
0 Kudos
Message 1 of 2
(6,097 Views)
This problem has a long history... I have to say Lookout is designed in this way, although it looks like unreasonable.
You click the button, it turns on "by the control", a write command is being sent. After you release it, it turns off "by the control". But after the ON command is sent, Lookout will read the current value on this register before it sends out OFF command, because Lookout wants to get the ON status if there are any display or control on panel. The button is connected to the register by the remote source, so it will reflect the change on status. So, Lookout reads the ON status back and turns ON the button again "at the source". Then Lookout writes OFF command to device. On the next poll, Lookout reads the OFF status and turn OFF button "at the source".
 
I know that it doesn't look good in Lookout, we will consider if we need to improve it.
Ryan Shi
National Instruments
0 Kudos
Message 2 of 2
(6,072 Views)