MattzoBricks

Intelligent LEGO trains

Implementation of V1.2.2

Welcome to MattzoBricks › Forums › MattzoBricks General Forum › Implementation of V1.2.2

Viewing 9 reply threads
  • Author
    Posts
    • June 20, 2025 at 12:29 #8506
      Des MatejkaDes Matejka
      Participant

      I’ve been successfully using Mattzobricks Powered Up automation since January 2025.
      I’d like to record my appreciation to the development team and particularly Dr. Matthias Runte for his help to me encouraging me along the way.
      Using V1.1 I have
      – az-delivery-devkit-v4 ESP32 development board
      – 3 MTC4BT each communicating with 4 Lego PH hubs
      – 2 MLC communicatng with 10 reed sensors
      – I am yet to implement switches, signals or lights
      I have upgraded to V1.2.2.
      My earlier implementation allowed the upgrade to be more easily understood.
      The upgrade is successful.
      The MTC4BT with WiFi can only communicte 2 Lego hubs and one PU controller.
      With V1.1 I could communicate with 4 Lego hubs.
      Is this an expectation from V1.2.2?
      I intend to try with Seeed Xiao ESP32-S3 development board to see if this changes.
      I have tried to use a W5500 Ethernet module without success
      Any comments would be greatly appreciated.
      Kind regards
      Des

    • June 26, 2025 at 12:07 #8507
      Hilbert BHilbert B
      Keymaster

      Hi Des,

      Sorry for the late reply, please post the startup log from your ESP, most of the time this gives us enough hints on where it went/goes wrong. (in debug mode)

      Regarding the W5500, again, post the startup log (in debug moode)

      Without these it is impossible to help.

      Regards, Hilbert

      PS use the “code” formatting, this helps the readability!

    • June 27, 2025 at 11:43 #8508
      Des MatejkaDes Matejka
      Participant

      Thanks Hilbert,
      I’ve pasted the code below.
      Only 3 of the 4 loco connect, but experience shows that only 2 will run.
      Hopefully you can offer some advice.

      I will post the W5500 output in another message.

      [1] Setup: Starting MTC4BT…
      [1] Setup: Loading network configuration…
      Syslog: Server: 192.168.1.1:514
      Syslog: Hostname: mtc4bt
      Syslog: Appname: MTC4BT
      [0000] [1] [INFO] Logging: Configured.
      [0001] [1] [DEBUG] Reading lookuptable
      [0002] [1] [INFO] Setup: Loading controller configuration…
      [0003] [1] [INFO] Config: Read controller name: gb_t_1-4_c-1-4f
      [0004] [1] [INFO] Config: Read ESP pin configuration (1).
      [0005] [1] [DEBUG] hub address: “90:84:2b:21:24:78”, config address: “90:84:2b:21:24:78”
      [0006] [1] [DEBUG] Number of triggers (2) and actions (1) loaded for this event.
      [0007] [1] [DEBUG] hub address: “90:84:2b:21:24:78”, config address: “90:84:2b:21:24:78”
      [0008] [1] [DEBUG] Number of triggers (3) and actions (1) loaded for this event.
      [0009] [1] [DEBUG] Number of events loaded: 2.
      [0010] [1] [DEBUG] hub address: “90:84:2b:21:d7:01”, config address: “90:84:2b:21:d7:01”
      [0011] [1] [DEBUG] Number of triggers (2) and actions (1) loaded for this event.
      [0012] [1] [DEBUG] hub address: “90:84:2b:21:d7:01”, config address: “90:84:2b:21:d7:01”
      [0013] [1] [DEBUG] Number of triggers (3) and actions (1) loaded for this event.
      [0014] [1] [DEBUG] Number of events loaded: 2.
      [0015] [1] [DEBUG] hub address: “90:84:2b:21:92:08”, config address: “90:84:2b:21:92:08”
      [0016] [1] [DEBUG] Number of triggers (2) and actions (1) loaded for this event.
      [0017] [1] [DEBUG] hub address: “90:84:2b:21:92:08”, config address: “90:84:2b:21:92:08”
      [0018] [1] [DEBUG] Number of triggers (3) and actions (1) loaded for this event.
      [0019] [1] [DEBUG] Number of events loaded: 2.
      [0020] [1] [DEBUG] hub address: “90:84:2b:21:92:0c”, config address: “90:84:2b:21:92:0c”
      [0021] [1] [DEBUG] Number of triggers (2) and actions (1) loaded for this event.
      [0022] [1] [DEBUG] hub address: “90:84:2b:21:92:0c”, config address: “90:84:2b:21:92:0c”
      [0023] [1] [DEBUG] Number of triggers (3) and actions (1) loaded for this event.
      [0024] [1] [DEBUG] Number of events loaded: 2.
      [0025] [1] [DEBUG] Starting reading remotes json
      [0026] [1] [DEBUG] freeButtonItem action 34 device 1.
      [0027] [1] [DEBUG] freeButtonItem action 35 device 1.
      [0028] [1] [DEBUG] freeButtonItem action 36 device 1.
      [0029] [1] [DEBUG] freeButtonItem action 2 device 1.
      [0030] [1] [DEBUG] freeButtonItem action 2 device 1.
      [0031] [1] [DEBUG] freeButtonItem action 49 device 6.
      [0032] [1] [DEBUG] freeButtonItem action 48 device 6.
      [0033] [1] [DEBUG] Config: number of remotes 1.
      [0034] [1] [DEBUG] Starting reading remotes json
      [0035] [1] [DEBUG] freeButtonItem action 34 device 1.
      [0036] [1] [DEBUG] freeButtonItem action 35 device 1.
      [0037] [1] [DEBUG] freeButtonItem action 36 device 1.
      [0038] [1] [DEBUG] freeButtonItem action 2 device 1.
      [0039] [1] [DEBUG] freeButtonItem action 2 device 1.
      [0040] [1] [DEBUG] freeButtonItem action 49 device 6.
      [0041] [1] [DEBUG] freeButtonItem action 48 device 6.
      [0042] [1] [DEBUG] Config: number of remotes 1.
      [0043] [1] [DEBUG] Starting reading remotes json
      [0044] [1] [DEBUG] freeButtonItem action 34 device 1.
      [0045] [1] [DEBUG] freeButtonItem action 35 device 1.
      [0046] [1] [DEBUG] freeButtonItem action 36 device 1.
      [0047] [1] [DEBUG] freeButtonItem action 2 device 1.
      [0048] [1] [DEBUG] freeButtonItem action 2 device 1.
      [0049] [1] [DEBUG] freeButtonItem action 49 device 6.
      [0050] [1] [DEBUG] freeButtonItem action 48 device 6.
      [0051] [1] [DEBUG] Config: number of remotes 1.
      [0052] [1] [DEBUG] Starting reading remotes json
      [0053] [1] [DEBUG] freeButtonItem action 34 device 1.
      [0054] [1] [DEBUG] freeButtonItem action 35 device 1.
      [0055] [1] [DEBUG] freeButtonItem action 36 device 1.
      [0056] [1] [DEBUG] freeButtonItem action 2 device 1.
      [0057] [1] [DEBUG] freeButtonItem action 2 device 1.
      [0058] [1] [DEBUG] freeButtonItem action 49 device 6.
      [0059] [1] [DEBUG] freeButtonItem action 48 device 6.
      [0060] [1] [DEBUG] Config: number of remotes 1.
      [0061] [1] [INFO] CTRL: Local channels initialized.
      [0062] [1] [DEBUG] Init remote
      [0063] [1] [DEBUG] Init remote
      [0064] [1] [DEBUG] Init remote
      [0065] [1] [DEBUG] Init remote
      [0066] [1] [INFO] Setup: Controller configuration completed.
      [0067] [1] [INFO] setup: WiFi Event ID: 4
      [0068] [1] [DEBUG] [WiFi-event] event: 0

      [0069] [1] [DEBUG] WiFi interface ready
      [0070] [1] [DEBUG] [WiFi-event] event: 2

      [0071] [1] [DEBUG] WiFi client started
      [0072] [1] [INFO] Wifi: Connecting to DigiFX 2.4GHz.
      [0073] [1] [INFO] Wait for WiFi/ETH…
      [0074] [1] [INFO] MQTT: Connecting to 192.168.1.207:1883…
      [0075] [1] [INFO] Setup: Initializing BLE…
      [0076] [1] [INFO] Setup: MattzoTrainController for BLE running.
      [0077] [1] [INFO] Setup: Number of locos to discover hubs for: 4
      [0078] [1] [INFO] Setup: Number of remotes to discover hubs for: 4
      [0079] [1] [DEBUG] SetE-Brake: 1
      [0080] [1] [DEBUG] SetE-Brake: 1
      [0081] [1] [DEBUG] SetE-Brake: 1
      [0082] [1] [DEBUG] SetE-Brake: 1
      [0083] [0] [INFO] BLE : Scanning for 8 hub(s)…
      [0084] [0] [INFO] BLE : Discovered unknown device: (50:32:37:c3:e1:74).
      [0085] [0] [INFO] BLE : Discovered unknown device: (60:ae:8b:43:c0:f8).
      [0086] [0] [INFO] BLE : Discovered unknown device: (77:c8:3e:a3:99:6f).
      [0087] [0] [INFO] BLE : Discovered unknown device: (7e:f8:cf:9b:65:5d).
      [0088] [0] [INFO] BLE : Discovered unknown device: (66:d5:0c:d6:76:6d).
      [0089] [0] [INFO] BLE : Discovered unknown device: (e8:16:6e:78:86:21).
      [0090] [0] [INFO] BLE : Discovered unknown device: (54:c4:7e:04:7e:a4).
      [0091] [0] [INFO] BLE : Discovered unknown device: (66:28:37:36:94:1e).
      [0092] [0] [INFO] BLE : Discovered unknown device: (7f:b4:0a:12:22:76).
      [0093] [0] [INFO] BLE : Discovered unknown device: (6f:4c:2a:e6:ea:fb).
      [0094] [0] [INFO] BLE : Scanning for 8 hub(s) aborted.
      [0095] [1] [DEBUG] [WiFi-event] event: 5

      [0096] [1] [DEBUG] Disconnected from WiFi access point
      WiFi lost connection. Reason: 203
      [0097] [1] [DEBUG] [WiFi-event] event: 4

      [0098] [1] [DEBUG] Connected to access point
      [0099] [1] [DEBUG] [WiFi-event] event: 7

      Obtained WiFi IP address: 192.168.1.106
      WiFi connected
      IP address:
      192.168.1.106
      MAC Address: 2C:BC:BB:0C:27:88
      [0100] [1] [INFO] Try mqtt reconnect…
      [0101] [1] [INFO] MQTT: Connected gb_t_1-4_c-1-4f
      [0102] [1] [INFO] Reconnected!
      [0103] [1] [DEBUG] SetE-Brake: 0
      [0104] [1] [DEBUG] SetE-Brake: 0
      [0105] [1] [DEBUG] SetE-Brake: 0
      [0106] [1] [DEBUG] SetE-Brake: 0
      [0107] [1] [INFO] MQTT: Received ‘shutdown’ command. Stopping all locos.
      [0108] [1] [DEBUG] SetE-Brake: 1
      [0109] [1] [DEBUG] SetE-Brake: 1
      [0110] [1] [DEBUG] SetE-Brake: 1
      [0111] [1] [DEBUG] SetE-Brake: 1
      [0112] [0] [INFO] BLE : Scanning for 8 hub(s)…
      [0113] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:92:08).
      [0114] [0] [INFO] BLE : Discovered unknown device: (53:fc:ad:be:88:34).
      [0115] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:24:78).
      [0116] [0] [INFO] BLE : Discovered unknown device: (d0:0e:09:c4:94:9f).
      [0117] [0] [INFO] BLE : Discovered unknown device: (d7:65:22:30:1a:30).
      [0118] [0] [INFO] BLE : Scanning for 8 hub(s) aborted.
      [0119] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:24:78’…
      [0120] [0] [DEBUG] hub created: 1073663052 (90:84:2b:21:24:78)
      [0121] [0] [INFO] BLE : Connected to hub ’90:84:2b:21:24:78′.
      [0122] [0] [DEBUG] connected connected address 90:84:2b:21:24:78, has callback 1
      [0123] [0] [INFO] BLE : Watchdog timeout not set for PU hubs
      [0124] [0] [INFO] PU : Found integrated RGB LED at port 32
      [0125] [0] [INFO] Loop: Connected to all hubs of loco ‘7777 Steam Tender’.
      [0126] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:92:08’…
      [0127] [0] [DEBUG] hub created: 1073657760 (90:84:2b:21:92:08)
      [0128] [0] [WARN] BLE : Failed to connect to hub ’90:84:2b:21:92:08′, deleted client.
      [0129] [0] [WARN] Loop: Connect failed. Will retry…
      [0130] [0] [INFO] BLE : Scanning for 6 hub(s)…
      [0131] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:d7:01).
      [0132] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:92:08).
      [0133] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:92:0c).
      [0134] [0] [INFO] BLE : Discovered unknown device: (e8:61:a7:58:05:7d).
      [0135] [0] [INFO] BLE : Scanning for 6 hub(s) aborted.
      [0136] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:d7:01’…
      [0137] [0] [DEBUG] hub created: 1073657760 (90:84:2b:21:d7:01)
      [0138] [0] [WARN] BLE : Failed to connect to hub ’90:84:2b:21:d7:01′, deleted client.
      [0139] [0] [WARN] Loop: Connect failed. Will retry…
      [0140] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:92:08’…
      [0141] [0] [DEBUG] hub created: 1073657828 (90:84:2b:21:92:08)
      [0142] [0] [WARN] BLE : Failed to connect to hub ’90:84:2b:21:92:08′, deleted client.
      [0143] [0] [WARN] Loop: Connect failed. Will retry…
      [0144] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:92:0c’…
      [0145] [0] [DEBUG] hub created: 1073657828 (90:84:2b:21:92:0c)
      [0146] [0] [WARN] BLE : Failed to connect to hub ’90:84:2b:21:92:0c’, deleted client.
      [0147] [0] [WARN] Loop: Connect failed. Will retry…
      [0148] [0] [INFO] BLE : Scanning for 4 hub(s)…
      [0149] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:d7:01).
      [0150] [0] [INFO] BLE : Discovered unknown device: (69:27:50:f8:8b:f5).
      [0151] [0] [INFO] BLE : Scanning for 4 hub(s) aborted.
      [0152] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:d7:01’…
      [0153] [0] [DEBUG] hub created: 1073659864 (90:84:2b:21:d7:01)
      [0154] [0] [WARN] BLE : Failed to connect to hub ’90:84:2b:21:d7:01′, deleted client.
      [0155] [0] [WARN] Loop: Connect failed. Will retry…
      [0156] [0] [INFO] BLE : Scanning for 6 hub(s)…
      [0157] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:d7:01).
      [0158] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:92:0c).
      [0159] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:92:08).
      [0160] [0] [INFO] BLE : Scanning for 6 hub(s) aborted.
      [0161] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:d7:01’…
      [0162] [0] [DEBUG] hub created: 1073659864 (90:84:2b:21:d7:01)
      [0163] [0] [WARN] BLE : Failed to connect to hub ’90:84:2b:21:d7:01′, deleted client.
      [0164] [0] [WARN] Loop: Connect failed. Will retry…
      [0165] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:92:08’…
      [0166] [0] [DEBUG] hub created: 1073657880 (90:84:2b:21:92:08)
      [0167] [0] [INFO] BLE : Connected to hub ’90:84:2b:21:92:08′.
      [0168] [0] [DEBUG] connected connected address 90:84:2b:21:92:08, has callback 1
      [0169] [0] [INFO] BLE : Watchdog timeout not set for PU hubs
      [0170] [0] [INFO] PU : Found integrated RGB LED at port 32
      [0171] [0] [INFO] Loop: Connected to all hubs of loco ‘7740 Int City’.
      [0172] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:92:0c’…
      [0173] [0] [DEBUG] hub created: 1073669624 (90:84:2b:21:92:0c)
      [0174] [0] [WARN] BLE : Failed to connect to hub ’90:84:2b:21:92:0c’, deleted client.
      [0175] [0] [WARN] Loop: Connect failed. Will retry…
      [0176] [0] [INFO] BLE : Scanning for 4 hub(s)…
      [0177] [0] [INFO] BLE : Discovered hub: (60:77:71:df:65:ec).
      [0178] [0] [INFO] BLE : Discovered unknown device: (c3:fa:77:2d:80:42).
      [0179] [0] [INFO] BLE : Discovered unknown device: (f9:2d:8d:cf:ab:3a).
      [0180] [0] [INFO] BLE : Discovered unknown device: (41:94:07:42:66:3e).
      [0181] [0] [INFO] BLE : Discovered unknown device: (e9:ca:fb:51:a5:1c).
      [0182] [0] [INFO] BLE : Discovered unknown device: (cb:5e:89:e9:72:90).
      [0183] [0] [INFO] BLE : Scanning for 4 hub(s) aborted.
      [0184] [0] [INFO] BLE : Connecting to hub ’60:77:71:df:65:ec’…
      [0185] [0] [DEBUG] hub created: 1073674400 (60:77:71:df:65:ec)
      [0186] [0] [WARN] BLE : Failed to connect to hub ’60:77:71:df:65:ec’, deleted client.
      [0187] [0] [WARN] Loop: Connect failed. Will retry…
      [0188] [0] [INFO] BLE : Scanning for 5 hub(s)…
      [0189] [0] [INFO] BLE : Discovered hub: (60:77:71:df:65:ec).
      [0190] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:d7:01).
      [0191] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:92:0c).
      [0192] [0] [INFO] BLE : Scanning for 5 hub(s) aborted.
      [0193] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:d7:01’…
      [0194] [0] [DEBUG] hub created: 1073669656 (90:84:2b:21:d7:01)
      [0195] [0] [INFO] BLE : Connected to hub ’90:84:2b:21:d7:01′.
      [0196] [0] [DEBUG] connected connected address 90:84:2b:21:d7:01, has callback 1
      [0197] [0] [INFO] BLE : Watchdog timeout not set for PU hubs
      [0198] [0] [INFO] PU : Found integrated RGB LED at port 32
      [0199] [0] [INFO] Loop: Connected to all hubs of loco ‘10219 Maersk’.
      [0200] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:92:0c’…
      [0201] [0] [WARN] BLE : Max clients reached – no more connections available.
      [0202] [0] [WARN] Loop: Connect failed. Will retry…
      [0203] [0] [INFO] BLE : Connecting to hub ’60:77:71:df:65:ec’…
      [0204] [0] [WARN] BLE : Max clients reached – no more connections available.
      [0205] [0] [WARN] Loop: Connect failed. Will retry…
      [0206] [0] [INFO] BLE : Scanning for 3 hub(s)…
      [0207] [0] [INFO] BLE : Discovered hub: (90:84:2b:21:92:0c).
      [0208] [0] [INFO] BLE : Scanning for 3 hub(s) aborted.
      [0209] [0] [INFO] BLE : Connecting to hub ’90:84:2b:21:92:0c’…
      [0210] [0] [WARN] BLE : Max clients reached – no more connections available.
      [0211] [0] [WARN] Loop: Connect failed. Will retry…
      [0212] [0] [INFO] BLE : Scanning for 4 hub(s)…
      [0213] [0] [INFO] BLE : Scanning for 4 hub(s) aborted.
      [0214] [0] [INFO] BLE : Scanning for 5 hub(s)…
      [0215] [0] [INFO] BLE : Discovered unknown device: (61:4f:93:af:e5:7c).
      [0216] [0] [INFO] BLE : Scanning for 5 hub(s) aborted.
      [0217] [0] [INFO] BLE : Scanning for 5 hub(s)…

    • June 27, 2025 at 15:07 #8512
      Hilbert BHilbert B
      Keymaster

      Des,

      Can you try and do the same but then with 4 configured devices?

      
