MOD300 RTAB mod.PU412 vs RTAB mod. PU514
I am working with a MOD development system composed by a notebook with
a VMware workstation running a virtual MOD300 Engineering station connected
to a RTAB PU412. I put all the CCF of the real control system on this node to make some tests.
I am able to do "almost "anything" .
I remember long time ago when I worked with "real" MOD300 nodes
(Multibus Turbonode or AdvantStation) that I could do anything,
(e.g LOOPFCM parameters setup, etc..) on a stand alone node,
I mean, without the need to close the dcn through another dcn node.
This is no more possible with the actual architecture (Engineering station
plus RTAB PU412). If I try to save a parameter il LOOPFCM by mean
of the MOD Eng Display software the value remains red coloured and it is not saved
(become black and actually saved) .
Other RTAB functions need a TBOX connected to the PU412 to be completed.
I was wondering if other MOD300 users observed this behaviour and, if so,
it can be corrected, maybe setting some flags using bugs ..
Thanks a lot
We recently jumped from AdvaBuild# 3.3/4 to 3/7SP1 and which included some specific fixes for MEDIC, for example fix #1713 in AdvaBuildi 3.5 talks about inconsistency in certain fields between MEDIC and Loop FCM edits.
But I feel your problem may be more generic than this.
Are you seeing any other problems in AdvaBuild Control Builder like Sys Doc and Service Display not working, loop loads not giving you confirmation popup? If this is the case you could be looking at a windows security configuration. You could try the following:
1) Local windows policy – its policy ‘Access the computer from the network’ & added the ‘advabuild’ user account you setup.
2) Re-run securitysetup.exe as administrator (must have admin rights) and potentially it can correct problems relating to MEDIC, Control Builder and TCL Builder.
Hopefully this helps.