LLExec RTX: Difference between revisions

From Axel Public Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:
==Prerequisites==
==Prerequisites==
* RTX64 must be alredy correctly installed and configured on the Windows system
* RTX64 must be alredy correctly installed and configured on the Windows system
* RTX64 must have the virtual network interface (between RTX64 and Windows) correctly configured
* RTX64 must have the virtual network interface (between RTX64 and Windows) correctly configured (see notes below)
* RTX64 must have one physical network interface correctly assigned and configured (for EtherCAT master only)
* RTX64 must have one physical network interface correctly assigned and configured (for EtherCAT master only)


Line 34: Line 34:
* You have a '''LLXPlugin_EXAMPLE''' sample project, to be built with VisualStudio; it will produce a .RTDLL files, that must be inserted in the LLExec.conf file
* You have a '''LLXPlugin_EXAMPLE''' sample project, to be built with VisualStudio; it will produce a .RTDLL files, that must be inserted in the LLExec.conf file
* Please refer to '''LLExec Technical Reference''' document (available in your private customer area) for further informations
* Please refer to '''LLExec Technical Reference''' document (available in your private customer area) for further informations
==VirtualNIC notes==
To setup the VirtualNIC, see official documentation for RTX64 [https://www.intervalzero.com/library/RTX64/HTML5/Content/PROJECTS/Subsystem/RTX_Virtual_Network_Adapter.htm here]




Line 40: Line 43:
==Prerequisites==
==Prerequisites==
* RTX must be alredy correctly installed and configured on the Windows system
* RTX must be alredy correctly installed and configured on the Windows system
* RTX must have the virtual network interface (between RTX and Windows) correctly configured
* RTX must have the virtual network interface (between RTX and Windows) correctly configured (see notes below)
* RTX must have one physical network interface correctly assigned and configured (for EtherCAT master only)
* RTX must have one physical network interface correctly assigned and configured (for EtherCAT master only)


Line 77: Line 80:
* You have a '''LLXPlugin_EXAMPLE''' sample project, to be built with VisualStudio; it will produce a .RTDLL files, that must be registered and inserted in the LLExec.conf file
* You have a '''LLXPlugin_EXAMPLE''' sample project, to be built with VisualStudio; it will produce a .RTDLL files, that must be registered and inserted in the LLExec.conf file
* Please refer to '''LLExec Technical Reference''' document (available in your private customer area) for further informations
* Please refer to '''LLExec Technical Reference''' document (available in your private customer area) for further informations
==VirtualNIC notes==
To setup the VirtualNIC, see official documentation for RTX [https://www.intervalzero.com/library/RTX/WebHelp/Content/PROJECTS/Subsystem/RTX_Virtual_Network_Adapter.htm here]
PS: as of 18/01/2018, the sample RtxTcpIp.ini is not correct: a working one can be found [http://www.axelsw.it/pwiki/pub/RtxTcpIp.ini here]


[[Category:LLExec]]
[[Category:LLExec]]

Revision as of 17:37, 18 January 2018

LLExec for RTX64 (64bit) usage instructions

Prerequisites

  • RTX64 must be alredy correctly installed and configured on the Windows system
  • RTX64 must have the virtual network interface (between RTX64 and Windows) correctly configured (see notes below)
  • RTX64 must have one physical network interface correctly assigned and configured (for EtherCAT master only)

Downloads

  • Get the latest version of LogicLab Automation suite setup from Axel website (private customer area)
  • Get the latest version of LLExec (x86 Windows) setup from Axel website (private customer area)
  • Get the latest version of LLExec for RTX64 binaries from Axel website (private customer area)
  • Get the latest version of socat binaries from Axel website (private customer area)

Installation

  • Install the LogicLab Automation suite using the setup
  • Install the LLExec (x86 Windows) using the setup
  • Unzip the LLExec_x.y.z_WinRTX64.zip archive where you want
  • Get the latest version of socat binaries from Axel website
  • Unzip the socat archive where you want
  • If the IP address of the RTX64 side of the virtual network interface is different from 192.168.1.1, please edit the socat_LLExec.bat

Execution

  • Execute LLExec_RTX64.bat to launch LLExec
    • On the first execution, LLExec will save a HardwareID.txt file on the disk and quit immediately; please send this file to support@axelsw.it and you will receive back a license file named LLExecRTX.key, to be placed in the same folder
  • Execute socat_LLExec.bat to allow LogicLab connections from the LAN

LogicLab usage

  • Execute LogicLab
  • Create a new project using the LLExec PLC runtime (RTX64) target
  • Configure the GDB connection using the normal IP address of the Windows side, port 5000

Plugins development

  • Get the latest version of PluginHeaders binaries from Axel website (private customer area)
  • Extract the contents of the archive where you want
  • You have a LLXPlugin_EXAMPLE sample project, to be built with VisualStudio; it will produce a .RTDLL files, that must be inserted in the LLExec.conf file
  • Please refer to LLExec Technical Reference document (available in your private customer area) for further informations

VirtualNIC notes

To setup the VirtualNIC, see official documentation for RTX64 here


LLExec for RTX (32bit) usage instructions

Prerequisites

  • RTX must be alredy correctly installed and configured on the Windows system
  • RTX must have the virtual network interface (between RTX and Windows) correctly configured (see notes below)
  • RTX must have one physical network interface correctly assigned and configured (for EtherCAT master only)

Downloads

  • Get the latest version of LogicLab Automation suite setup from Axel website (public download area)
  • Get the latest version of LLExec (x86 Windows) setup from Axel website (public download area)
  • Get the latest version of LLExec for RTX binaries from Axel website (private customer area)
  • Get the latest version of socat binaries from Axel website (private customer area)

Installation

  • Install the LogicLab Automation suite using the setup
  • Install the LLExec (x86 Windows) using the setup
  • Unzip the LLExec archive where you want
  • If you DO NOT NEED EtherCAT master functionality:
    • edit RegisterRtxDll.bat and remove the registration of LLXPlugin_EtherCAT_RTX.rtdll and RTXFilterDriver.rtdll
    • edit LLExec_RTX.conf and remove the line with LLXPlugin_EtherCAT_RTX.rtdll
  • Execute RegisterRtxDll.bat to register the .rtdll components in the system
  • Get the latest version of socat binaries from Axel website
  • Unzip the socat archive where you want
  • If the IP address of the RTX side of the virtual network interface is different from 192.168.1.1, please edit the socat_LLExec.bat

Execution

  • Execute LLExec_RTX.bat to launch LLExec
    • (RTX2016 only) On the first execution, LLExec will save a HardwareID.txt file on the disk and quit immediately; please send this file to support@axelsw.it and you will receive back a license file named LLExecRTX.key, to be placed in the same folder
  • Execute socat_LLExec.bat to allow LogicLab connections from the LAN
  • To stop LLExec, execute LLExec_shutdown.bat

LogicLab usage

  • Execute LogicLab
  • Create a new project using the LLExec PLC runtime (RTX) target
  • Configure the GDB connection using the normal IP address of the Windows side, port 5000

Plugins development

  • Get the latest version of PluginHeaders binaries from Axel website (private customer area)
  • Extract the contents of the archive where you want
  • You have a LLXPlugin_EXAMPLE sample project, to be built with VisualStudio; it will produce a .RTDLL files, that must be registered and inserted in the LLExec.conf file
  • Please refer to LLExec Technical Reference document (available in your private customer area) for further informations

VirtualNIC notes

To setup the VirtualNIC, see official documentation for RTX here

PS: as of 18/01/2018, the sample RtxTcpIp.ini is not correct: a working one can be found here