Brian_73

Verfasste Forenbeiträge

  • Als Antwort auf: Alarm dispatcher using Moxa Oncell G3150A-LTE

    11 März 2020 um 3:43 pm #35880
    Brian_73
    Teilnehmer

    Hi,
    I have never used a dual sim modem, but it could be an idea in a redundant application.
    In the past I used 2 modems also because the AD was not inserted in the redundant processes of Movicon 11. Now with the Movicon.NExT the AD follows the redundancy settings configured in the I/O Data Server-
    I had also looked at the moxa model you posted in the previous link.
    I thought it was interesting, but what kind of errors are coming from this device?
    A Dual-sim Modem I think it handles all the sim management inside it and should be transparent anyway

    All you have to do is give Movicon’s dispatcher the baud rate and the COM…the initialization string …nothing else …

    For everything else i think the Dispatcher of Movicon knows nothing about the management of the dual sim , it does not send specific commands for the SIM…

    Regards
    Brian

  • Als Antwort auf: Connectivity Status

    11 März 2020 um 3:31 pm #35879
    Brian_73
    Teilnehmer

    Hi Praveenraj.K
    I had the same problem with the OPC UA Client driver and Movicon.NExT 3.4.268 , I contacted the Progea tech support and they told me that the problem is known and it will be fixed with the next release in April.
    I’m waiting for the new release, as alternative method I think you need a manual whatchdog logic.

    Regards
    Brian

  • Als Antwort auf: Tag Import fromOPC Driver

    11 März 2020 um 3:16 pm #35878
    Brian_73
    Teilnehmer

    Hi Dhakshin,
    Simply browse and select the variables….you don’t have to import one by one ….
    I think you’re missing a few steps…

    Which version of the software are you using?

    Regards
    Brian

  • Als Antwort auf: Accessing Arrays in the tag list from scripts

    11 März 2020 um 3:11 pm #35876
    Brian_73
    Teilnehmer

    Hi Hans ,
    I found this information on the help :

    Array Variables

    In cases where Array variable types are used, each array element can be accessed by specifying its number between rounded brackets by using direct tag access syntax. For example, let’s suppose that we have created the ‚var_01‘ array tag type in the server’s address space, in order to access the tag’s elements we would use the following syntax:

    Var_01(0) = 1

    Var_01(1) = 2

    However, direct syntaxes can only be used in script on the Client side and not in that of the Server side.

    Despite this, it is also possible to access Array elements using script functions with the following syntax:

    Script on Client side:

    ScriptDocument.GetVariableValue(„Var_01“)(0) = 1

    ScriptDocument.GetVariableValue(„Var_01“)(1) = 2

    Script on Server side:

    ServerScriptManager.GetTag(„Var_01“).Value(0) = 1

    ServerScriptManager.GetTag(„Var_01“).Value(1) = 2

    However, please note that even though the script functions are used to write an Array element, it will not be notified to the Client which will continue showing the old value. In order for the Server to notify the Client of this change, the entire Array variable will have to be set. Therefore, you will need to use a temporary variable within the script as in the following example where “Folder1\Tag_ArrayFloat” is the Server’s Array variable:

    ‚#Language „WWB.NET“

    Option Explicit

    Sub Main Handles .Main

    Dim myArr() As Single

    Dim nLen As Integer

    Dim iCounter As Integer

    nLen = UBound(Folder1_Tag_ArrayFloat)

    ReDim myArr(nLen)

    myArr = Folder1_Tag_ArrayFloat

    For iCounter = LBound(myArr) To UBound(myArr)

    myArr(iCounter) = myArr(iCounter) + 1

    Next iCounter

    here is the source where i took this info:

    http://www.movicon.info/HelpNExT3.4/269/en-US/PlatformNext.htm#t=mergedProjects%2FScripting%20VB_DOCNET%2FLanguages%2FScriptResources%2FProjectBasicScript%2FBasic_Script_Variables.htm&rhsearch=array&rhhlterm=array&rhsyns=%20

    I think you’re using the wrong syntax. I hope I can help.

    Regards
    Brian

    • Diese Antwort wurde geändert vor 2 Wochen, 3 Tagen von Brian_73.
  • Als Antwort auf: Runtime User Management | Audit Trail

    6 Februar 2020 um 11:24 am #35516
    Brian_73
    Teilnehmer

    Hi Redrod,
    Normally the „Edit runtime user“ command is a password protected option inside the application, not available for „normal“ users.
    In the system log you will also have the info that the file „.rtusers“ extension is modified.
    With these 2 info you know who and when changes in the application the list of runtime users. Then the other data like teh user name ect are sesitive data i think are not exposed by-design. Anyway these info are present inside the „.rtusers“ file and using a tool that compares these files you know the which user was added or deleted.

    BR
    Brian

  • Als Antwort auf: Installazione da riga di comando

    6 Februar 2020 um 11:06 am #35515
    Brian_73
    Teilnehmer

    Hi Fabio,
    I found these info in the help , Introduction > Installing and running application

    Silent Installation

    Movicon can be installed without user interface (silent mode) by using the following command line:

    path\Setup.exe /s /l1033 /v/qn

    where:

    „path“ = relative or absolute path where all the Movicon setu files are found (setup.exe, movicon11.4.msi, etc.)

    /s = silent mode

    /l = Installation language. 1033 for English (default), 1031 for German, 1036 for French, 1040 for Italian and 2052 for Chinese

    /v/qn = exclusion of user interface

    if you wish to specify the installation directory, eg. C:\MyDir, use:

    path\Setup.exe /s /l1033 /v“/qn INSTALLDIR=C:\MyDir“

    if you wish to install the runtime module only, write:

    path\Setup.exe /s /l1033 /v“/qn INSTALLDIR=C:\MyDir ADDLOCAL=MoviconRun“

    When installing MoviconBA, the runtime only installation string is:

    setup.exe /s /v“/qn INSTALLDIR=c:\temp\progea\movba ADDLOCAL=BA_MoviconRun“

    or it you which to add two Features, the syntas for the „ADDLOCAL“ parameter is:

    ADDLOCAL=FeatureA,FeatureB“

    Make sure you don’t insert spaces one feature and the other one and the Case Senstive syntax.

    If you wish to indivate which component to install, e.g. the „Modbus“ Driver, the „ModbusTCP“ Driver and the components for the Software License, the command line is as follows:

    path\Setup.exe /l1033 /v“/qn INSTALLDIR=C:\Movicon

    ADDLOCAL=MoviconRun,Modbus,ModbusTcpip,LicenseComponents,SGLockDrivers,

    CripKeyDrivers“

    or

    setup.exe /s /v“/qn ADDLOCAL=BA_MoviconRun“

    This works in WindowsXP, but the UAC in Windows 10/8/7 will intervene asking for administrator installation rights. In this case you can use the following command line (but a password is needed):

    runas /user:administrator „c:\temp\setup\setup.exe /s /l1040 /v\“/qn INSTALLDIR=C:\MyDir ADDLOCAL=MoviconRun\““

    Considering that:

    1) the complete path where setup.exe file is found is required

    2) all that follows after the user name must be written between double quotation marks. Since the topic of the command line contains double quotation marks, the “ character must be replaced with \“.

    This procedure works only if the user is a built-in pc administrator (user = administrator) and the UAC will intervene for other Administrator level users as explained in the microsoft document:

    http://msdn.microsoft.com/en-us/library/aa511445.aspx

    For other cases you will need to disable the UAC in order to carry out the installation procedure.

    BR

    Brian

  • Als Antwort auf: Minimizing Pop-Up

    6 Februar 2020 um 11:03 am #35514
    Brian_73
    Teilnehmer

    Hi Angel,
    I had the same issue in the past with Movicon 11.6.
    I asked at the Progea technical support and they told me it is behavior „bydesign“; when you use popup windows, you cannot mange this functions. This also because the „focus“ remains in only one popup layer …you cannot operate outside.
    I solved by managing additional opening closing buttons inside the popup windows.

    BR
    Brian

  • Als Antwort auf: TAGs in BadTimeout after net fail

    6 Februar 2020 um 10:27 am #35513
    Brian_73
    Teilnehmer

    Hi,
    You can view the driver logs directly by inserting the toolbox object Alarm Viewers > Historical Log Viewer.
    You can filter driver errors in the object properties , Filter Event Type > Drivers

    In addition all these information are automatically recorded in the SQL DB in the project table UFUAAuditLogItem.

    I hope to be of help!

    BR

    Brian

  • Als Antwort auf: Runtime User Management | Audit Trail

    3 Februar 2020 um 5:33 pm #35503
    Brian_73
    Teilnehmer

    Hi Redrod,

    It is very easy, You have to :

    – Enable the Password Management in the Users and User Groups resource of the project
    -In General > Advanced Enable also Runtime Users
    -Then you can add a button in a screen with configured the predefined user command „Edit Users“

    All the activities is traced in the project logs.

    BR
    Brian

  • Als Antwort auf: TAGs in BadTimeout after net fail

    3 Februar 2020 um 5:26 pm #35502
    Brian_73
    Teilnehmer

    Hi
    Any error in the logs? I’d say a detailed analysis starts here.
    It could be a timeout issue , timeout must be configured in a good way when using a gateway. I mean try to set an higher timeout in the GPRS gateway (e.g. 10seconds) and higher in the Movicon driver (e.g. 12 seconds) .

    BR
    Brian

  • Als Antwort auf: Report Parameters

    3 Januar 2020 um 10:19 am #35267
    Brian_73
    Teilnehmer

    Hi WANGRENZHI,
    Normally I create the connection to the DB directly in the report properties (execution , reader item source reference).
    If you do it later in the report designer you have to create a data source in a custom way (small arrow on the top left of teh report)
    BR
    Brian

  • Als Antwort auf: OPC client DA

    3 Januar 2020 um 10:12 am #35265
    Brian_73
    Teilnehmer

    Hi Marco,
    Movicon.NExT only implements the „new“ OPC UA technologies.
    Have you verified if the FANUC OPC SERVER can expose on OPC UA?
    If you still have to connect an old OPC DA Server I think is better use Movicon 11 (or you can use Movicon11 as a bridge to move the data to Movicon.NExT).
    BR
    Brian

  • Als Antwort auf: XtraReport cannot connect to SQL database

    3 Januar 2020 um 10:07 am #35264
    Brian_73
    Teilnehmer

    Hi WANGRENZHI,
    Normally I create the connection to the DB directly in the report properties (execution , reader item source reference).
    If you do it later in the report designer you have to create a data source in a custom way (small arrow on the top left of teh report)
    BR
    Brian

  • Als Antwort auf: Proprietà "Text" esploratore animazioni oggetto

    3 Dezember 2019 um 10:29 am #35074
    Brian_73
    Teilnehmer

    Hi Daniele,
    I think you have to use the „Animated Text“ object present in the Movicon.NExT toolbox „Texts“ folder.

    An example is also available in the pre-installed demos :

    C:\Users\Public\Documents\Progea\Movicon.NExT\ExampleProjects 3.4\GraphicAnimations

    I hope to be of help!

    Ciao
    Brian

  • Als Antwort auf: Open PopUp Screen On Hoverover

    7 November 2019 um 10:38 am #34958
    Brian_73
    Teilnehmer

    Hi Praveenraj

    Yes, You can do this easily with the Hot Region object present inside the toolbox.

    Hot Region properties > Button Behaviour > Click Mode

    Select „Hover“

    Then you can configure the command to open the popup as usual in the classical command list.

    I hope I can help.

    Regards
    Brian