[0077] [1] [INFO] Setup: Number of locos to discover hubs for: 4
[0078] [1] [INFO] Setup: Number of remotes to discover hubs for: 4

      At the moment you have 8 devices configured, this keeps the program scanning for all 8. 4 Should be no problem in any case.

      With the wired interface you could try more devices.

      As a general rule, do not configure more devices than that you are going to use!

      Hilbert

    • June 27, 2025 at 23:15 #8514
      Des MatejkaDes Matejka
      Participant

      Hello Hilbert,
      I do appreciate the time that you are giving to this. You are very generous.

      Can I remove the remotes from the “controller_config.json” file?

      This would test with 4 hubs.

      “remoteConfigs”: [
      “/c01_r_7777_f.json”,
      “/c02_r_maresk_f.json”,
      “/c03_r_7740_f.json”,
      “/c04_r_7725_f.json”
      ]
      }

      As I noted, with V1.1 I could communicate with 4 Lego hubs.
      Is V1.2.2. just going to deliver fewer hubs?

      Cheers

      Des

      I have the fllowing “controller_config.json” file which works fine but still only 2 locos.

      {
      “name”: “gb_t1-2_c1-7”,
      “espPins”: [
      {
      “pin”: 2,
      “attachedDevice”: “status”
      }
      ],
      “locos”: [],
      “locoConfigs”: [
      “/01_7777.json”,
      “/02_maersk.json”
      ],
      “remoteConfigs”: [
      “/c1-7_list.json”
      ]
      }

    • June 28, 2025 at 23:28 #8515
      Hilbert BHilbert B
      Keymaster

      Hi Des,

      No problem, I have put some time in the coding of this part 😉

      Yes, you can remove those includes.

      I have tested it with 4 hubs (2 lego and 2 buwizz) and one remote. So it should work (5 devices), I think Mattze tested with even more devices.

      It is however highly recommended that when you use a lot of BLE devices on one ESP32 to use a W5500 module for the network connection. The reason for this is that every ESP32 has only one radio, the same is used for both WiFi and BLE. By adding a W5500 (wired Ethernet) we offload the wifi to wired Ethernet thus removing the WiFi and BLE switching, this greatly improved the performance and stability.

      We used seeed_xiao_esp32-s3 with external antenna and that one handles 4 BLE devices with ease (a BLE device is either a hub or a remote).

      In the Readme.md included in the MTC4BT map. Search for “Wired Ethernet” there you will find how to connect and configure the W5500 module.

      Regards, Hilbert

    • June 29, 2025 at 09:38 #8516
      Des MatejkaDes Matejka
      Participant

      Hi Hilbert
      Thanks for your reply.
      It seems that I need to continue testing my setup.
      I have not yet been successful with W5500 (wired Ethernet) or tried the seeed_xiao_esp32-s3
      At least my coding seems OK.
      It will be at least 2 weeks until I can try again.
      We are travelling to Adelaide from Sydney by car about 1300 km to visit the 2025 BRIXPO Lego show. I’m expecting to see a large Lego Train display at the exhibition. I wonder how many users are implementing Mattzobricks?
      At the Sydney show I saw some train automation systems that were custom designed, but mostly I am seeing manual implementation with minimal use of automation systems.
      I became quite skilled at using Lego Powered Up coding for automation, but the limitations are quite apparent.
      I am excited with the full automation of Mattzobricks Train Automation System. What you have developed is really good and I can see the potential it offers.
      As I work with Mattzobricks I become more skilled and ultimately more successful.
      I am very close to sharing what I have with others.
      Cheers
      Des

    • August 23, 2025 at 23:27 #8550
      Des MatejkaDes Matejka
      Participant

      Success with seed_xiao_esp32-s3.
      It runs four BLE devices without any problems.
      Rocrail is successfully configured for layout needs.
      In some respects, this has been the most difficult part.
      Someone suggested using ChatGPT for questions about Rocrail configuration.
      This was quite helpful, if only to help understand the nature of the problem.
      So thanks again for your wonderful help.
      BRIXPO in Adelaide was outstanding.
      The train display was somewhat limited, and there were no train automation systems in operation.
      Given the population base and distance to travel, I understand this.
      Regards
      Des

    • August 23, 2025 at 23:31 #8551
      Des MatejkaDes Matejka
      Participant

      To complete my layout needs with 14 locoimotives I need several boards in operation.
      The seed_xiao_esp32-s3 can run four BLE devices.
      I have several az-delivery-devkit-v4 ESP32 development boards so I will use these for the rest of my devices.
      I’m considering dedicating some of the az-delivery boards for the PU controllers.
      Is this a good idea?
      Regards
      Des

    • August 27, 2025 at 22:03 #8552
      Hilbert BHilbert B
      Keymaster

      Des,

      I wouldn’t do the PU version, but the MTC4BT version for those esp32’s, do not use the esp32-s3 profile in vscode, that won’t upload because it is an other processor.
      Adding a W5500 module to the esp32 will improve things!

      Hilbert

      • This reply was modified 3 weeks, 4 days ago by Hilbert BHilbert B.
  • Author
    Posts
Viewing 9 reply threads
  • You must be logged in to reply to this topic.