The Industrial Wi-Fi Shop Podcast

The Industrial Wi-Fi Shop Podcast – Ep. 25 Industrial Wireless Clients

1 h 31 min · 30. mar. 2026
episode The Industrial Wi-Fi Shop Podcast – Ep. 25 Industrial Wireless Clients cover

Beskrivelse

Upcoming Events! * Upcoming Wi-Co Events * Be sure to check https://wi-co.org/ [https://wi-co.org/] Don’t forget to check out our new document library with free valuable downloadable content! * Miliwatt to dBm  conversion table * Wireless IoT reference charts for types and security * Best practice white papers to help you stay on your game Why specialized industrial wireless clients? * Wireless clients are the bridge between the past and the present. The vast majority of industrial devices, PLCs, drives, sensors, HMIs, and controllers, are engineered for deterministic performance and long service life, not wireless connectivity. They ship with Ethernet ports, not radios. Industrial wireless client radios exist specifically to give these wired-by-design devices a wireless presence without requiring any changes to the device itself or the control program running inside it. * Freedom of movement changes what’s possible on the plant floor. Conveyors, AGVs, robotic arms, transfer carts, and overhead cranes all move, and running Ethernet cable to something that moves is either impractical, expensive, or eventually guaranteed to fail. Wireless clients eliminate the cable entirely, giving mobile and rotating machinery reliable network connectivity that moves with the equipment. * Wireless clients enable the Industrial Internet of Things (IIoT) without a forklift upgrade. Adding wireless clients to existing field devices means real-time data, cycle counts, temperatures, fault codes, production rates, can flow to SCADA systems, historians, and cloud analytics platforms without replacing equipment that still has years of useful life left. The radio does the heavy lifting; the device just keeps doing its job. * In hazardous, remote, or physically inaccessible locations, wireless isn’t a convenience,  it’s the only option. Tank farms, offshore platforms, grain elevators, and mining operations all present environments where pulling cable is either dangerous, cost-prohibitive, or physically impossible. Industrial-grade wireless clients, rated for wide temperature ranges, vibration, and hazardous area classifications, make instrumentation and control possible in places where no wire will ever go. Phoenix Contact 1021 Industrial Wireless Client Modes: * In FTB mode, the client radio acts as a wireless bridge allowing multiple wired end devices to communicate transparently via Layer 2 or Layer 3 communication. FTB is used when wirelessly connecting to a Phoenix Contact WLAN module configured as an access point. * In SCB mode, data is transmitted transparently on Layer 2. Only the device whose MAC address is entered for the radio can be accessed via WLAN, and only one wired device may be connected. * In MCB mode, the Phoenix radio uses a Layer 2 NAT function when communicating to the access point, allowing multiple wired clients to communicate over the wireless connection. All wired clients behind the device are transmitted with the MAC address of the radio, the number of wired clients is unlimited. * Client (NAT) breaks into two sub-modes: * 1:1 NAT, where each LAN device is allocated an IP address from the higher-level network so it can be reached from the WAN * IP masquerading, where the NAT device acts as a proxy and all LAN devices communicate externally using only the NAT device’s own WAN address — with TCP/UDP ports used to differentiate between devices. This is useful when you have duplicate IP address spaces across identical machine cells. * Client (VXLAN), the fully transparent bridge and VxLAN (Virtual Extensible LAN) enable transparent PROFINET and PROFIsafe communication, which is critical in automation networks. This mode is documented in relation to the WLAN 1000 client family pairing with the new WLAN 2300 access points. It’s standards-based (RFC 7348), so it isn’t locked to Phoenix Contact infrastructure the way FTB is. What is VxLAN? * VxLAN wraps a complete Ethernet frame inside a regular IP/UDP packet so it can travel anywhere IP travels, then unwraps it at the other end, making two distant devices believe they’re sitting on the same local wire. Why it matters for industrial wireless specifically: * Protocols like PROFINET and PROFIsafe are “Layer 2 snobs”, they expect to see the real MAC address of the device they’re talking to, unmodified, end to end. Modes like MCB swap out MAC addresses behind the scenes, which breaks PROFINET. VxLAN mode preserves everything inside the tunnel,  the receiving device opens it up and sees the exact original Ethernet frame, MAC address intact, as if the wireless hop never happened. VXLAN vs FTB — what’s the difference? Both achieve true Layer 2 transparency, but: * FTB is Phoenix Contact proprietary and requires a Phoenix Contact AP on the infrastructure side * VXLAN is standards-based (IETF RFC 7348) and works with any AP or controller that supports VXLAN termination, including the Phoenix Contact WLAN 2300 series access points [https://industrialwifishop.com/wp-content/uploads/2026/03/image-1.png?w=1024] ProSoft Technologies RLX2-IHNF-A, Four Operational Modes Explained * Master – The Master is the anchor and root of the entire RLX2 wireless network. Every other radio in the network, Repeaters, Bridging Clients, and Clients, ultimately connects back to the Master, either directly or through a chain of Repeaters. There is typically one Master per wireless network, though multiple Masters can coexist without special programming for redundancy. * Repeater – The Repeater is the workhorse of the ProSoft network. It connects wirelessly to a Master (or another Repeater), extends the wireless coverage area, and simultaneously allows additional radios to connect through it. It is also the factory default shipping configuration, every RLX2 radio ships as a Repeater out of the box, ready to link to whatever Master it finds. * Bridging Client – Bridging Client is the mode used when you want to connect multiple wired Ethernet devices through a single RLX2 radio to a third-party 802.11 access point, not a ProSoft Master. Think of it as the “multi-device adapter” for foreign Wi-Fi infrastructure. * Bridging Client mode is specifically designed for environments where the access point is not a ProSoft radio. It uses standard 802.11 association and works with the AP’s existing SSID and security settings. Note that some third-party AP controllers (notably Cisco WLC systems) may require additional configuration to allow multiple MAC addresses over a single wireless association — the same consideration that applies to MCB mode in other industrial radio families. * Client – Client mode is the simplest connection mode in the RLX2 lineup — one radio, one wired device, one wireless connection to a third-party access point. It’s the “single device adapter” for foreign Wi-Fi infrastructure. * The radio can be configured in two sub-modes: * Auto, the radio automatically detects the MAC address of whatever is plugged into its Ethernet port and uses it for the wireless association. Easy, fast, and appropriate for most single-device setups * Specify, the operator manually enters the MAC address of the target device. The manual notes this is only necessary for devices that do not send unsolicited Ethernet packets — meaning the device is passive and doesn’t announce itself. ProSoft’s guidance is to try Auto first and only use Specify if Auto doesn’t work [https://industrialwifishop.com/wp-content/uploads/2026/03/image.png?w=1024] As you probably know, Scott and Jeremy work with different application types for the most part. Jeremy primarily touches mobility applications with mixed/client and infrastructure. Jeremy generally works with whatever infrastructure the end customer has for enterprise and occasionally gets to build both ends of the WLAN. Jeremy’s team used to use the Aruba501, which had a lot going for it. RSSI log, simple interface, remote packet capture, exportable logs.. <- You could do a lot to troubleshoot these devices. I was just on a call with a vendor and it is both nice and disheartening to hear that telemetry and data can be hidden because the “casual end customer” will generate more nonsense complaints if the nerd knobs are exposed. Sometimes you have to get into the weeds, limiting MCS, NAT/IP Masquerading to work around passive client issues. What is a Passive Client? A passive client is a device that does not actively participate in normal network communication unless it is polled or queried. In practical terms, a passive client: * Does not initiate traffic on its own * May not send ARP, DHCP renewals, or periodic data * Only responds when another device communicates with it Examples in industrial environments * PLCs waiting for control traffic * I/O devices that only respond to cyclic polling * Sensors that do not generate unsolicited traffic NAT, specifically IP masquerading, helps by making multiple downstream devices appear as a single active client to the wireless network. The radio handles all communication on behalf of the devices behind it, so the infrastructure only needs to track one MAC and IP address. This keeps passive devices reachable even if they never transmit, but the tradeoff is that Layer 2 transparency is lost, which can break protocols that rely on seeing the original MAC addresses. So this is one of the main reasons we lean on the Siemens hardware. Siemens Siemens SCALANCE typical models: W734 – WiFi 4 and WUM763/766 The WiFi4 stuff is well established and has tons of features. * Dynamic antenna selection * NAT/IP Masquerading * Remote capture on WLAN interface * Available APs <- helps identify interferers * Signal Recorder Piecewise site survey, lots of KPIs and if you have Siemens infrastructure you can get both sides of the conversation. * Detailed Logging * Config Plugs * iPCF * Force Roam on IP Down Most of this is still present in the WiFi6 hardware. PoE capability is not present in the WUM763. Siemens cabinet based models are IP30 The hardened units are IP65, and typically use some variation of M12 connector. D-coded or X-coded 8 pin. 1. Transparent Bridge (Default / Standard Mode) * True Layer 2 bridge * Passes all MAC addresses unchanged * Supports: * PROFINET * PROFIsafe * Multiple devices behind the client are fully visible to the network This is the primary and most important mode for all of these clients. 2. Layer 2 Tunnel Mode (Used with IPCF) * Required when running IPCF (deterministic wireless) * Encapsulates Ethernet frames for controlled delivery * Maintains full Layer 2 transparency * Used specifically for: * Real-time industrial communication * Deterministic cyclic traffic Siemens explicitly calls out using “Layer 2 Tunnel” MAC mode with IPCF  3. Standard Wi-Fi (DCF) vs IPCF Operation This is a major behavioral “mode” difference: DCF (DEFAULT WI-FI) * Standard contention-based Wi-Fi * Works with any infrastructure * Non-deterministic IPCF Mode * Scheduled medium access (deterministic) * AP controls airtime * Used for: * Motion control * Real-time automation Important: * IPCF and standard Wi-Fi cannot be mixed in the same cell  Aunex Aunex wireless clients are designed to be flexible and infrastructure-agnostic. They behave more like traditional Wi-Fi clients with options for bridging or NAT, making them easy to integrate into mixed networks. The tradeoff is that they rely on standard Wi-Fi behavior, so they don’t provide the same level of deterministic performance or deep diagnostics that more specialized industrial platforms offer. They have 6E Clients. Core Design Approach MODAS clients follow a standard 802.11 client model and are designed to work with a wide range of third-party access points and controllers. They support: * Single-device client operation * Multi-device bridging * Layer 3/NAT-based connectivity The focus is on adaptability rather than tightly controlled, deterministic wireless behavior. Networking Behavior Layer 2 Bridging * Can pass Ethernet frames between wired devices and the WLAN * May support multiple MAC addresses depending on configuration and infrastructure * Works best in networks that allow multi-MAC clients NAT / Routing Modes * Supports Layer 3 NAT / IP masquerading * Useful for: * Handling duplicate IP address spaces * Reducing MAC scaling challenges on controllers * Simplifying machine-level network integration MAC Handling * Can operate as: * Transparent bridge (when supported) * Single visible client using NAT Wireless Capabilities * Operates using standard Wi-Fi (DCF) * Supports common enterprise features: * WPA2/WPA3 * Roaming (model dependent) * No deterministic scheduling mechanism like IPCF Legacy Interface Flexibility (Key Differentiator) One area where MODAS clients stand out is support for legacy industrial interfaces, including: * RS-232 / RS-485 serial connectivity * Serial-to-IP conversion (serial tunneling) * Ability to transport legacy protocols over Wi-Fi Why this matters * Many industrial systems still rely on serial communications * MODAS devices can act as a bridge between legacy serial equipment and modern IP networks * Enables: * Retrofit of older machines without replacing hardware * Wireless connectivity for devices that were never designed for Ethernet Typical behavior * Serial data is encapsulated into IP packets * Transported over Wi-Fi * Reconstructed at the receiving end This allows legacy devices to function across a wireless link as if they were locally connected. Diagnostics and Management * Provides standard industrial diagnostics: * RSSI / signal strength * Link status * Throughput and error counters * Typically lacks deep RF time-series logging found in more specialized platforms If you would like to connect with Scott or learn more about his employer, Global Process Automation (GPA), then check the following: Scott McNeil – https://www.linkedin.com/in/americanmcneil/ [https://www.linkedin.com/in/americanmcneil/]  GPA – https://www.global-business.net/ [https://www.global-business.net/]  If you would like to connect with Jeremy or learn more about his employer, Prism Systems Inc, then check the following: Jeremy Baker – https://www.linkedin.com/in/jeremyabaker/ [https://www.linkedin.com/in/jeremyabaker/]  Prism Systems Inc – https://www.prismsystems.com/ [https://www.prismsystems.com/]

