RailBOX RB 23XX — Configuration Reference

Reference documentation for RailBOX RB 2300 and RB 2310 DCC Wi-Fi sound decoders. This document is not tied to the BigFred or Loco runtime; it is intended as a future data source for decoder configuration.

Decoder highlights: DCC addresses 1–10239, F0–F28 function outputs, F0–F63 sounds, 28 or 128 speed steps, RailCom, Back-EMF, 9 function outputs + 3 logic outputs, Wi-Fi sound upload, map.txt / logic.txt / cv.txt configuration files.

Acceleration, deceleration, and speed

Shunting mode

Output mapping, brightness, and lighting effects

Digital coupler (uncoupler)

Smoke generator

Volume regulation

Sound pack file naming

D — Full CV table

E — Forum insights (RailBOX)

1. Acceleration, deceleration, and speed

1.1 Basic momentum (CV #3 and CV #4)

Acceleration and deceleration are configured independently.

Firmware ≥ 1.3: NMRA encoding changed — when migrating from older firmware or ESU-style values, convert: new = 1020 / old (see Appendix E).

1.2 Speed curve (CV #2, #5, #6)

Together, CV #2, #5, and #6 define the locomotive speed characteristic (NMRA-style 3-point curve).

1.3 Speed steps and direction (CV #29)

1.4 Back-EMF and PID (CV #50–#55, #58–#60)

Factory defaults are tuned for typical HO motors. Adjust for specific motor types.

PID coefficients

KFF_A / KFF_D (CV #54, #55) mainly matter for high acceleration and deceleration values.

Back-EMF system

CV #60 differs from CV #5: CV #5 limits the speed curve; CV #60 sets the Back-EMF regulation voltage at maximum speed.

1.5 Start delay (CV #63)

1.6 Consist address (CV #19)

1.7 Persisting motor CVs via cv.txt

Important motor CVs can be stored in a cv.txt file uploaded with the sound pack. After a factory reset the decoder reloads these defaults:

cv1=3
cv50=40
cv51=130

2. Shunting mode

2.1 Function key assignment (CV #165)

2.2 Shunting momentum (CV #61, #62)

Separate acceleration and deceleration times apply while shunting mode is active:

Factory defaults give faster response in shunting than normal running (CV #3 = 34, CV #4 = 25).

2.3 Shunting in logic.txt

Shunting mode (typically F6) is widely used as a trigger function in sound and lighting automation:

Use the web generator at railbox.pl/sounds to build custom shunting logic.

2.4 Default PIKO mappings using F6

EP08 (PluX22):

AUX5:F6>,F27>
AUX6:F6<,F27<

BR232 (PluX22):

AUX5:F5<>
AUX6:F6>,F27>
AUX7:F6<,F27<

F6 switches directional AUX outputs during shunting (e.g. shunting-step lights).

3. Output mapping, brightness, and lighting effects

3.1 Physical outputs

NEM652 pin assignment (RB 2300):

21MTC (RB 2310): CV #209 selects connector standard — 0 = NEM660 (AUX3/AUX4 as logic outputs), 1 = MKL (AUX3/AUX4 as power outputs).

3.2 Output mapping — map.txt and mobile app

Output-to-function assignment is not done via NMRA CV #33–#46. Instead:

1. map.txt file uploaded via Wi-Fi web interface or RailBOX: Railroad Control app.
2. Mobile app — Loco Editor → Edit CV → OUTPUTS MAPPING → Read/Write on programming track.

Syntax:

AUXn:Fn>,Fn<,Fm<>
F0F:F0>          # forward headlight
F0R:F0<          # reverse headlight

The same output can map to several functions and directions. When mixing direction modes on one output, use only <> and leave arrows blank.

Web generator: railbox.pl/sounds

NEM652 note: Decoders without a preloaded map.txt assign outputs sequentially from F0 by default.

3.3 Lighting effects (CV #112–#118, #212–#215)

Each of the 11 outputs has an independent effect CV:

Base effect values

Effect modifiers (add to base value)

Timing CVs

Factory custom sequences are preloaded in CV #139–#164 (written one byte at a time).

3.4 Brightness (CV #119–#128, #219–#222, #126–#132, #226–#229)

3.5 Dynamic dimming via logic.txt (software ≥ 1.3)

The DIM logic function reduces brightness of a mapped function while a trigger is active:

F6_DIM_F0_V50

Requires logic.txt upload. Generator: railbox.pl/sounds.

3.6 Servos

Up to two servos connect to S1 and S2 terminals (−, +, signal). Set the target output to effect value 9 (Servo mode) in the corresponding effect CV.

4. Digital coupler (uncoupler)

4.1 Wiring

Digital couplers connect between:

• the + (common / LED anode) terminal, and
• a selected function output (external pads on the decoder board, or AUX output on the locomotive PCB).

Two servos and one digital coupler can be installed per the connection diagram in the manual (§4). The coupler may also use a dedicated pad on the locomotive's factory board if available.

Load limits: Observe decoder maximum output current (0.5 A total function outputs; 1 A continuous motor). Avoid short circuits — outputs have protection but external overvoltage can cause damage.

4.2 Output assignment

Assign the coupler to an AUX output via map.txt or the mobile app, e.g.:

AUX4:F7>

No dedicated coupler PWM mode or automatic uncoupling sequence is documented (unlike ESU or ZIMO). Control is on/off through normal function output switching.

4.3 Sound integration

Coupler sounds are triggered via logic.txt rules, e.g.:

F10_LON_F6_ON_D4000

Plays the F10 coupling sound 4 seconds after F6 (shunting mode) is activated.

4.4 Automatic switch-off

Use the lighting effect and output timing features, or logic rules, to limit energisation time. ROCO-style couplers cannot tolerate continuous activation — the manual recommends timed switch-off for digital couplers in the ESU context; apply the same principle by releasing the function key promptly or using logic.txt automation.

5. Smoke generator

The RB 23XX manual does not describe a dedicated smoke generator mode or synchronised smoke control.

Smoke units (e.g. Seuthe) can be wired to any free function output mapped via map.txt, subject to:

• maximum output current (0.5 A total for function outputs),
• appropriate brightness CV for the assigned output (#119–#222),
• effect CV set to 0 (steady output) unless pulsed behaviour is desired.

For speed-synchronised smoke, consider a third-party smoke module with its own control logic, or a different decoder family with dedicated smoke support (e.g. ESU LokSound, ZIMO MS).

Practical note: If the smoke generator is chassis-referenced, wire the second pole to + (U+) rather than ground to avoid half-wave power loss on DCC — same guidance as for other decoder brands.

6. Volume regulation

6.1 Master volume (CV #203)

6.2 Per-function volume (CV #192, #193)

Procedure: Write the function number to CV #192, then set CV #193. Repeat for each function.

6.3 Mute function keys (CV #206, #207)

6.4 Runtime volume via logic.txt (software ≥ 1.3)

The VOL logic function sets all sounds to a specified level while active:

F23_VOL_V50

Reduces all sounds to 50% while F23 is on. Parameter V = target volume percent.

6.5 Sound smoothness (CV #204, #205)

6.6 Logic system disable (CV #208)

Individual automation features can be turned off:

6.7 Sound pack selection (CV #202)

F28 (default Wi-Fi / sound enable, CV #200) must be on for any sound playback or Wi-Fi access. Per-sound levels and assignments are defined inside the uploaded sound pack. Factory sound-slot layouts vary by project — download packs from railbox.pl/sounds.

6.8 Chuff / loop sound frequency (CV #210)

7. Sound pack file naming

Sound files uploaded to the decoder (Wi-Fi web interface or RailBOX app) are assigned to behaviour by filename. Supported formats: PCM, ADPCM, Vorbis (OGG) — see technical parameters in the manual.

This naming scheme is independent of logic.txt automation (Appendix C): filenames define built-in playback rules inside the sound pack; logic.txt adds optional cross-function rules on top.

7.1 Filename structure

F{n}_[S{speed}_][D{delay}_]{TYPE}[{suffix}].wav

Extension: .wav for PCM/ADPCM; OGG files use the same naming with .ogg (e.g. F1_STOP_D3500_EN57.ogg).

Sample rate: Do not mix 16 kHz and 32 kHz ADPCM files in one pack (forum, 2025). 32 kHz ADPCM packs are offered separately on railbox.pl/sounds.

7.2 Playback types

ADPCM and LOOP

For ADPCM files with type LOOP, include parameter _T = real audio length in milliseconds (IMA ADPCM adds trailing silence). Parameter _S = minimum speed 1–100%. Use the converter / emulator from railbox.pl/sounds.

7.3 Worked examples

7.4 Station announcements (INFO / INFONEXT)

Pair INFOn with INFONEXTn for each station index. Firmware ≥ 1.5 behaviour (manufacturer):

Rule: INFONEXTn always plays before INFOn within each station set.

Classic two-key layout (manual / early packs):

Example layout for two stations:

F20_INFO1.wav
F20_INFONEXT1.wav
F20_INFO2.wav
F20_INFONEXT2.wav

Press F20 → INFONEXT1, INFO1, INFONEXT2, INFO2.
Press F21 → INFONEXT2, INFO2, INFONEXT1, INFO1.

7.5 Relation to logic.txt

Both can coexist in one project. Prefer filenames for standard per-function sounds; use logic.txt when one function must trigger another function's sound with explicit delays (L, D, R parameters — see Appendix C).

Appendix A — Configuration files

Upload via Wi-Fi: enable F28, connect to RB2300_XXXXX (password 000000000), browse to http://192.168.4.1.

cv.txt format (manufacturer, forum): lowercase keys, one per line, upload into the sound pack folder (not decoder root):

cv1=35
cv2=160
cv3=70

Values apply when that pack is active; they reload after factory reset if stored in the pack. Use as last resort when the command station cannot program CV #1 (e.g. Roco MultiMaus PoM limitation).

functions.txt: Generate in RailBOX: Railroad Control app — long-press ZASTOSUJ on an existing loco profile (firmware ≥ 1.11.1). Required for automatic loco registration on RB1110 / PIKO WLAN (RailCom Plus / DCCA).

Emulator: Desktop emulator at railbox.pl/sounds previews packs offline — it does not connect to the decoder. After validation, upload the folder of .wav / .ogg files.

Appendix B — Key default logic rules (factory PIKO packs)

EP08:

F2_L1500_ESTOP_D200
F4_BLOCK_F1
F6_BLOCK_F12
F9_BLOCKDRV … F26_BLOCKDRV
F17_L4000_DCL_V300
F21_ACCDCL_V500_L4000
F13_DCL_V200_L4000

BR232:

F2_L1500_ESTOP_D200
F6_BLOCK_F12
F9_BLOCKDRV … F20_BLOCKDRV
F17_L4000_DCL_V300
F19_L4000_ACC_V200
F21_L4000_ACCDCL_V500
F13_DCL_V200_L4000

Appendix C — Logic function reference (logic.txt)

Hall / GPIO input (SW ≥ 1.10.0, CV #64 = 2): prefix I1_ — e.g. I1_TOGETHER_F13_INMOVE, F2_ON_I1_L2000.

SUSI (SW ≥ 1.5): map CLK / DAT in map.txt like other outputs.

Appendix D — Full CV table

Source: manual CV configuration table (pp. 13–17). Output mapping is primarily via map.txt / mobile app — not CV #33–#46.

Address, motor, and speed

CV #28 — RailCom configuration (bit field)

CV #29 — Decoder configuration (bit field)

Lighting effects (CV #112–#118, #212–#215)

Outputs 1–7 use CV #112–#118; outputs 8–11 use CV #212–#215. Range 0–135 each, default 0.

Modifiers (add to base): +16 fade-in (CV #135); +32 fade-in (CV #136); +64 fade-in 500 ms; +128 run custom sequence once.

Brightness per output

Lighting timing and custom sequences

Back-EMF, PID, and shunting

CV #64 — Pin configuration (bit field)

Volume and sound

CV #208 — Logic system disable (bit field)

Connector and misc

LOAD simulation (SW ≥ 1.12): internal parameter LOAD 0–255 rises with motor current and falls when coasting. Formula (manufacturer): LOAD = CV194 × (motor_current / max_current). Tune CV #195 / #196 for response. Use with VOLLOAD, FAN, MINLOAD, TURBO filenames and logic rules.

CV #3 / #4 after SW 1.3: NMRA encoding changed — convert old values: new = 1020 / old (round to integer).

CV #28 (SW ≥ 1.7): also enables ABC automatic braking when bit set per NMRA.

Appendix E — Forum insights (RailBOX manufacturer)

Condensed from 55 pages of the modelarstwo.info RB 2300 thread (posts by railbox, 2023–2025). Use alongside the PDF manual when behaviour differs by firmware version.

E.1 Sound, Wi-Fi, and troubleshooting

E.2 Hardware and connectors

E.3 Firmware changelog (highlights)

Current firmware: check railbox.pl / decoder CV #7.

E.4 Example logic snippets (forum)

Hall — wheel squeal on curves while moving:

I1_TOGETHER_F13_INMOVE

Hall — 2 s horn when passing a magnet:

F2_ON_I1_L2000

Random compressor (10–30 s, only when stopped):

F12_RANDOM_S10_E30_L4000_INSTOP

Dim output 3 to 40% when F5 on:

F5_DIM_O3_V40

Link F60 with F1:

F60_TOGETHER_F1

E.5 Support

Manufacturer asks users to report bugs via e-mail (see railbox.pl). Custom Wi-Fi function mapping (other than F28) may be programmed on order.