LLExec RTX

From Axel Public Wiki
Revision as of 14:28, 5 October 2017 by Axelpwiki (talk | contribs) (Created page with "=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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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
  • 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
  • Execute socat_LLExec.bat to allow LogicLab connections from the LAN
  • To connect with LogicLab, configure the GDB connection using your Windows IP address