Recipe - send value to NSCOM external tags

6 Posts
3 Users
0 Likes
35 Views
w.qin
(@w-qinarcinfo-com)
Posts: 21
Eminent Member
Topic starter
 

Hello,

How can we send command to modbus tags which with priority mode?
Because normally the tags' status are NS_COM, by send->receipe animation, doesn't work on these tags.
But if by send-register animation to single tag, it works.
Is there any effective way to solve this problem?

Thank you very much!

Lily

4186=606 modbus
 
Posted : 07/06/2018 8:41 am
e.mahaut
(@e-mahautarcinfo-com)
Posts: 270
Member Moderator
 

Hi Lily,

There are 2 options for recipes.
One is global and one for each recipe

4192=607 Recipe Settings

Could you please try and confirm.

Edouard

 
Posted : 08/06/2018 2:44 am
w.qin
(@w-qinarcinfo-com)
Posts: 21
Eminent Member
Topic starter
 

Thank you Edouard.
That works. 😆

 
Posted : 08/06/2018 10:31 am
w.qin
(@w-qinarcinfo-com)
Posts: 21
Eminent Member
Topic starter
 

Sorry Edouard,
I made mistake while testing it. It doesn't work even if ticked that two options.
So is that a bug? Should I make one SPR?
Lily

 
Posted : 11/06/2018 8:15 am
LM
 LM
(@l-micaudarcinfo-com)
Posts: 383
Member Admin
 

Hello Lily,

I wonder if you can first add some traces on the variable before making the SPR? It can be interesting.
Please see KB774.

 
Posted : 11/06/2018 12:16 pm
e.mahaut
(@e-mahautarcinfo-com)
Posts: 270
Member Moderator
 

Hi,

In fact, there are many levels (3) of options to know about recipes.
- The first one is the global option
- The second one is the recipe option

If both are OK, the recipe is sent but excluding variables which are NS and this is the reason why you get a message on the event viewer '... (@VarName) Variable not send (NS status)'

- The last one is more complex to understand because of the variable itself and also its protocol (for example, frame for Cimway cases)

Thus, it can depend on
1/ 'non permanent scan feature' (permanent scan for all variables option off + variable monitoring option)
2/ scan rate for frames or any reason the variable becomes NS

For the first case, the workaround is using RECIPE verb with STARTWATCH and STOPWATCH modes

For the second case, the workaround is configuring a scan rate even with an important value (5 minutes for example. Not greater than 59 minutes!) in order to get at least a value at startup. The other workaround is using CIMWAY verb with SCANMDF mode, but it is much more difficult to code and synchronize because of all frames scan to be managed.

 
Posted : 11/06/2018 3:05 pm