Kommentarer

0

Vær den første til at kommentere

Tilmeld dig nu og bliv en del af The Industrial Wi-Fi Shop Podcast-fællesskabet!

Kom i gang

1 måned kun 9 kr.

Derefter 99 kr. / måned · Opsig når som helst

  • Podcasts kun på Podimo
  • 20 lydbogstimer pr. måned
  • Gratis podcasts

Alle episoder

29 episoder

episode The Industrial Wi-Fi Shop Podcast – Ep. 27 Invisible Design Practices cover

The Industrial Wi-Fi Shop Podcast – Ep. 27 Invisible Design Practices

Upcoming Events! * Upcoming Wi-Co Events * Be sure to check https://wi-co.org/ [https://wi-co.org/] Don’t forget to check out our new document library with free valuable downloadable content! * Miliwatt to dBm  conversion table * Wireless IoT reference charts for types and security * Best practice white papers to help you stay on your game On with Episode 27!! Every successful industrial wireless network has one thing in common, and it isn’t just great RF design. Behind every reliable deployment is a foundation of thorough documentation, consistent layouts, and disciplined engineering habits that often go unnoticed but make all the difference when it’s time to troubleshoot, expand, or hand the project off to someone else.  * Wireless Designs Don’t Fail… Documentation Does * One of the biggest reasons wireless projects become expensive isn’t RF coverage—it’s that nobody knows what was actually installed. * Missing AP naming standards * No cable labeling * Unknown switch ports * Missing VLAN documentation * No IP address inventory * Nobody knows why Channel 44 was selected * The Million-Dollar Visio * Real documentation includes: * Fiber routes * Industrial switches * Patch panels * Wireless backhaul * Control cabinets * Antenna locations * Elevations * Cable lengths * Redundant paths * The Hidden Cost of “Future Me Will Remember” * Every engineer has done this. “I’ll remember why I changed that.” * Three years later… Nobody remembers. * Examples: * Static routes * QoS changes * Radio power adjustments * Disabled data rates * DFS exclusions * RRM disabled * CurWB channel selections * If there isn’t a note… It effectively never happened * Pictures Are Documentation * Take pictures of EVERYTHING * Examples: * Cabinet before wiring * Cabinet after wiring * Antenna mounting * Cable routing * Patch panels * Fiber trays * Grounding * Pole installations * Control room racks * Phones have become one of the best engineering tools. * Build Documentation While You’re Walking * Instead of: * Survey —> Finish Project —> Spend 3 days documenting * Try to document continuously * Voice notes * Tablet/phone notes * OneNote * Hamina notes * Photos * GPS pins * Documentation should happen during deployment whenever possible * Naming Things Is Hard… Until You Have Standards * Everyone eventually invents names like: * AP-East * AP-East-2 * AP-East-New * AP-East-New-Final * AP-East-Final2 * Instead, develop standardized naming conventions. Examples to include in names could be: * Building * Area * Floor * Cabinet * Function * Same applies to: * Switches * Controllers * Fiber and copper patch panels * Consistency matters more than creativity. * Standard Deliverables Every Wireless Project Should Include * Create a checklist. For example: * RF heatmaps * Predictive models * Final validation surveys * Spectrum captures * Switch configs (where applicable) * AP configs * Firmware versions * IP & VLAN documentation * SSIDs * Authentication methods * Full devices inventory / BoM * Mounting details * Photos * Backup configs * Habits that save projects * Not technical skills… Habits. Examples include: * Label every cable * Save configs before changes * Export controller backups * Verify drawings before leaving site * Document assumptions * Keep changelogs * Date every document * The “Invisible Design” * Customers notice: * Fast Wi-Fi * Roaming * Coverage * They never notice: * Naming conventions * Documentation * Labels * Change logs * Asset tracking * Configuration standards * Drawing quality * Yet those invisible things are often what make the network maintainable. “Good wireless is visible on Day One. Great engineering is invisible for the next five years.” If you would like to connect with Trae or learn more about his employer, Prism Systems Inc, then check the following: Trae Rushing – https://www.linkedin.com/in/trae-rushing-7874a78a/ [https://www.linkedin.com/in/trae-rushing-7874a78a/]  Prism Systems Inc – https://www.prismsystems.com/ [https://www.prismsystems.com/]   If you would like to connect with Scott or learn more about his employer, Global Process Automation (GPA), then check the following: Scott McNeil – https://www.linkedin.com/in/americanmcneil/ [https://www.linkedin.com/in/americanmcneil/]  GPA – https://www.global-business.net/ [https://www.global-business.net/]  If you would like to connect with Jeremy or learn more about his employer, Prism Systems Inc, then check the following: Jeremy Baker – https://www.linkedin.com/in/jeremyabaker/ [https://www.linkedin.com/in/jeremyabaker/]  Prism Systems Inc – https://www.prismsystems.com/ [https://www.prismsystems.com/]

