LLExec RTX: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
* RTX64 must have the virtual network interface (between RTX64 and Windows) correctly configured (see notes below) | * 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) | ||
* You must have correctly installed the "AXEL64" license from IntervalZero | |||
==Downloads== | ==Downloads== | ||
| Line 21: | Line 22: | ||
==Execution== | ==Execution== | ||
* Execute '''LLExec_RTX64.bat''' to launch LLExec | * Execute '''LLExec_RTX64.bat''' to launch LLExec | ||
* Execute '''socat_LLExec.bat''' to allow LogicLab connections from the LAN | * Execute '''socat_LLExec.bat''' to allow LogicLab connections from the LAN | ||
* To stop LLExec, execute '''LLExec_shutdown.bat''' | |||
==LogicLab usage== | ==LogicLab usage== | ||
* Execute LogicLab | * Execute LogicLab | ||
* Create a new project using the '''LLExec PLC runtime (RTX64)''' target | * 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 | * Configure the GDB connection using the normal IP address of the Windows side, port 5000. This requires socat to be running; however, if LogicLab is running on the same PC with RTX, you could also connect to the IP address of the RTX side of the VirtualNIC directly | ||
==Plugins development== | ==Plugins development== | ||
| Line 38: | Line 39: | ||
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] | 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] | ||
Please remember that the two sides of the VirtualNIC must have two different IP addresses on the same subnet; if everything is working, you should be able to ping each other address. | |||
| Line 66: | Line 68: | ||
==Execution== | ==Execution== | ||
* Execute '''LLExec_RTX.bat''' to launch LLExec | * Execute '''LLExec_RTX.bat''' to launch LLExec | ||
* Execute '''socat_LLExec.bat''' to allow LogicLab connections from the LAN | * Execute '''socat_LLExec.bat''' to allow LogicLab connections from the LAN | ||
* To stop LLExec, execute '''LLExec_shutdown.bat''' | * To stop LLExec, execute '''LLExec_shutdown.bat''' | ||
| Line 73: | Line 74: | ||
* Execute LogicLab | * Execute LogicLab | ||
* Create a new project using the '''LLExec PLC runtime (RTX)''' target | * 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 | * Configure the GDB connection using the normal IP address of the Windows side, port 5000. This requires socat to be running; however, if LogicLab is running on the same PC with RTX, you could also connect to the IP address of the RTX side of the VirtualNIC directly | ||
==Plugins development== | ==Plugins development== | ||
| Line 83: | Line 84: | ||
==VirtualNIC notes== | ==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] | 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] | ||
Please remember that the two sides of the VirtualNIC must have two different IP addresses on the same subnet; if everything is working, you should be able to ping each other address. | |||
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] | 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]] | ||
Latest revision as of 16:03, 9 February 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)
- You must have correctly installed the "AXEL64" license from IntervalZero
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
- 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 (RTX64) target
- Configure the GDB connection using the normal IP address of the Windows side, port 5000. This requires socat to be running; however, if LogicLab is running on the same PC with RTX, you could also connect to the IP address of the RTX side of the VirtualNIC directly
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
Please remember that the two sides of the VirtualNIC must have two different IP addresses on the same subnet; if everything is working, you should be able to ping each other address.
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
- 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. This requires socat to be running; however, if LogicLab is running on the same PC with RTX, you could also connect to the IP address of the RTX side of the VirtualNIC directly
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
Please remember that the two sides of the VirtualNIC must have two different IP addresses on the same subnet; if everything is working, you should be able to ping each other address.
PS: as of 18/01/2018, the sample RtxTcpIp.ini is not correct: a working one can be found here