Got it 👍 — you’re using an M580 PLC with remote I/O on a loop topology.
To make sure I help you correctly — could you tell me a bit more about your setup or goal? For
example:
Are you using Remote I/O via Ethernet (Ethernet RIO) or via a Remote Drop on X80
bus coupler (e.g. BME CRA 312 10/20)?
By “loop remote I/O”, do you mean dual-ring Ethernet RIO topology (fiber or copper),
or are you referring to current loops (4–20 mA) on the I/O modules?
What do you want to do or troubleshoot — configuration, communication, redundancy,
or diagnostics?
Once I know that, I can show you the correct network architecture, Control Expert setup, and
diagnostic steps (for example, how to configure the Ethernet RIO in a ring or daisy-chain loop).
You said:
I have use BME CRA 312 which is connection is in ring
ChatGPT said:
Thought for 13s
Great — thanks for confirming you’re using the BME/BMX CRA-312 adapter in a ring (daisy-
chain) Ethernet RIO topology with the M580. Below I’ve put together a practical checklist and
actionable steps you can follow (physical + Control Expert + diagnostics + tips). I included the
most important references from Schneider’s docs so you can look up details.
Quick checklist (what to verify right away)
1. Each remote drop has a BME/BMX CRA-312 adapter installed in slot 0. Schneider
Electric+1
2. The M580 CPU has Ethernet I/O (RIO) scanner service enabled (so it will poll the RIO
drops). Distributor Data Solutions
3. Physical ring wiring: use the CRA-312 ring ports to form the daisy-chain/ring (cable type
per manual) and check LEDs for link/status. Schneider Electric+1
4. Firmware/Control Expert project matches the hardware revision (firmware
compatibility). Distributor Data Solutions
Physical wiring & LEDs (hardware checks)
Use the CRA-312 Ethernet ports in the order the manual recommends to build the
ring/daisy chain. If you have ConneXium switches/DRS, follow the topology examples in
the planning guide. Distributor Data Solutions+1
Check module LEDs: RUN/ERR/NETSTATUS/ETH MS etc. — they quickly show link,
module status and recoverable vs fatal errors. LED behavior and patterns are documented
in the adapter and M580 manuals. [Link]+1
If a cable is broken, the CRA-312 with RSTP support will allow the ring to re-route
automatically (redundancy), so expect a short switch-over time; verify RSTP behavior in
the adapter parameters. Distributor Data Solutions+1
Control Expert (software) — recommended
steps
1. In your Control Expert project, confirm the CPU supports RIO and that the RIO scanner
service is enabled (EIO Bus). Add the remote drops as racks under the EIO bus.
Distributor Data Solutions
2. Double-click the CRA-312 adapter in the project to access configuration tabs: RSTP,
SNMP, Service port, Parameters, Time stamping. Configure RSTP and any timeouts
there. Distributor Data Solutions
3. Set the device name / starting address and reserve slots correctly for X80 platform
modules (slot 0 is reserved for CRA). Save and download to the CPU. RS Components+1
4. If you need deterministic behaviour, use the recommended scan settings and make sure
I/O sync settings are applied per the RIO docs. [Link]
Diagnostics & troubleshooting
Start with LEDs on the CRA-312 and CPU (NET STATUS, ETH MS). Then use
Control Expert online diagnostics (RIO diagnostics pages) to view RSTP status and
connection health. [Link]+1
Ping the adapter’s IP (if it has a device IP) and check EtherNet/IP identity objects (some
adapters expose diagnostics via CIP). MRO Electric
If you see repeated re-routing or flapping: check cable quality, connectors, and remove
any network loops outside the intended RIO ring. Verify firmware versions across drops.
Distributor Data Solutions+1
Useful project tips / best practices
Keep CRA-312 firmware and the CPU firmware compatible — check the release notes in
Schneider docs. Distributor Data Solutions+1
Use the RSTP configuration tab in Control Expert to review bridge parameters — the
RIO ring uses this for redundancy; you typically do not need to manually create spanning
trees for simple RIO rings. Distributor Data Solutions+1
If you have lots of remote drops, consider sub-rings or using ConneXium DRS switches
per Schneider topology guides for better manageability. Distributor Data Solutions
References (for deeper reading)
Schneider product page / datasheet for BMX/BME CRA-312. Schneider Electric+1
Modicon M580 RIO modules & Control Expert configuration (RIO chapters). Distributor
Data Solutions+1
System Planning Guide and topology examples (complex topologies, sub-rings).
Distributor Data Solutions
If you want, I can:
Give a step-by-step Control Expert walkthrough to add a CRA-312 drop in your
existing project (I can list the exact clicks/fields to set).
Draw a wiring/logic diagram for the ring and point out where LED/status changes
happen.
Help troubleshoot a specific symptom (e.g., a particular LED pattern, a drop showing
offline in Control Expert, or frequent ring re-routing).
Which of those would be most helpful now?
You said:
I face a problem when 2 Ethernet connection is lost and when it restore Ethernet connection it
will activation output PLC and I have check PLC program it is normal Can you check this case ?
ChatGPT said:
Good — that’s an important and subtle issue 👍
Let’s carefully analyze your situation step by step:
🔧 Your system
M580 PLC (main CPU with Ethernet RIO scanner)
Remote I/O drop(s) with BME CRA 312 10/20 adapter
Ring topology (dual Ethernet cables between CPU and CRA modules)
Problem:
When both Ethernet links in the ring are lost → communication drops (expected).
When the ring restores (links reconnected) → some outputs briefly activate (turn ON)
even though your PLC logic is normal.
🧩 Root cause possibilities
Let’s separate possible causes into hardware, configuration, and logic effects.
1️⃣ RIO Recovery Behavior
When the Ethernet RIO link is lost, the CRA-312 enters a fallback mode:
It freezes outputs at last state (default), or
Forces outputs to a predefined fallback value (e.g. OFF) — depending on your
configuration.
When the link restores, the CRA-312:
Re-synchronizes with the PLC.
Then applies the current control data from PLC to its output modules.
🧠 If the CRA module’s fallback or reinitialization sequence is not configured properly, outputs
may briefly go to their fallback state before being refreshed by the CPU scan.
2️⃣ Output Module Setting (Fallback Values)
Each output module (e.g., BMX DDO 3202) has its Fallback mode setting in Control Expert:
Hold Last Value
Set to 0
Set to 1
➡️When communication is lost and then restored, the transition from fallback → normal
operation can cause momentary output changes (a glitch).
3️⃣ Delay in synchronization
After RIO communication recovers, there is a few milliseconds delay before the first valid I/O
exchange completes. During that time, if your logic uses latched memory or outputs directly
linked to %Q, the hardware output may briefly reflect whatever fallback configuration is stored
in the CRA or I/O module.
4️⃣ PLC logic side
Even if your logic doesn’t explicitly turn outputs ON, if your outputs (%Qx) are used as direct
variables without intermediate memory buffering, any resync or “false good” frame from
CRA-312 might drive the outputs momentarily.
✅ How to check and fix
Let’s go through diagnostic and corrective steps.
🧪 Step 1: Check fallback configuration
In Control Expert:
1. Go to each RIO drop → CRA-312 → Fallback tab
2. Review the setting for Output modules:
o Choose Hold Last Value for safety-critical signals
o Or Set to 0 if you want all outputs OFF on comms loss
3. Download again to the PLC & CRA.
🧪 Step 2: Check "Reconfiguration behavior"
In RIO drop properties → Advanced → Reconfiguration behavior:
Make sure “Reapply I/O image after reconnection” is enabled.
This ensures that PLC re-sends output image immediately after link restoration.
🧪 Step 3: Observe CRA-312 diagnostic LEDs
During restore:
RUN / ERR / I/O LEDs can tell if CRA reboots or only resyncs.
If CRA restarts fully (e.g. power glitch), outputs may also go through “OFF → ON →
OFF” momentarily.
🧪 Step 4: Buffer outputs in logic
For critical outputs, use an intermediate memory (%M):
%M100 := <your logic>;
IF RIO_OK THEN
%Qx := %M100;
ELSE
%Qx := 0;
END_IF;
Then drive the actual output only when the RIO_OK flag is true (use the RIO drop status bit or
system variable).
🧪 Step 5: Check firmware versions
Older CRA-312 firmware had known issues with output glitching after RIO reconnection.
👉 Make sure both:
CPU firmware and
CRA-312 firmware
are up to date and compatible.
🔍 You can help me check further
Can you tell me:
1. The model of the CPU (e.g. BME P58 2040)
2. The number of RIO drops
3. The firmware version of your CRA-312 (shown in Control Expert “Module Info”)
4. What type of output module you use (e.g. BMX DDO 3202K, DDO 1602K, etc.)
5. What fallback mode you have currently set
Then I can help you pinpoint the exact cause — for example, whether it’s a known firmware
issue or a fallback configuration issue.
Would you like me to show you the exact place in Control Expert where you set the fallback
value for outputs?
You said:
what is best indicator in tradeview ?
ChatGPT said:
Good question 👍 — there’s no single “best” indicator in TradingView for all traders, but there
are a few that consistently work well depending on your strategy (trend, swing, scalp, long-
term).
Let’s go through this step-by-step 👇
🧭 1️⃣ If you trade trend-following
You want to follow big moves and avoid sideways traps.
✅ Best indicators:
EMA (Exponential Moving Averages) → EMA 20, 50, 200
o Trend direction: price above 50 EMA → uptrend
o Crossovers (EMA 20 > 50) → possible buy signal
MACD (Moving Average Convergence Divergence)
o Confirms momentum and crossover timing
ADX (Average Directional Index)
o ADX > 25 = strong trend
📈 Example setup (TradingView):
EMA20, EMA50, EMA200 + MACD + ADX
💎 2️⃣ If you trade breakouts or volatility
You need to catch moves when price breaks out of ranges.
✅ Best indicators:
Bollinger Bands (BB) → breakout when candle closes outside band
Volume / Volume Profile / OBV → confirm breakout strength
RSI (Relative Strength Index) → confirm not overbought before entry
📈 Example setup:
Bollinger Bands + RSI + Volume
🕰️3️⃣ If you do scalping or short-term
You want fast signals for quick profits.
✅ Best indicators:
EMA 9 and 21 crossovers
Stochastic RSI → overbought/oversold
VWAP (Volume Weighted Average Price) → intraday trend
SuperTrend → quick trend reversal indicator
📈 Example setup:
SuperTrend + EMA9/21 + Stochastic RSI + VWAP
📊 4️⃣ If you do swing or spot investing
You look for strong entry points with confirmation.
✅ Best indicators:
RSI (14) → below 30 = oversold, above 70 = overbought
MACD → momentum confirmation
Volume / OBV → check accumulation or distribution
EMA 50 & 200 → trend direction
📈 Example setup:
RSI + MACD + Volume + EMA50/200
🧠 Pro tip: Combine “trend + momentum + volume”
The best setups usually combine:
Trend → (EMA or SuperTrend)
Momentum → (RSI or MACD)
Volume → (Volume, OBV, or Volume Profile)
⚙️Bonus for crypto traders
If you trade crypto (like BTC, SNX, ETH):
Volume Profile (Visible Range) → shows where big players buy/sell
Funding Rate / Open Interest (if futures) → shows crowd bias
Market Cipher / LuxAlgo / TrendMagic (premium or script-based indicators) are
popular in TradingView.
Would you like me to build a ready-to-use indicator setup (for example, “best for crypto swing
trading” or “best for short-term scalping”) — I can show you which exact indicators to add in
TradingView and how to use each one step-by-step?