20. juli 20261 h 21 min
episode The Industrial Wi-Fi Shop Podcast – Ep. 26 Industrial Wireless Challenges Round Table cover

The Industrial Wi-Fi Shop Podcast – Ep. 26 Industrial Wireless Challenges Round Table

In this round table episode of the Industrial Wi-Fi Shop Podcast, Scott, Jeremy, Justin, and Troy dig into the real-world challenges that come with designing, troubleshooting, and securing wireless networks in industrial environments. The discussion covers the difference between industrial Wi-Fi and enterprise Wi-Fi, how harsh plant conditions affect wireless performance, why OT priorities differ from IT priorities, and where newer technologies like Wi-Fi 6E, Wi-Fi 7, private LTE, and Wi-Fi HaLow fit into the picture. Industrial wireless is rarely a one-size-fits-all problem. In manufacturing and other OT settings, teams have to think about uptime, reliability, roaming behavior, security, physical access, antenna placement, coverage, capacity, and the long-term maintainability of the system. This episode focuses on those practical realities and highlights why wireless in the plant is often more about dependable delivery than raw throughput. UPCOMING EVENTS Be sure to check out upcoming Wi-Co events at wi-co.org [https://wi-co.org/]. We also encourage you to visit our document library, where you’ll find free downloadable resources, including: * Miliwatt to dBm conversion table. * Wireless IoT reference charts for types and security. * Best-practice white papers designed to help you stay current. TOPICS COVERED This episode was built as a round table discussion around 11 core topic areas: 1. RF IN HARSH ENVIRONMENTS How heat, dust, humidity, metal, vibration, and washdown conditions affect wireless design and long-term reliability. 2. INDUSTRIAL WI-FI VS. ENTERPRISE WI-FI Where the design rules diverge, what enterprise teams often miss, and what industrial sites actually need from wireless. 3. RF INTERFERENCE AND COEXISTENCE How to deal with noise from motors, drives, arc welders, VFDs, and other radios in crowded plant environments. 4. ASSESSMENT AND TROUBLESHOOTING IN OT What a good wireless site survey looks like in a factory, what tools matter most, and how troubleshooting differs from office networks. 5. MOBILITY AND ROAMING Best practices for handhelds, AGVs, AMRs, forklifts, mobile HMIs, and other devices that depend on seamless roaming. 6. COVERAGE VS. CAPACITY When the issue is truly signal reach versus when it is client density, airtime contention, or application behavior. 7. SECURITY IN INDUSTRIAL WIRELESS How to balance security requirements with uptime, device constraints, legacy systems, and operational practicality. 8. WIRELESS FOR MACHINE CONNECTIVITY Where wireless makes sense for PLCs, I/O, sensors, and control-adjacent applications, and where it still creates too much risk. 9. DESIGNING FOR UPTIME AND RESILIENCE Redundancy, failover, mesh vs. infrastructure, backhaul options, and what “good enough” looks like in production environments. 10. EMERGING TECHNOLOGIES AND WHAT’S REAL Wi-Fi 6, 6E, and 7, private LTE/5G, LoRaWAN, Wi-Fi HaLow, and how to evaluate which technologies are actually useful on the plant floor. 11. ANTENNA SELECTION AND THIRD-PARTY OPTIONS What to do when you don’t have a compatible antenna available that meets your application needs. GUEST INTRODUCTIONS TROY MARTIN Troy brings deep experience across a wide range of industrial environments, including pulp and paper, nuclear, oil and gas pipelines, and pharmaceuticals. His background includes Wi-Fi design tools, scanning and testing tools, mesh deployments, point-to-point links, camera backhaul, mustering solutions, and wireless sensor backhaul. Connect with Troy on LinkedIn: Troy Martin [https://www.linkedin.com/in/labguy/] JUSTIN SHADE Justin has spent two decades with Phoenix Contact and works across wireless and automation-related challenges. His perspective adds practical insight into industrial deployments, product development, and the realities of supporting customers in the field. Connect with Justin on LinkedIn: Justin Shade [https://www.linkedin.com/in/justin-shade-a44817b/] Phoenix Contact: phoenixcontact.com [https://www.phoenixcontact.com/en-us/] SCOTT MCNEIL Scott brings real-world industrial wireless and OT networking experience, including assessments, deployments, security concerns, and design tradeoffs in challenging environments. Connect with Scott on LinkedIn: Scott McNeil [https://www.linkedin.com/in/americanmcneil/] GPA: global-business.net [https://www.global-business.net/] JEREMY BAKER Jeremy contributes practical insight from the engineering and deployment side, especially around wireless design choices, emerging technologies, and plant-floor realities. Connect with Jeremy on LinkedIn: Jeremy Baker [https://www.linkedin.com/in/jeremyabaker/] Prism Systems Inc: prismsystems.com [https://www.prismsystems.com/] WHY INDUSTRIAL WIRELESS IS DIFFERENT One of the biggest themes in this episode is that industrial wireless cannot be treated like ordinary enterprise Wi-Fi. In OT environments, availability often matters more than confidentiality, because a missed message can affect a process, a machine, or even worker safety. That means reliability, determinism, and resilience often take priority over designs that would be perfectly acceptable in an office network. The panel also explains why many industrial sites still rely on flat networks, why security upgrades can be difficult to implement without downtime, and why wireless must often be evaluated on a case-by-case basis. In many environments, the challenge is not whether wireless can work in theory, but whether it can work consistently in the presence of interference, harsh conditions, and operational constraints. SECURITY AND SEGMENTATION Security is another major thread throughout the conversation. The group discusses how wireless signals can extend beyond the physical boundary of a plant, creating exposure far outside the immediate site perimeter. They also explain why segmentation, layered defense, and proper firewall policies are essential in OT, especially where wireless devices connect to systems that can influence real-world operations. A recurring point in the episode is that baseline security matters more than advanced monitoring tools if the foundational architecture is weak. In other words, specialized detection platforms and advanced analytics only go so far if the network is still flat, overexposed, or poorly segmented. WIRELESS IN THE REAL WORLD The episode includes a number of practical examples that show why wireless design decisions matter. The panel talks about industrial sites where radios are visible far beyond the property line, where weak security leaves control systems exposed, and where wireless sensor data can create both value and risk. They also explore how cloud-connected sensor systems and wireless monitoring tools can improve visibility without needing to become part of the core control network. Toward the second half of the episode, the conversation shifts to emerging wireless technologies. The team discusses Wi-Fi 6E and Wi-Fi 7 deployments, antenna challenges, spectrum availability, and what industrial teams should realistically expect from the newest standards. The consensus is clear: new technology is useful, but only when it solves an actual operational problem. CONCLUSION Episode 26 is a practical discussion for anyone working in industrial networking, automation, OT, or plant-floor wireless design. Whether you are dealing with RF interference, roaming, security, uptime, or the decision of whether wireless even belongs in a given application, this episode offers useful perspective from people who have spent real time in the field. If your team is evaluating industrial Wi-Fi or trying to improve wireless reliability in manufacturing, this episode is built to help you think through the tradeoffs before making deployment decisions.

1. juni 20261 h 29 min
episode The Industrial Wi-Fi Shop Podcast – Ep. 25 Industrial Wireless Clients cover

The Industrial Wi-Fi Shop Podcast – Ep. 25 Industrial Wireless Clients

Upcoming Events! * Upcoming Wi-Co Events * Be sure to check https://wi-co.org/ [https://wi-co.org/] Don’t forget to check out our new document library with free valuable downloadable content! * Miliwatt to dBm  conversion table * Wireless IoT reference charts for types and security * Best practice white papers to help you stay on your game Why specialized industrial wireless clients? * Wireless clients are the bridge between the past and the present. The vast majority of industrial devices, PLCs, drives, sensors, HMIs, and controllers, are engineered for deterministic performance and long service life, not wireless connectivity. They ship with Ethernet ports, not radios. Industrial wireless client radios exist specifically to give these wired-by-design devices a wireless presence without requiring any changes to the device itself or the control program running inside it. * Freedom of movement changes what’s possible on the plant floor. Conveyors, AGVs, robotic arms, transfer carts, and overhead cranes all move, and running Ethernet cable to something that moves is either impractical, expensive, or eventually guaranteed to fail. Wireless clients eliminate the cable entirely, giving mobile and rotating machinery reliable network connectivity that moves with the equipment. * Wireless clients enable the Industrial Internet of Things (IIoT) without a forklift upgrade. Adding wireless clients to existing field devices means real-time data, cycle counts, temperatures, fault codes, production rates, can flow to SCADA systems, historians, and cloud analytics platforms without replacing equipment that still has years of useful life left. The radio does the heavy lifting; the device just keeps doing its job. * In hazardous, remote, or physically inaccessible locations, wireless isn’t a convenience,  it’s the only option. Tank farms, offshore platforms, grain elevators, and mining operations all present environments where pulling cable is either dangerous, cost-prohibitive, or physically impossible. Industrial-grade wireless clients, rated for wide temperature ranges, vibration, and hazardous area classifications, make instrumentation and control possible in places where no wire will ever go. Phoenix Contact 1021 Industrial Wireless Client Modes: * In FTB mode, the client radio acts as a wireless bridge allowing multiple wired end devices to communicate transparently via Layer 2 or Layer 3 communication. FTB is used when wirelessly connecting to a Phoenix Contact WLAN module configured as an access point. * In SCB mode, data is transmitted transparently on Layer 2. Only the device whose MAC address is entered for the radio can be accessed via WLAN, and only one wired device may be connected. * In MCB mode, the Phoenix radio uses a Layer 2 NAT function when communicating to the access point, allowing multiple wired clients to communicate over the wireless connection. All wired clients behind the device are transmitted with the MAC address of the radio, the number of wired clients is unlimited. * Client (NAT) breaks into two sub-modes: * 1:1 NAT, where each LAN device is allocated an IP address from the higher-level network so it can be reached from the WAN * IP masquerading, where the NAT device acts as a proxy and all LAN devices communicate externally using only the NAT device’s own WAN address — with TCP/UDP ports used to differentiate between devices. This is useful when you have duplicate IP address spaces across identical machine cells. * Client (VXLAN), the fully transparent bridge and VxLAN (Virtual Extensible LAN) enable transparent PROFINET and PROFIsafe communication, which is critical in automation networks. This mode is documented in relation to the WLAN 1000 client family pairing with the new WLAN 2300 access points. It’s standards-based (RFC 7348), so it isn’t locked to Phoenix Contact infrastructure the way FTB is. What is VxLAN? * VxLAN wraps a complete Ethernet frame inside a regular IP/UDP packet so it can travel anywhere IP travels, then unwraps it at the other end, making two distant devices believe they’re sitting on the same local wire. Why it matters for industrial wireless specifically: * Protocols like PROFINET and PROFIsafe are “Layer 2 snobs”, they expect to see the real MAC address of the device they’re talking to, unmodified, end to end. Modes like MCB swap out MAC addresses behind the scenes, which breaks PROFINET. VxLAN mode preserves everything inside the tunnel,  the receiving device opens it up and sees the exact original Ethernet frame, MAC address intact, as if the wireless hop never happened. VXLAN vs FTB — what’s the difference? Both achieve true Layer 2 transparency, but: * FTB is Phoenix Contact proprietary and requires a Phoenix Contact AP on the infrastructure side * VXLAN is standards-based (IETF RFC 7348) and works with any AP or controller that supports VXLAN termination, including the Phoenix Contact WLAN 2300 series access points [https://industrialwifishop.com/wp-content/uploads/2026/03/image-1.png?w=1024] ProSoft Technologies RLX2-IHNF-A, Four Operational Modes Explained * Master – The Master is the anchor and root of the entire RLX2 wireless network. Every other radio in the network, Repeaters, Bridging Clients, and Clients, ultimately connects back to the Master, either directly or through a chain of Repeaters. There is typically one Master per wireless network, though multiple Masters can coexist without special programming for redundancy. * Repeater – The Repeater is the workhorse of the ProSoft network. It connects wirelessly to a Master (or another Repeater), extends the wireless coverage area, and simultaneously allows additional radios to connect through it. It is also the factory default shipping configuration, every RLX2 radio ships as a Repeater out of the box, ready to link to whatever Master it finds. * Bridging Client – Bridging Client is the mode used when you want to connect multiple wired Ethernet devices through a single RLX2 radio to a third-party 802.11 access point, not a ProSoft Master. Think of it as the “multi-device adapter” for foreign Wi-Fi infrastructure. * Bridging Client mode is specifically designed for environments where the access point is not a ProSoft radio. It uses standard 802.11 association and works with the AP’s existing SSID and security settings. Note that some third-party AP controllers (notably Cisco WLC systems) may require additional configuration to allow multiple MAC addresses over a single wireless association — the same consideration that applies to MCB mode in other industrial radio families. * Client – Client mode is the simplest connection mode in the RLX2 lineup — one radio, one wired device, one wireless connection to a third-party access point. It’s the “single device adapter” for foreign Wi-Fi infrastructure. * The radio can be configured in two sub-modes: * Auto, the radio automatically detects the MAC address of whatever is plugged into its Ethernet port and uses it for the wireless association. Easy, fast, and appropriate for most single-device setups * Specify, the operator manually enters the MAC address of the target device. The manual notes this is only necessary for devices that do not send unsolicited Ethernet packets — meaning the device is passive and doesn’t announce itself. ProSoft’s guidance is to try Auto first and only use Specify if Auto doesn’t work [https://industrialwifishop.com/wp-content/uploads/2026/03/image.png?w=1024] As you probably know, Scott and Jeremy work with different application types for the most part. Jeremy primarily touches mobility applications with mixed/client and infrastructure. Jeremy generally works with whatever infrastructure the end customer has for enterprise and occasionally gets to build both ends of the WLAN. Jeremy’s team used to use the Aruba501, which had a lot going for it. RSSI log, simple interface, remote packet capture, exportable logs.. <- You could do a lot to troubleshoot these devices. I was just on a call with a vendor and it is both nice and disheartening to hear that telemetry and data can be hidden because the “casual end customer” will generate more nonsense complaints if the nerd knobs are exposed. Sometimes you have to get into the weeds, limiting MCS, NAT/IP Masquerading to work around passive client issues. What is a Passive Client? A passive client is a device that does not actively participate in normal network communication unless it is polled or queried. In practical terms, a passive client: * Does not initiate traffic on its own * May not send ARP, DHCP renewals, or periodic data * Only responds when another device communicates with it Examples in industrial environments * PLCs waiting for control traffic * I/O devices that only respond to cyclic polling * Sensors that do not generate unsolicited traffic NAT, specifically IP masquerading, helps by making multiple downstream devices appear as a single active client to the wireless network. The radio handles all communication on behalf of the devices behind it, so the infrastructure only needs to track one MAC and IP address. This keeps passive devices reachable even if they never transmit, but the tradeoff is that Layer 2 transparency is lost, which can break protocols that rely on seeing the original MAC addresses. So this is one of the main reasons we lean on the Siemens hardware. Siemens Siemens SCALANCE typical models: W734 – WiFi 4 and WUM763/766 The WiFi4 stuff is well established and has tons of features. * Dynamic antenna selection * NAT/IP Masquerading * Remote capture on WLAN interface * Available APs <- helps identify interferers * Signal Recorder Piecewise site survey, lots of KPIs and if you have Siemens infrastructure you can get both sides of the conversation. * Detailed Logging * Config Plugs * iPCF * Force Roam on IP Down Most of this is still present in the WiFi6 hardware. PoE capability is not present in the WUM763. Siemens cabinet based models are IP30 The hardened units are IP65, and typically use some variation of M12 connector. D-coded or X-coded 8 pin. 1. Transparent Bridge (Default / Standard Mode) * True Layer 2 bridge * Passes all MAC addresses unchanged * Supports: * PROFINET * PROFIsafe * Multiple devices behind the client are fully visible to the network This is the primary and most important mode for all of these clients. 2. Layer 2 Tunnel Mode (Used with IPCF) * Required when running IPCF (deterministic wireless) * Encapsulates Ethernet frames for controlled delivery * Maintains full Layer 2 transparency * Used specifically for: * Real-time industrial communication * Deterministic cyclic traffic Siemens explicitly calls out using “Layer 2 Tunnel” MAC mode with IPCF  3. Standard Wi-Fi (DCF) vs IPCF Operation This is a major behavioral “mode” difference: DCF (DEFAULT WI-FI) * Standard contention-based Wi-Fi * Works with any infrastructure * Non-deterministic IPCF Mode * Scheduled medium access (deterministic) * AP controls airtime * Used for: * Motion control * Real-time automation Important: * IPCF and standard Wi-Fi cannot be mixed in the same cell  Aunex Aunex wireless clients are designed to be flexible and infrastructure-agnostic. They behave more like traditional Wi-Fi clients with options for bridging or NAT, making them easy to integrate into mixed networks. The tradeoff is that they rely on standard Wi-Fi behavior, so they don’t provide the same level of deterministic performance or deep diagnostics that more specialized industrial platforms offer. They have 6E Clients. Core Design Approach MODAS clients follow a standard 802.11 client model and are designed to work with a wide range of third-party access points and controllers. They support: * Single-device client operation * Multi-device bridging * Layer 3/NAT-based connectivity The focus is on adaptability rather than tightly controlled, deterministic wireless behavior. Networking Behavior Layer 2 Bridging * Can pass Ethernet frames between wired devices and the WLAN * May support multiple MAC addresses depending on configuration and infrastructure * Works best in networks that allow multi-MAC clients NAT / Routing Modes * Supports Layer 3 NAT / IP masquerading * Useful for: * Handling duplicate IP address spaces * Reducing MAC scaling challenges on controllers * Simplifying machine-level network integration MAC Handling * Can operate as: * Transparent bridge (when supported) * Single visible client using NAT Wireless Capabilities * Operates using standard Wi-Fi (DCF) * Supports common enterprise features: * WPA2/WPA3 * Roaming (model dependent) * No deterministic scheduling mechanism like IPCF Legacy Interface Flexibility (Key Differentiator) One area where MODAS clients stand out is support for legacy industrial interfaces, including: * RS-232 / RS-485 serial connectivity * Serial-to-IP conversion (serial tunneling) * Ability to transport legacy protocols over Wi-Fi Why this matters * Many industrial systems still rely on serial communications * MODAS devices can act as a bridge between legacy serial equipment and modern IP networks * Enables: * Retrofit of older machines without replacing hardware * Wireless connectivity for devices that were never designed for Ethernet Typical behavior * Serial data is encapsulated into IP packets * Transported over Wi-Fi * Reconstructed at the receiving end This allows legacy devices to function across a wireless link as if they were locally connected. Diagnostics and Management * Provides standard industrial diagnostics: * RSSI / signal strength * Link status * Throughput and error counters * Typically lacks deep RF time-series logging found in more specialized platforms If you would like to connect with Scott or learn more about his employer, Global Process Automation (GPA), then check the following: Scott McNeil – https://www.linkedin.com/in/americanmcneil/ [https://www.linkedin.com/in/americanmcneil/]  GPA – https://www.global-business.net/ [https://www.global-business.net/]  If you would like to connect with Jeremy or learn more about his employer, Prism Systems Inc, then check the following: Jeremy Baker – https://www.linkedin.com/in/jeremyabaker/ [https://www.linkedin.com/in/jeremyabaker/]  Prism Systems Inc – https://www.prismsystems.com/ [https://www.prismsystems.com/]

30. mar. 20261 h 31 min
episode The Industrial Wi-Fi Shop Podcast – Ep. 24 Clip, Click, Survey! cover

The Industrial Wi-Fi Shop Podcast – Ep. 24 Clip, Click, Survey!

IWS Episode 24 Show Notes – Clip, Click, Survey: Modern Tools for Industrial Wireless Upcoming Events! * WLPC – Phoenix AZ USA 2026 * Main Conference: 17-19 FEB 2026 * Boot Camps: 14-16 FEB 2026 * Upcoming Wi-Co Events * Thursday, 12 March 2026 — Stockholm, Sweden (Downtown Camper by Scandic) * Thursday, 9 April 2026 — Helsinki, Finland (Epicenter) * Thursday, 16 April 2026 — Philadelphia, PA, USA (1100 Pattison Avenue) * Wednesday, 22 April 2026 — Toronto, Canada (Steam Whistle Brewing) * Wednesday, 29 April 2026 — Frankfurt, Germany (Hilton Garden Inn Frankfurt City Centre) * Thursday, 21 May 2026 — Brussels, Belgium (Park Inn by Radisson) * Wednesday, 3 June 2026 — Oslo, Norway (Telnor Expo) * Thursday, 2 July 2026 — Lyon, France (Mob Hotel) * Wednesday, 9 September 2026 — Manchester, UK (Stoller Hall) * Thursday, 24 September 2026 — Cleveland, OH, USA * Wednesday, 7 October 2026 — Montreal, Canada * Tuesday, 10 November 2026 — Washington, DC, USA Don’t forget to check out our new document library with free valuable downloadable content! * Miliwatt to dBm  conversion table * Wireless IoT reference charts for types and security * Best practice white papers to help you stay on your game IWS Episode 24 – Clip, Click, Survey: Modern Tools for Industrial Wireless * Device Positioning & Strategy * What problems Hamina aimed to solve with the Clip, e.g., reduction of cables, simplification of surveys, lighter carry-loads vs traditional hardware. * Hardware Design Philosophy * Explaining the rugged and compact industrial design: * Dust/splash resistance * Drop and temperature tested * Silent with no active cooling needed * All-day battery life with USB-C charging. * Clip vs Nomad Comparison * The product page clearly separates Clip from Nomad, a more traditional shoulder-strap survey device with advanced packet capture and spectrum capability.  * What were the tradeoffs and why two device formats? * Airtool and WiFi Explorer sensors * Wireless Connection Workflow * How Clip connects wirelessly via BLE to phones/tablets (vs USB-C for Nomad) and why that matters for field surveys, including reliability and freedom of movement.I * Integration with Hamina Onsite[https://industrialwifishop.wordpress.com/b55af006-82a0-4cee-bc02-cfd890716093] * Clip is designed to work seamlessly with the Hamina Onsite app, covering multi-floor surveys, real-time troubleshooting, and live heatmapping.  * How does this tight integration improve productivity? * Wi-Fi Generation Support * Support for 2.4, 5, and 6 GHz Wi-Fi including Wi-Fi 7 and earlier standards * why multi-band support is crucial today. * Spectrum Capabilities * Clip offers a standard RF spectrum view without full raw RF energy, ideal for most surveys, while Nomad can be expanded with tools like NetAlly NXT-2000 for full spectrum analysis.  * How does the base capability serve most use cases vs advanced stakeholders? * Real-World Testimonials * Clip’s official product page shows quotes from Wi-Fi experts (HPE, Cisco, and independent professionals) praising its clip-on mobility and cable-free operation.  * Who all has had a chance to put this new device through its paces? * Survey Speed & Accuracy * What are the operational impacts of lighter tools?  * More surveys per day, faster thank-you motion compared to traditional bulky gear. How can the Hamina Clip Benefit OT Wireless Deployments? * Rapid Field Validation * The Clip’s portability enables quick turn-key surveys on manufacturing floors, warehouses, and other OT sites where wired hardware is impractical. * Cable-Free Freedom * Field engineers no longer need to carry or manage USB cables, especially useful in large industrial spaces or dense production aisles. * Lightweight for Frequent Use * At ~282 g, the Clip stays in everyday bags, encouraging more frequent and thorough surveys. * BLE Connected Surveys * Wireless BLE connectivity allows uninterrupted survey data capture even while moving through metal-rich OT spaces with reflection and interference. * Environmental Ruggedness * Designed to withstand dust, splash, heat, and cold, essential for industrial and factory climates. * Multi-Band Wi-Fi Coverage * Coverage of 2.4 GHz, 5 GHz, and 6 GHz bands gives visibility into dense enterprise/OT traffic environments and supports future-proof deployments. * Efficient Troubleshooting * Instant heatmaps with Hamina Onsite allow engineers to quickly identify dead spots, interference zones, and roaming boundaries in OT environments. * Training & Documentation * Ease of use lowers the learning curve for technicians new to site surveys, reducing training costs and increasing survey adoption. * Site-Wide Consistency * Lighter tools mean more consistent usage across large facilities, improving coverage baseline documentation for OT support and SLA validation. * Flexible Deployment Model * The existence of both Clip and Nomad allows teams to choose the right tool for the job, lightweight speed or full technical capability, without sacrificing unified software workflows. https://ai-tools.teigenrf.org/ [https://ai-tools.teigenrf.org/] Joel’s site –  https://clipboard.potatofi.com/ [https://clipboard.potatofi.com/]  Joel’s site – https://spectrum.potatofi.com/ [https://spectrum.potatofi.com/]  If you would like to connect with Jerry or learn more about his employer, Hamina, then check the following: Jerry Olla – https://www.linkedin.com/in/jerryolla/ [https://www.linkedin.com/in/jerryolla/]  Hamina – https://www.hamina.com/ [https://www.hamina.com/]  If you would like to connect with Scott or learn more about his employer, Global Process Automation (GPA), then check the following: Scott McNeil – https://www.linkedin.com/in/americanmcneil/ [https://www.linkedin.com/in/americanmcneil/]  GPA – https://www.global-business.net/ [https://www.global-business.net/]  If you would like to connect with Jeremy or learn more about his employer, Prism Systems Inc, then check the following: Jeremy Baker – https://www.linkedin.com/in/jeremyabaker/ [https://www.linkedin.com/in/jeremyabaker/]  Prism Systems Inc – https://www.prismsystems.com/ [https://www.prismsystems.com/]

9. feb. 20261 h 36 min
episode The Industrial Wi-Fi Shop Podcast – Ep. 23 What’s on the Bench? cover

The Industrial Wi-Fi Shop Podcast – Ep. 23 What’s on the Bench?

Upcoming Events! * WLPC – Phoenix AZ USA 2026 * Main Conference: 17-19 FEB 2026 * Boot Camps: 14-16 FEB 2026 Jeremy – I got a 20 minute talk at WLPC, Common Industrial WLAN Deployments Don’t forget to check out our new document library with free valuable downloadable content! * Miliwatt to dBm  conversion table * Wireless IoT reference charts for types and security * Best practice white papers to help you stay on your game IWS Episode 23 – What’s on the Bench? Links to all of the interesting things we were talking about! * Milesight LoRaWan Field Tester – https://www.milesight.com/product/accessories/ft101 [https://www.milesight.com/product/accessories/ft101] * The Milesight Field Tester FT101 is the ultimate companion for signal assessment and optimization in LoRaWAN® networks. Featuring a 5.72-inch HD touch screen, it provides real-time network signal testing and analysis at your fingertips, making it easier to deploy and manage LoRaWAN® devices. * Heltec Wi-Fi HaLow Dongle v2 – https://heltec.org/project/ht-hd01/ [https://heltec.org/project/ht-hd01/] * A long-range communicator based on Wi-Fi HaLow, the communication range is 1–2 km. It can be used to extend the coverage of traditional networks through bridging, to set up LAN, or to serve as an IoT protocol. Pair two devices for use, or work with the HaLow gateway. * Epitiro – https://www.epitiro.com/wi-fi-7-capable-agent/ [https://www.epitiro.com/wi-fi-7-capable-agent/] * Ensuring better internet today and tomorrow. Wi-Fi 7 is on its way. If you’re looking to monitor your current and future internet performance, get ahead of the curve with our new 6177 agent. Our new agent ensures you can reliably monitor, test and remotely troubleshoot your existing Wi-Fi networks and any upgraded or future Wi-Fi 6, 6E, or 7 network. This means you can confidently deploy our best-in-class monitoring solution knowing your investment is futureproofed to work today and for years to come. * WLAN Pi – https://www.wlanpi.com/ [https://www.wlanpi.com/] * It all began with an idea. Then a community of wireless engineers formed to create an affordable tool tailored to the every day needs of someone in Wi-Fi. * Sidos Wave – https://www.sidos.com/sidos-wave/ [https://www.sidos.com/sidos-wave/] * Introducing Sidos Wave, the most advanced and accurate Wi-Fi measurement device on the market. The Wave is rugged, blazing fast, lightweight, and capable of performing high-precision surveys across 2.4 GHz, 5 GHz, and 6 GHz bands. * Fünfeinhalb (BlitzFunk wireless radios) – https://fuenfeinhalb.de/en/products#W10= [https://fuenfeinhalb.de/en/products#W10=] * Conventional Wi-Fi was designed for people, not for machines. When multiple wireless devices are involved and movement occurs, delays can bring systems to a halt. * For industrial control systems, the maximum latency and minimum data rate in the worst case are what matter — not just the advertised best values. We promise nothing we cannot uphold in 99.9999% of cases. * NetAlly Cyberscope Air – https://cyberscope.netally.com/products/cyberscope-air [https://cyberscope.netally.com/products/cyberscope-air] * CyberScope Air enables SecOps or NetOps teams to discover, validate, and scan edge infrastructure and IoT, OT, and ICS devices whether WiFi or Bluetooth/BLE. Assessing cybersecurity posture of WLANs against policies, generating reports, and performing ongoing monitoring for changes has never been easier. * NetAlly LinkRunner 4000 – https://www.netally.com/products/linkrunner-4000/ [https://www.netally.com/products/linkrunner-4000/] * The LinkRunner AT 4000 is a cutting-edge network cable tester for modern networking tasks and infrastructural diagnostics. Designed for network engineers requiring a robust toolset for both fiber and Multigigabit Ethernet environments * NetAlly Test Accessory – https://www.netally.com/products/testaccessory/ [https://www.netally.com/products/testaccessory/] * This portable iPerf tool allows you to proactively validate network performance conveniently, even when infrastructure accessibility is limited. It accomplishes the same network port tests as LinkSprinter and seamlessly reports back to Link-Live. * Air Console – https://www.get-console.com/shop/en/27-airconsole [https://www.get-console.com/shop/en/27-airconsole] * Airconsole is our popular portable, battery powered, RS232 Serial over WIFI and/or BT Adaptor. Designed to be seamlessly used with Mobile Apps on iOS, Android and also on PC, MAC OSX and Linux, Airconsole provides flexible and convenient access to physical Serial and Ethernet ports from devices (such as iPads and iPhones) that have only WIFI or BT interfaces. * IP Explorer – https://plctools.com/products/sim-ipe [https://plctools.com/products/sim-ipe] * Discover unknown IP addresses, assign an IP address via BOOTP or DHCP, and set to static or change the IP address of Ethernet/IP enabled devices. * It replaces your computer based BOOTP/DHCP Server and will quickly assign any IP address to any industrial BOOTP or DHCP enabled control device, like Programmable Controller, PLC communication modules, smart switches and I/O adapters. * This is not a port scanner that chokes networks.  It actively listens to network traffic to discover devices by looking for EtherNet/IP, Profinet, GigE,  ARP, and other discoverable packets.  If a device sits silently on the network, it will not be discovered. * It works with many brands of Ethernet devices including Allen Bradley and Siemens.  We do not have a comprehensive list of brands that it works with.  DHCP and BOOTP assignment will always work, IP discovery works with popular devices, and Set to Static and Change Static IP require that the device be Ethernet/IP compliant. * WiFi Explorer – https://www.intuitibits.com/products/wifiexplorer/ [https://www.intuitibits.com/products/wifiexplorer/] * Determine a better placement for your access point, identify channel conflicts or troubleshoot configuration issues that may affect your Wi-Fi network’s connectivity and performance. * WLPC – https://www.thewlpc.com/ [https://www.thewlpc.com/] * WLPC is all about the people. Whether you’re just starting your career in WLAN technologies or you’ve been in the field for decades, we would love to see you at one of our upcoming events. * #WLPC is a vendor-neutral event, free of sales pitches, where Wi-Fi enthusiasts gather to discuss technology, share knowledge, and engage in one of the best tech communities in the world. Each event offers multiple ways to learn and grow your skills and knowledge through Boot Camps, Deep Dives, and Presentations, along with valuable connections and learning that happen over meals, drinks, and in the hallways. * Wi-Co – https://wi-co.org/ [https://wi-co.org/] * Wi-Co, short for Wireless Community, is the brainchild of Peter Mackenzie and Alan Blake, on a mission to make the Wireless Community party like it’s 1999 (but without the B rates). * Their strategy? Well, it’s all about “bringing the herd together” by organising Affordable, Accessible, Local Events, all over the world,  where knowledge is shared. * They’ve got the leading technology companies in on the action too! With the help of these benevolent backers, Wi-Co ensures that their events are not just Wireless strong but also financially fit. If you would like to connect with Ali or learn more about his employer, Nile, then check the following: Ali – https://www.linkedin.com/in/mali77/ [https://www.linkedin.com/in/mali77/]  Nile –  http://www.nilesecure.com [http://www.nilesecure.com/]  If you would like to connect with Mark or learn more about his employer, Northeastern Utah Educational Services, then check the following: Mark Houtz – https://www.linkedin.com/in/markhoutz/ [https://www.linkedin.com/in/markhoutz/]  NUES –  http://www.nucenter.org [http://www.nucenter.org/] If you would like to connect with Nick or learn more about his employer, Blitsfunk, then check the following: Nick Schwarzenberg – https://www.linkedin.com/in/nick-schwarzenberg/ [https://www.linkedin.com/in/nick-schwarzenberg/]  Blitzfunk – https://fuenfeinhalb.de/en [https://fuenfeinhalb.de/en]  If you would like to connect with Tobias or learn more about his employer, Aunex, then check the following: Tobias Meyer – https://www.linkedin.com/in/americanmcneil/https://www.linkedin.com/in/tobimeyer/ [https://www.linkedin.com/in/tobimeyer/]  Aunex Inc. – https://www.global-business.net/https://aunex.io/en-us/ [https://aunex.io/en-us/]   If you would like to connect with Scott or learn more about his employer, Global Process Automation (GPA), then check the following: Scott McNeil – https://www.linkedin.com/in/americanmcneil/ [https://www.linkedin.com/in/americanmcneil/]  GPA – https://www.global-business.net/ [https://www.global-business.net/]  If you would like to connect with Jeremy or learn more about his employer, Prism Systems Inc, then check the following: Jeremy Baker – https://www.linkedin.com/in/jeremyabaker/ [https://www.linkedin.com/in/jeremyabaker/]  Prism Systems Inc – https://www.prismsystems.com/ [https://www.prismsystems.com/]

26. dec. 20251 h 36 min