Two issues with SBrick and Buwizz2

[Dirk Schäfer]

Hello,

I am currently trying to migrate the MTC4BT from ESP32 to seeed Studio XIAO ESP32S3 using Mattzobricks 1.2.2. For Lego PU this works really well, is far more stable and has a higher range.
However, two problems have arisen with SBrick and Buwizz2 that I have not yet been able to solve and where I need your expertise:

Isssue 1:
I have one SBrick (Hardware v12 and Firmware v26) that is not recognised by the controllers (ESP32 and ESP32S3) no longer. When I switch on the SBrick’s power supply, it is not displayed in Visual Studio Code’s monitoring of the ESP32, not even as an unknown device. In the SBrick app or in Brickcontroller2, the SBrick is recognised without any problems and can be controlled. Other SBricks are discovered and can be controlled as usual by the MTC4BT. I disconnected the motors and lights and I also used other power supplies, but nothing changed.

Issue 2:
Since using the ESP32S3 all of my Buwizz 2.0 have shown problems that did not occur with the ESP32-WROOM-32. Typcially, the Buwizz2 is discovered by the MTC4BT and then connected to the MTC4BT correctly. But frequently, when I change the speed or switch a light on or off, an ERROR occurs, the Buwizz2 is disconnected and subsequently reconnected. In the VSC Monitor an ERROR is stated, but no error code. This happens so often that a reasonable operation is not possible. The firmware of the Buwizz is up tp date (Firmware 1.2.70) and the battery charge is high. In the Buwizz App the Buwizz2 are recognised without any problems and work properly with the same configuration.

Any ideas on these?
Thank you for your help.

Kind regards,
Dirk

[Dirk Schäfer]

Hi,

short update on issue 2:

When I reduce the controller_config.json to the loco with the Buwizz2, the ESP32S3 connects to the Buwizz2 and the connection remains stable and I can control the locomotive without problems in ROCRAIL. As soon as I add a second loco, the connections is unstable.

Here is an example of the output of the VSC monitor for an unstable connection with BuWizz2 (50:fa:ab:3d:89:ab):

[0118] [0] [INFO] BLE : Scanning for 1 hub(s)…
[0119] [0] [INFO] BLE : Scanning for 1 hub(s) aborted.
[0120] [0] [INFO] BLE : Scanning for 1 hub(s)…
[0121] [0] [INFO] BLE : Discovered unknown device: (76:f4:7a:b6:d7:cb).
[0122] [0] [ERROR] BLE : Disconnected from hub ’50:fa:ab:3d:89:ab’.
[0124] [0] [INFO] BLE : Discovered unknown device: (dc:84:8c:84:8b:aa).
[0125] [0] [INFO] BLE : Scanning for 1 hub(s) aborted.
[0126] [0] [INFO] BLE : Scanning for 2 hub(s)…
[0127] [0] [INFO] BLE : Discovered hub: BuWizz2 (50:fa:ab:3d:89:ab).
[0128] [0] [INFO] BLE : Scanning for 2 hub(s) aborted.
[0129] [0] [INFO] BLE : Connecting to hub ’50:fa:ab:3d:89:ab’…
[0130] [0] [INFO] BLE : Connected to hub ’50:fa:ab:3d:89:ab’.
[0132] [0] [INFO] BLE : Reconnected to hub ’50:fa:ab:3d:89:ab’…
[0133] [0] [INFO] BLE : BuWizz2 : Watchdog timeout not set
[0134] [0] [INFO] Loop: Connected to all hubs of loco ‘CROCOG’.
[0135] [0] [INFO] BLE : Scanning for 1 hub(s)…
[0136] [0] [INFO] BLE : Scanning for 1 hub(s) aborted.
[0137] [0] [ERROR] BLE : Disconnected from hub ’50:fa:ab:3d:89:ab’.
[0139] [0] [INFO] BLE : Scanning for 2 hub(s)…
[0140] [0] [INFO] BLE : Discovered hub: BuWizz2 (50:fa:ab:3d:89:ab).
[0141] [0] [INFO] BLE : Scanning for 2 hub(s) aborted.
[0142] [0] [INFO] BLE : Connecting to hub ’50:fa:ab:3d:89:ab’…
[0143] [0] [INFO] BLE : Connected to hub ’50:fa:ab:3d:89:ab’.
[0145] [0] [INFO] BLE : Reconnected to hub ’50:fa:ab:3d:89:ab’…
[0146] [0] [INFO] BLE : BuWizz2 : Watchdog timeout not set
[0147] [0] [INFO] Loop: Connected to all hubs of loco ‘CROCOG’.
[0148] [0] [INFO] BLE : Scanning for 1 hub(s)…
[0149] [0] [ERROR] BLE : Disconnected from hub ’50:fa:ab:3d:89:ab’.
[0151] [0] [INFO] BLE : Discovered hub: BuWizz2 (50:fa:ab:3d:89:ab).
[0152] [0] [INFO] BLE : Discovered unknown device: (fe:e4:00:42:64:54).
[0153] [0] [INFO] BLE : Scanning for 1 hub(s) aborted.
[0154] [0] [INFO] BLE : Connecting to hub ’50:fa:ab:3d:89:ab’…
[0155] [0] [INFO] BLE : Connected to hub ’50:fa:ab:3d:89:ab’.
[0157] [0] [INFO] BLE : Reconnected to hub ’50:fa:ab:3d:89:ab’…
[0158] [0] [INFO] BLE : BuWizz2 : Watchdog timeout not set
[0159] [0] [INFO] Loop: Connected to all hubs of loco ‘CROCOG’.
[0160] [0] [INFO] BLE : Scanning for 1 hub(s)…
[0161] [0] [INFO] BLE : Scanning for 1 hub(s) aborted.
[0162] [0] [INFO] BLE : Scanning for 1 hub(s)…
[0163] [0] [INFO] BLE : Scanning for 1 hub(s) aborted.

Kind regards,
Dirk

[Autor]

Beiträge