List of Contributions

Hi Eduard, hi Scott, Thanks Eduard - your description is correct, and there are no issues with that setup. To clarify and align the two points of view: The Stratix 4300 LAN interface itself does not perform inter‑VLAN routing. If VLANs are used (for example VLAN 26, VLAN 27, etc.), inter‑VLAN ...

Hi Scott, Great question, this is a common point of confusion. The LAN interface on the Stratix 4300 can be configured with one or more IP addresses, but these IPs are not assigned to the devices connected to the port (PLCs, HMIs, etc.). They are IP addresses that the Stratix itself uses on its LAN ...

Hi @AutomateSHANE and @Retzlaff, sorry for the late reply. The Stratix 4300 (the version with the cellular option) can send and receive SMS to manage the Digital Input, allowing the device to be set online or offline in the FTRA Manager domain. This is the only way to manage I/Os remotely, and supporting ...

Hi @AutomateSHANE and @Miguel Torres Jr, a Stratix 4300 for every controller cab be a solution but a little-bit overkilling imho, as explained below the "real solution" is using the embedded Firewall policies. Sub-devices feature, instead, is just an "easy way" to automate the access to the services ...

Hi @Retzlaff, good question! You don't need to create sub-devices to restrict access. The right way is to use Firewall Policies in FactoryTalk Remote Access. This lets you define rules by IP address and assign them to specific users or groups, so each vendor only sees their own PLC. Here's how ...

Hi, OptixPanel embeds the FactoryTalk Remote Access runtime and starting from 13.5 release (that together comes with firmware upgrade 4.0.2.x) you can use FT Remote Access tools to connect to the OptixPanel via Local Connection, with same capabilities of VNC (screen mirroring) and much more like File ...