All-in-One IoT Controllers for Industrial Data Collection Without Programming
Stop wrestling with complex IoT systems that demand custom code for every sensor. M2M Controllers deliver built-in data acquisition, storage, visualization, and cloud transmission through simple web-based configuration. No programming skills required. Connect your factory sensors to any cloud service in hours, not months—while maintaining full control at the edge.
Why Traditional IoT Implementation Fails in Industrial Environments
You've seen the IoT hype: "Connect everything to the cloud! Get real-time insights!" But when you actually try to implement it in your factory, you hit these walls. Sound familiar?
"Our Team Doesn't Know Python/C++"
Traditional IoT platforms require custom coding for every sensor interface. Need to hire expensive programmers or consultants. 3-6 month development cycles for "simple" data collection projects.
"Nothing Talks to Anything"
Sensor A speaks Modbus, Sensor B speaks 4-20mA analog, PLC C speaks proprietary protocol. You need 3 different converters, 2 different software packages, and a prayer that they'll all work together.
"What If Internet Goes Down?"
Cloud-only IoT solutions sound great until your factory loses connectivity. Production stops, but you still pay monthly cloud fees. No local control, no local HMI, no fallback plan.
"Per-Tag Pricing Is a Trap"
Cloud IoT platforms charge per data point, per user, per screen. Starts affordable until you realize you need 500 tags. Suddenly facing thousands per month in recurring fees with no escape clause.
"It Works in the Lab..."
Consumer-grade IoT boards work fine in office conditions (20-25°C). Place them in real industrial environments—near heat sources (45°C+) or cold storage (-15°C)—and reliability issues appear. Industrial applications require industrial-grade hardware.
"The Guy Who Built This Left"
Custom-coded IoT system works great until the developer leaves. Nobody knows how to modify it, debug it, or add new sensors. You're stuck maintaining mystery code or starting from scratch.
These aren't edge cases—they're the norm for traditional IoT implementations. But what if there was a different approach? One designed specifically for industrial engineers, not software developers?
How M2M Controllers Fit Into Your Industrial Ecosystem
Understand the complete data flow from field sensors to cloud platforms. M2M Controllers sit at the critical edge layer, bridging legacy industrial equipment with modern cloud infrastructure.
M2M Controller System Architecture
Complete data flow from field devices to cloud platforms
Key Architecture Benefits:
- •Edge Intelligence: Process data locally before cloud transmission (reduce bandwidth, faster response)
- •Offline Resilience: Local storage ensures no data loss during internet outages
- •Protocol Translation: Bridge legacy serial devices with modern cloud APIs
- •Distributed Access: Operators view HMI locally, managers access cloud dashboards
Key Architecture Benefits:
- Edge Intelligence: Process data locally before cloud transmission (reduce bandwidth, faster response)
- Offline Resilience: Local storage ensures no data loss during internet outages
- Protocol Translation: Bridge legacy serial devices with modern cloud APIs
- Distributed Access: Operators view HMI locally, managers access cloud dashboards
M2M Controllers: Complete All-in-One Solution for Industrial Data Collection
Instead of buying multiple devices from different vendors, M2M Controllers give you one integrated device that handles data acquisition, local storage, visualization, and cloud transmission. Configure everything through a web browser—no programming, no software installation, no monthly per-tag fees.
Collect Data from Any Source
Digital I/O, analog sensors (4-20mA, 0-10V), thermocouples, RTDs, counters, RS-232C/485 serial devices—all supported natively. No custom drivers or middleware required.
- Analog: 4-20mA, 0-10V, ±10V
- Digital: Opto-isolated 8-16ch
- Serial: RS-232C, RS-422A/485
- Counter: Encoder, pulse, frequency
Store Data at the Edge
Internal storage logs data locally even when cloud connection fails. No data loss during internet outages. Automatic sync when connection restores.
- Local database storage
- Circular buffer (auto-overwrite old data)
- Works fully offline if needed
- Sync to cloud when available
Visualize via Any Browser
Built-in web server serves HMI screens to any device with a browser. No SCADA software license needed. Access from factory LAN, VPN, or cloud.
- 37 UI components (gauges, graphs, buttons)
- Drag-and-drop HMI builder
- Multi-screen support (unlimited)
- Access from PC, tablet, phone
Send Data Anywhere
Transmit to any cloud service (AWS, Azure, Google Cloud) or your own on-premise server. MQTT, HTTP/HTTPS, OPC UA protocols supported.
- MQTT publisher/subscriber
- HTTP POST/GET to REST API
- OPC UA server (selected models)
- Cloud optional, not mandatory
Cloud Transmission Data Flow with Offline Resilience
See how the M2M Controller handles internet outages with local buffering and automatic retry logic. Zero data loss guaranteed even when connectivity drops.
Integrated Type vs Configurable Type: Which Fits Your Application?
Both types deliver the same built-in functionality (data acquisition, HMI, cloud transmission). The difference is physical form factor and I/O expandability.
Fixed I/O configuration in a single compact device. Plug-and-play installation—mount on DIN rail, connect sensors, power on. Best for small to medium I/O requirements.
• Width: 188.0 mm
• Depth: 78.0 mm
• Height: 30.5 mm
• DIN rail or fixed mounting
• Daisy-chain connections (no HUB)
• Temperature: -20°C to 60°C
• Humidity: 10% to 90% RH non-condensing
• Input: 12 to 24 VDC
• Consumption: Varies by model (typically 3-8W)
Modular system: Controller unit + I/O expansion modules. Add up to 16 I/O modules per controller. Mix-and-match different module types (analog, digital, relay, counter, serial).
• Width: 44.7 mm
• Depth: 94.7 mm
• Height: 124.8 mm
• DIN rail mountable
• Modular stacking design
• Each module adds 12.5-25mm width
• Temperature: -20°C to 60°C
• Humidity: 10% to 90% RH non-condensing
• Input: 24 VDC only
• Consumption: Controller + modules (varies)
• Up to 16 I/O modules per controller
• Hot-swappable modules (some models)
I/O Expansion Stack Architecture
Visual guide showing how to scale from 4 I/O points to 256 I/O points using modular expansion. See automatic detection and DIN rail stacking design.
| Feature | Integrated Type | Configurable Type |
|---|---|---|
| Form Factor | Single all-in-one device | Controller + I/O modules |
| I/O Expandability | Fixed (cannot add I/O) | Up to 16 modules per controller |
| Installation Time | Faster (plug-and-play) | Slightly longer (module assembly) |
| Initial Cost | Lower | Higher (controller + modules) |
| Long-Term Cost | Higher if needs change | Lower (add modules as needed) |
| Typical I/O Count | 8-16 points | 20-256 points |
| Best Application | Small fixed systems | Large or growing systems |
Still unsure? Rule of thumb: If you need less than 20 I/O points and won't expand later, choose Integrated Type. If you need 20+ points or might add sensors in the future, choose Configurable Type.
8 Reasons Engineers Choose Industrial-Grade Controllers Over Custom Solutions
You could build a custom solution with consumer-grade boards and programming. But industrial applications require proven reliability in real factory environments—here's what makes the difference.
-20°C to 60°C Operation
Unlike consumer electronics (0°C to 40°C operating range), M2M Controllers operate reliably in harsh industrial temperatures. Install near heat sources, outdoors, or cold storage facilities—continuous reliable operation.
Tested: 500+ hours at -20°C, 1000+ hours at 60°CEMI/Noise Immunity Built-In
All digital inputs/outputs are opto-coupler isolated. Factory floor noise from motors, VFDs, and welders won't cause false triggers or data corruption. Sleep better at night.
Isolation: 2500Vrms (consumer boards: typically 0V isolation)Standard Industrial Installation
Mount on 35mm DIN rail just like PLCs, power supplies, and terminal blocks. Professional industrial enclosure with proper vibration and shock resistance.
Vibration: 2.0G / Shock: 15G (forklift-proof)Web-Based Configuration
Configure everything through web browser. No Python scripts to maintain. No Linux command line. Your operators can modify HMI screens and add sensors without calling IT.
Training time: 2 hours (not 2 weeks of Python courses)Professional SCADA Interface
Drag-and-drop 37 UI components (gauges, trend graphs, buttons, sliders, alarms). Create multi-screen HMI systems comparable to expensive SCADA licenses—included free with every controller.
Value: Replaces SCADA software licensesFlowchart Programming
Need control logic? Use VTC (Visual Task Control) flowchart editor. Drag "Read Sensor", "If-Then Logic", "Send Email Alert" blocks. No Ladder Logic or Python required.
96 pre-built function blocks availableNo Expensive Network Switch
Connect multiple controllers via daisy-chain (controller 1 → controller 2 → controller 3). Reduces wiring cost and eliminates single point of failure from central switch.
Savings: No HUB/switch required per locationLong-Term Availability
CONTEC maintains 10-year minimum product lifecycle for industrial continuity. Consumer-grade boards often see model changes every 2 years. Plan your system with confidence—spare parts remain available throughout product lifecycle.
Policy: 10-year minimum product lifecycleM2M Controllers aren't just "industrial IoT devices"—they're complete systems designed for engineers who need reliable solutions, not experimental prototypes. One device. One vendor. One support contact. Done right.
11 M2M Controller Models: Find Your Perfect Match
Each model shares the same core functionality (data acquisition, local storage, web HMI, cloud transmission). Choose based on your I/O requirements and communication protocols.
Integrated Type - All-in-One Devices (8 Models)
CPS-MC341Q-ADSC1-111
"Swiss Army Knife" Configuration
Best For: Mixed I/O applications, small to medium systems (under 20 points)
CPS-MC341-ADSC1-931
"Smart Manufacturing Ready"
Best For: CNC machine monitoring, Industry 4.0 systems, OPC UA/MTConnect integration
CPS-MC341-ADSC1-111
"Reliable Workhorse"
Best For: Budget-conscious projects, standard data logging, small-scale monitoring
CPS-MC341-ADSC2-111
"Serial Device Gateway"
Best For: Multiple RS-485 device networks, Modbus sensor aggregation, multi-zone monitoring
CPS-MC341-DS1-111
"High-Density Digital"
Best For: On/off sensor monitoring (limit switches, proximity sensors), discrete signal control
CPS-MC341-DS11-111
"Legacy Device Bridge"
Best For: Legacy equipment with RS-232C (barcode scanners, scales, printers), retrofitting old machinery
CPS-MC341-DS2-911
"Automotive & Mobile Equipment"
Best For: Automotive testing equipment, mobile machinery (construction, agriculture), CAN bus device integration, vehicle telematics
CPS-MC341-A1-111
"High-Resolution Analog"
Best For: Analog sensor arrays (temperature, pressure, flow, level), process control feedback loops, high-accuracy voltage measurements, testing and quality control data acquisition
All 11 Models Shown Above
Still not sure which controller fits your application? Our team can help you select the right model based on your I/O requirements, connectivity needs, and budget.
Which M2M Controller Model Is Right for Your Application?
Follow this decision tree to select the optimal controller from 11 models based on your I/O requirements, expansion needs, and protocol support. Reduce selection time from 2-3 weeks to 15 minutes.
Model Selection Decision Tree
Interactive flowchart guiding you through 11 M2M Controller models based on your I/O requirements, expansion needs, and protocol support. Find your perfect match in minutes.
Still unsure which model to choose? Contact our technical team with your application details (sensor types, I/O count, protocols needed) and we'll recommend the best-fit controller within 24 hours. No obligation, no sales pressure—just honest technical guidance.
Complete Technical Specifications Across All Models
Common specifications apply to all models unless noted otherwise. Use this reference for design, installation planning, and system integration.
• Range: -20°C to 60°C
• Storage: -30°C to 70°C
• Range: 10% to 90% RH (non-condensing)
• 2.0G (10 to 60Hz, X/Y/Z axes)
• 15G (11ms pulse, X/Y/Z axes)
• DIN rail (35mm) or fixed mounting with screws
• Integrated Type: 188.0 × 78.0 × 30.5 mm (W × D × H)
• Configurable Type: Controller 44.7 × 94.7 × 124.8 mm (W × D × H)
• Each I/O module adds 12.5-25mm width
• Fanless convection cooling (no moving parts)
• CE marking (EMC Directive, RoHS compliant)
• UKCA marking
Need CAD drawings, wiring diagrams, or dimensional specs?
8 Industries Already Using M2M Controllers to Solve Real Problems
From factory floors to agricultural fields, M2M Controllers deliver reliable data collection in harsh environments. Here's how different industries deploy these systems.
Smart Manufacturing / Industry 4.0
Monitor multiple production lines from one dashboard. Collect machine status, cycle times, reject counts, and OEE metrics. Send real-time data to MES/ERP systems via OPC UA or MQTT.
Energy Management
Track power consumption, runtime hours, and operating efficiency of HVAC, chillers, and air compressors. Identify energy waste patterns and optimize operating schedules.
Water & Wastewater Treatment
Remote monitoring of pumping stations, water tanks, and treatment processes. Collect level, flow, pressure, and water quality data from multiple remote sites.
Building Automation
Integrate HVAC, lighting, access control, and utility meters into one monitoring system. Reduce energy costs and improve occupant comfort.
Smart Agriculture
Monitor soil moisture, temperature, humidity, and light levels. Automate irrigation, ventilation, and fertilizer injection based on real-time conditions.
CNC Machine Tool Monitoring
Capture machine operating status, alarm codes, program numbers, and cycle times from FANUC, Mitsubishi, or MAZAK CNC controllers. Send data to MES or cloud dashboards.
Cold Chain / Temperature Monitoring
Continuous temperature monitoring of refrigerated warehouses, cold storage rooms, and transport containers. Automatic email/SMS alerts when temperature exceeds limits.
Predictive Maintenance
Track motor vibration, bearing temperature, and runtime hours to predict failures before they happen. Schedule maintenance based on actual condition, not fixed intervals.
What do all these applications have in common? Harsh environments, remote locations, and the need for reliable data without expensive custom programming. That's exactly where M2M Controllers excel.
From Box to Data Collection in 4 Simple Steps
No programming experience required. No software installation on your PC. Just a web browser and 30 minutes. Here's exactly how to go from unboxing to live dashboards.
Mount & Wire the Controller
Install the M2M Controller on a standard 35mm DIN rail in your electrical panel. Connect power and I/O terminals. Takes about 10 minutes.
- Hook the top of the controller onto the rail
- Push the bottom until you hear a click
- Tug gently to verify it's locked in place
- For daisy-chaining multiple controllers: connect LAN OUT port to next controller's LAN IN port (up to 16 units)
- Integrated Type: 12-24 VDC, ±10% tolerance (9 watts typical, 15 watts max)
- Configurable Type: 24 VDC only, ±10% tolerance (12 watts typical, 20 watts max)
- Connect + wire to 24V+ terminal, - wire to GND terminal (clearly labeled on housing)
- Double-check polarity before powering on (reverse polarity protection built-in but best to avoid)
- Power on → PWR LED (green) lights up, RUN LED (orange) blinks during boot, LAN LED (green) blinks when connected
- Digital Inputs (DI): Connect dry contact sensors (limit switches, push buttons) to DI+ and COM terminals. No external power needed—controller supplies 24V internally.
- Digital Outputs (DO): Connect relay coils, indicator lights, or solenoid valves to DO and COM terminals. Max 2A per channel. Use external power for high-current loads.
- Analog Inputs (AI): Connect 4-20mA sensors to AI+ and AI- terminals. For 0-10V sensors, use voltage input terminals (AI_V+ and GND). Polarity matters!
- Counter Inputs: Connect proximity sensors, encoders, or flow meters to CNT terminals. Supports up to 10kHz pulse frequency.
- RS-485 Serial: Connect Modbus RTU devices (energy meters, motor drives) to A+, B-, and GND terminals. Use twisted-pair shielded cable. Add 120Ω termination resistor at both ends of long cable runs (>50 meters).
Built-In I/O Wiring Examples
Detailed terminal connection reference for digital inputs, digital outputs, analog inputs, and counter inputs. See field device wiring for common sensors and loads.
- Label all wires before connecting (printer labels or masking tape work great)
- Use ferrule terminals for solid connections (included in box)
- Keep AC power wires separate from DC signal wires (at least 10cm apart) to avoid interference
- Take a photo of your wiring—helpful for troubleshooting later
Connect to Network & Access Web Interface
Plug in an Ethernet cable and the controller will automatically get an IP address from your router (DHCP). Then access the built-in web interface from any browser.
- Connect Cat5e or Cat6 cable from controller's LAN port to your network switch/router
- LAN LED will blink green when connected
- Controller automatically requests an IP address via DHCP (takes 5-10 seconds)
- Log in to your router admin page (usually 192.168.1.1 or 192.168.0.1)
- Go to Status → DHCP Client List or Attached Devices
- Look for device with hostname 'CPS-MC' or MAC address starting with 00:90:A9
- Note the IP address (e.g., 192.168.1.150)
- Download the free tool from CONTEC's support website (Windows/Mac versions available)
- Run the tool—it scans your LAN subnet and lists all CONTEC devices
- Shows IP address, MAC, firmware version, and model number
- Click 'Open Web Interface' button to launch browser automatically
- Disconnect controller from network
- Connect Ethernet cable directly from controller to your laptop
- Controller defaults to 192.168.250.1 in direct-connect mode
- Set your laptop's Ethernet adapter to manual IP: 192.168.250.100, subnet 255.255.255.0
- Open browser and go to http://192.168.250.1
- Supported browsers: Chrome, Edge, Firefox, Safari (no Internet Explorer)
- Navigate to http://[controller-ip-address] (e.g., http://192.168.1.150)
- Login screen appears—default credentials:Username: admin
Password: contec - After first login, you'll be prompted to change the password (highly recommended for security)
- Go to Settings → Network → LAN Settings
- Change from DHCP to Static IP
- Enter IP address, subnet mask, and gateway (e.g., 192.168.1.150, 255.255.255.0, 192.168.1.1)
- Click Save → Controller reboots and applies new IP
- Reconnect using the new static IP
- Write down the IP address and password somewhere safe (tape a label on the panel door)
- Use descriptive hostnames if your router supports it (e.g., 'factory-line-1-controller')
- Configure firewall rules if you need remote access from outside your LAN
- Bookmark the controller's IP in your browser for quick access
Configure I/O Channels & Data Logging
Tell the controller what each sensor does and how to interpret the signals. Set up data logging to store historical data locally. No coding—just fill in forms.
- Go to Settings → I/O Configuration → Digital Inputs
- For each DI channel you wired:
- Enable: Check the box
- Tag Name: Give it a meaningful name (e.g., 'Door_Open_Sensor', 'E-Stop_Status')
- Debounce Time: Default 10ms works for most sensors (increase to 50ms for noisy mechanical switches)
- Inverted Logic: Check if sensor is normally-closed (NC) instead of normally-open (NO)
- Click Save
- Go to Settings → I/O Configuration → Digital Outputs
- For each DO channel:
- Enable: Check the box
- Tag Name: e.g., 'Alarm_Buzzer', 'Valve_1_Control'
- Default State: Choose ON or OFF for power-up behavior
- Safety Mode: Enable to force outputs OFF if controller loses network connection or crashes (critical for safety applications)
- Click Save
- Go to Settings → I/O Configuration → Analog Inputs
- For each AI channel:
- Enable: Check the box
- Tag Name: e.g., 'Tank_Level_Sensor', 'Inlet_Pressure'
- Input Type: Select 4-20mA or 0-10V (must match your sensor)
- Scaling: Convert raw signal to engineering units:Example: Pressure Sensor (4-20mA = 0-150 PSI)
- Input Min: 4.0 (mA) → Output Min: 0.0 (PSI)
- Input Max: 20.0 (mA) → Output Max: 150.0 (PSI)
- Unit: PSI
- Now when sensor outputs 12mA, controller displays 75 PSI
Example: Temperature Sensor (4-20mA = 0-100°C)- Input Min: 4.0 (mA) → Output Min: 0.0 (°C)
- Input Max: 20.0 (mA) → Output Max: 100.0 (°C)
- Unit: °C
- Click Save
- Go to Settings → I/O Configuration → Counter Inputs
- For each counter channel:
- Mode: Select Up Counter (totalizer), Frequency (Hz), or Pulse Width (ms)
- Scaling Factor: For flow meters, enter pulses-per-liter (e.g., 1 pulse = 0.1 liters)
- Reset Option: Enable manual reset button in HMI if needed
- Go to Settings → Data Logging → Log Configuration
- Select which tags to log (check boxes next to tag names)
- Log Interval: Choose from 1 second to 1 hour
- Fast-changing values (motor speed, vibration): 1-10 seconds
- Slow-changing values (temperature, tank level): 1-5 minutes
- Efficiency tip: 1-minute intervals are a good starting point
- Trigger Mode:
- Continuous: Logs at fixed intervals (most common)
- On Change: Only logs when value changes by a threshold (saves storage space)
- On Alarm: Only logs when alarm conditions are met
- Format: CSV (readable in Excel) or Binary (more compact)
- Circular Buffer: Enable to overwrite oldest data when storage is full (prevents storage errors)
- Storage Estimate:Example: 100 tags @ 1-minute sampling = ~8GB/year
With 16GB onboard storage = ~2 years of data
With 1-second sampling = ~60 days of data - Click Save & Start Logging
- Use descriptive tag names with no spaces (use underscores: Tank_Level_1, not 'Tank Level 1')
- Start with slower log intervals (1 minute) and speed up later if needed—prevents filling storage too fast
- Test analog input scaling before deploying: manually apply a known signal (e.g., 12mA = 50% of range) and verify display
- For pressure/temperature sensors, use 'On Change' trigger with 2% threshold to save storage (if value doesn't change, don't log)
Create HMI Dashboard & Start Cloud Data Transmission
Build a live monitoring dashboard with drag-and-drop widgets (no coding). Then configure MQTT or HTTP to send data to your cloud platform or SCADA system.
- Go to HMI Editor → New Screen
- Drag-and-drop components from the palette (37 types available):
- Gauges: Circular, horizontal bar, vertical tank level
- Charts: Line graph (trends), bar chart, pie chart
- Buttons: Toggle output, reset counter, acknowledge alarm
- Indicators: LED (on/off), numeric display, text label
- Images: Equipment photos, process flow diagrams
- Configure each widget:Example: Circular Gauge for Tank Level
- Data Source: Select tag 'Tank_Level_Sensor'
- Min/Max: 0 to 100 (% or liters, based on your scaling)
- Color Zones:
- 0-70%: Green (normal)
- 70-90%: Yellow (warning)
- 90-100%: Red (critical)
- Update Rate: 1 second (real-time)
Example: Line Chart for Temperature Trend- Data Source: Select up to 4 tags (e.g., Temp_Sensor_1, Temp_Sensor_2)
- Time Range: Last 1 hour, 8 hours, or 24 hours
- Y-Axis: Auto-scale or fixed range (0-100°C)
- Line Colors: Different color for each tag
- Arrange widgets on screen (resize, align, group)
- Click Save → Screen is now live at http://[controller-ip]/hmi
- Access from any device on your network (laptop, tablet, smartphone)
- Go to Settings → Cloud Integration → MQTT Configuration
- Enter your MQTT broker details:Example for AWS IoT Core:
Protocol: MQTTS (TLS/SSL)
Broker Address: a1b2c3d4e5f6g7.iot.us-east-1.amazonaws.com
Port: 8883
Client ID: factory-line-1-controller
Topic: factory/line1/sensors
Username: (leave blank if using TLS certificates)
Password: (leave blank if using TLS certificates)
TLS Certificate: Upload .crt and .key files from AWS IoT console
Message Format: JSON
Publish Interval: 10 seconds
QoS Level: 1 (at least once delivery)Example Payload (Auto-Generated JSON):
{ "timestamp": "2024-01-15T10:30:45Z", "device_id": "CPS-MC341-001", "tags": { "Tank_Level_Sensor": 75.5, "Inlet_Pressure": 120.3, "Temperature_1": 68.2, "Pump_Running": true } } - Click Test Connection (controller will attempt to connect and report success/failure)
- If successful, click Enable → Data starts transmitting immediately
- Go to Settings → Cloud Integration → HTTP Configuration
- Enter your REST API endpoint:Example:
Method: POST
URL: https://api.yourplatform.com/v1/data/ingest
Headers:
  Content-Type: application/json
  Authorization: Bearer YOUR_API_KEY_HERE
