MOROS.neo

WiFi: What’s the difference between an access point and a client—and when should I use 2.4 GHz or 5 GHz?

In access point mode, the router provides its own WiFi network. This is particularly useful for setup, maintenance, or temporary on-site access when you want to connect to the device without additional cabling. In client mode, however, the router uses an existing WiFi network as an uplink and integrates into an existing infrastructure.

2.4 GHz is particularly suitable when range, compatibility, and a robust basic connection are the top priorities. 5 GHz is usually the better choice if you want higher performance and less congested channels. Important: The integrated WiFi is designed for a clearly defined purpose. Therefore, only one band or one mode is active at a time.

Dual-SIM (DSSS): What does “Dual SIM” mean – and why can only one SIM be online at a time?

With Dual SIM Single Standby (DSSS), two SIM cards are present in the device, but only one SIM is online. The second SIM remains on standby and is used when a switch is necessary. The added value, therefore, lies not in parallel operation, but in robust and clearly manageable redundancy.

If the primary network fails or no longer meets defined requirements, the system can switch to the secondary SIM. This increases the availability of the mobile connection without unnecessarily complicating the architecture. It is important to note that: DSSS stands for redundancy, not for load-balancing and not for active-active operation.

Dual-SIM Best Practices: Which SIM combinations make sense?

If maximum availability is the priority, Provider A is generally recommended as the primary SIM and Provider B as the fallback SIM. This reduces the risk that both cards will be affected by the same network outage or the same backend issues.

If, on the other hand, costs or internal requirements play a greater role, a cost-effective primary plan paired with a robust secondary plan may be advisable. For industrial applications, we generally recommend using only M2M SIMs, as these are designed for long-term operation and higher resilience. Ultimately, the deciding factor is whether your priority lies more with availability, cost control, or single provider and security requirements.

Gigabit Ethernet & VLAN/Managed Switch: When Is IT/OT/Service Network Segmentation Recommended?

Segmenting local IP networks using VLANs and managed switch functions is recommended when the router, acting as a central gateway, needs to clearly separate multiple communication domains from one another – such as IT, OT, service access, or even a separate camera, diagnostic, or process network.

The benefit is twofold: it provides greater clarity while simultaneously increasing security, as data streams, access rights, and network segments remain clearly separated. This is particularly relevant when different user groups, security requirements, or data-intensive components come together.

RS-485/RS-232: Why do we still need these today?

RS-485 and RS-232 remain relevant in industrial environments because many legacy devices, field devices, and sensors still communicate via serial interfaces. This is particularly true for legacy and retrofit scenarios where existing infrastructure is to be reused rather than replaced solely for the sake of communication technology.

This is precisely where the practical benefit lies: Serial devices can still be integrated, for example via Serial-over-IP or as a Modbus RTU/TCP gateway.

Secure Boot: What are the benefits, what do I need to know, and what are the implications?

Secure Boot is not a feature you need to actively use; rather, it is a platform security mechanism. The device boots only with approved and signed INSYS firmware, and the entire boot process is cryptographically secured. This reduces the risk of tampering and supports higher security requirements in industrial environments.

It is important to understand the proper context:

• Secure Boot is an additional protective measure, but it does not replace secure configuration, network segmentation, access control policies, or organizational security processes.
• Likewise, Secure Boot should not be interpreted to mean that devices without Secure Boot are inherently insecure.
• For you, Secure Boot primarily means greater confidence in the integrity of the platform and a securely established foundation for operation.

Already today, INSYS icom routers running icom OS exclusively accept the loading of firmware signed by INSYS. Secure Boot extends this protection to the entire boot process – including the bootloader.

Containers/LXC: Which applications can I run directly on the router—and what are the limitations?

With containers (LXC), the router becomes a local application platform. This is particularly useful for clearly defined applications such as protocol gateways, data loggers, edge analytics, or customer-specific logic. This allows data and protocols to be processed directly on the device without always having to plan for additional IPC hardware. This reduces integration effort and system complexity.

A major advantage lies in field operability: In conjunction with INSYS icom Router Management (iRM), applications can be deployed and updated in a targeted manner. Together with icom OS, this also creates a transparent framework for access, operation, and IT security.

The main limitations lie in the required computing power. The decisive factor here is either the type of implementation – for example, if an application is inefficiently programmed – or a fundamentally very high performance requirement, such as in AI-based image processing. In such cases, an IPC is often the more suitable solution. When it comes to the efficient implementation of container applications, INSYS icom is happy to provide you with targeted support.

Does MOROS.neo support 5G – and if not, what alternatives are available for 5G projects?

MOROS.neo is a good choice if your application can be reliably supported by 4G, Ethernet, and optional WiFi. This is already entirely sufficient for many industrial use cases – for example, when secure remote access, stable communication, and a cost-effective solution are the top priorities.

However, if your project requires 5G – for example, due to higher data rates, lower latency, or specific on-site requirements – MRX.neo is the more suitable alternative. This provides you with a platform that offers greater flexibility for such requirements and can be specifically tailored to more demanding mobile applications.

In short: MOROS.neo is the right choice if 4G already meets your needs. MRX.neo is the right choice if your use case actually leverages the additional capabilities of 5G.