Body: (same JSON format as MQTT payload)
Publish Interval: 30 seconds
Retry on Failure: 3 retries with 5-second delay - Click Test Request (controller sends sample data and shows HTTP response code)
- If you get 200 OK, click Enable
- Start with a simple HMI screen (4-5 components) before building complex dashboards
- Use MQTTS (with TLS) instead of plain MQTT for production—prevents eavesdropping
- Test cloud connectivity with a public MQTT broker (broker.hivemq.com) before configuring your actual cloud platform
- If you have intermittent internet, enable 'Store & Forward' mode—controller buffers data locally and sends when connection returns
Congratulations! Your M2M Controller is Now Operational
Your system is now collecting data from sensors, logging locally to internal storage, transmitting to your cloud platform, and displaying live values on the HMI dashboard. Total setup time: ~30-45 minutes.
Troubleshooting Common Issues
Run into a snag? These are the 4 most common setup issues and their solutions. 95% of installation problems are solved by one of these fixes.
Complete Software Ecosystem: HMI, VTC, Cloud Integration & SDKs
M2M Controllers include built-in software tools for HMI creation, flowchart programming, and cloud integration. No separate software licenses required. Everything runs on the controller itself—just use your web browser to configure.
Web-Based HMI Builder - No SCADA License Required
Create professional operator interfaces with drag-and-drop simplicity. 37 pre-built UI components (gauges, graphs, buttons, sliders, alarms) let you build multi-screen dashboards in hours, not weeks. Access from any device with a web browser—PC, tablet, smartphone. No client software installation needed.
Web HMI Component Gallery - 37 UI Components
Explore all 37 drag-and-drop components organized in 6 categories: Basic, Gauges, Charts, Tables, Images, and Advanced. See data binding options and access control features.
Gauges & Meters
Circular gauges, horizontal/vertical bar meters, thermometer-style displays. Configurable thresholds (green/yellow/red zones), needle styles, and size presets.
Real-Time Trend Graphs
Line charts, area charts, multi-axis plots. Display up to 8 tags on one graph. Time ranges: last 1 hour, 8 hours, 24 hours, 7 days. Auto-scroll or static view. Export as PNG/CSV.
Digital Numeric Displays
Large numeric readouts with configurable font size, decimal places, and units. Color-coded based on value thresholds (e.g., green normal, red alarm).
LED Indicators & Status Lights
Colored LEDs (red/yellow/green), flashing/steady modes, custom labels. Mimic physical indicator lights on control panels.
Buttons, Switches & Sliders
Push buttons (momentary/toggle), ON/OFF switches, slider controls (0-100%). Write values to digital outputs or trigger VTC tasks. Optional confirmation dialogs for safety.
Alarm Tables & Event Logs
Scrolling list of active alarms and historical events. Timestamp, alarm message, acknowledge button, severity color-coding (critical/warning/info).
Multi-Screen Support
- Unlimited screens (depends on memory)
- Navigation buttons / menu bars
- Screen switching logic based on conditions
- Home screen auto-load
Responsive Design
- Auto-scales to screen size (PC, tablet, phone)
- Portrait / landscape orientation support
- Touch-friendly UI (20mm minimum button size)
- Mouse and touch gesture support
Security & User Management
- Multi-user access (read-only, operator, admin)
- Password-protected screens
- Action confirmation dialogs
- Audit log (who did what, when)
No Client Software Needed
- Runs in any web browser (Chrome, Edge, Firefox, Safari)
- No Java, Flash, ActiveX plugins required
- Works on Windows, macOS, Linux, iOS, Android
- Bookmark URL for instant access
Frequently Asked Questions About M2M Controllers
Real questions from engineers, facility managers, and system integrators. If you don't see your question here, contact our technical support team—they respond within 24 hours.
Start by counting your I/O requirements:
If you need LESS THAN 20 I/O points and won't expand later:
→ Choose Integrated Type (fixed all-in-one device)
- • Mixed I/O (analog + digital)? → CPS-MC341Q-ADSC1-111 or CPS-MC341-ADSC1-111
- • Only digital I/O (on/off sensors)? → CPS-MC341-DS1-111
- • Only analog I/O (4-20mA sensors)? → CPS-MC341-A1-111
- • Need OPC UA / MTConnect? → CPS-MC341-ADSC1-931
If you need MORE THAN 20 I/O points or might expand later:
→ Choose Configurable Type (modular expandable system)
- • Standard features? → CPS-MCS341-DS1-111
- • Need OPC UA / MTConnect? → CPS-MCS341-DS1-131
- • Remote location without internet? → CPS-MCS341G5-DS1-130 (4G LTE)
Still unsure? Contact sales with your I/O list—we'll recommend the best fit.
Didn't find your answer? Our technical team is here to help.
Transform Your Factory Floor Into a Smart, Data-Driven System
No programming required. No monthly per-tag fees. No cloud dependency. Just reliable industrial IoT that works. Choose from 11 M2M Controller models designed for real-world manufacturing environments.