- This topic has 3 replies, 3 voices, and was last updated 2 months ago by
.
-
Posts
-
-
Hallo,
ich versuche gerade dem MTC4BT meine Fernbedienungen beizubringen. Ich benutze dafür einen Seeed Xiao ESP32-S3.
Zunächst habe ich festgestellt, dass zu viele PoweredUp Hubs in der Liste der bekannten Geräte irgendwann nicht mehr funktionieren, auch wenn nur einer dieser Hubs eingeschaltet ist. (Bei mir wurde aktuell der 16. Eintrag nicht verbunden.)
Wenn ich aber nun versuche, eine Fernbedienung einzurichten, scheint der ESP immer wieder Resets durchzuführen. Nehme ich die Fernbedienung aus der controller_config.json raus, funktioniert alles problemlos.
So sieht meine controller_config.json aus:
{ "name": "LegoTrainControl", "espPins": [], "fn": [], "locos": [], "remotes": [], "locoConfigs": [ "/7722_kl_Dampf.json", "/7727_kl_Dampf.json", "/7720_kl_Diesel.json", "/60337_Flix.json" ], "remoteConfigs": [ "/pu_remote1.json" ] }Die Datei für die Fernbedienung sieht so aus:
{ "type": "PUController", "name": "PUC1", "address": "a4:da:32:68:04:8e", "mode": "list", "list": [ { "address": 4, "type": "loco", "color": "yellow" }, { "address": 11, "type": "loco", "color": "red" }, { "address": 9, "type": "loco", "color": "green" }, { "address": 6, "type": "loco", "color": "blue" } ] }Hat jemand eine Idee, woran das liegen könnte?
Viele Grüße
Stephan
-
Stephan,
Without the serial log, I am guessing what is going on.
Most of the time the serial log will give away what is going on.
What we have seen and put in the configuration that at the time of writing, more than 5 ble devices on a Seeed Xiao ESP32-S3 are not possible, we have seen 9 on a regular esp32.
Also it is not a good practice to configure more devices than you are using!
Hilbert
-
-
Hallo,
ich habe mal etwas weiter getestet.
Habe jetzt ein ESP32-S3 nur mit den Controllern programmiert.
Wenn RocRail läuft und alle Controller ausgeschaltet sind, kommt es immer wieder zum Neustart des ESPs. Dies kann man auch am Notebook merken, da sich die serielle Schnittstelle immer wieder an- und abmeldet.
Die erste serielle Ausgabe sieht so aus:
0029] [1] [INFO] Setup: Initializing BLE... [0030] [1] [INFO] Setup: MattzoTrainController for BLE running. [0031] [1] [INFO] Setup: Number of locos to discover hubs for: 0 [0032] [1] [INFO] Setup: Number of remotes to discover hubs for: 3 [0033] [0] [INFO] BLE : Scanning for 3 hub(s)... [0035] [0] [INFO] BLE : Scanning for 3 hub(s) aborted. [0036] [1] [INFO] Try mqtt reconnect... [0037] [1] [INFO] MQTT: Connected LegoTrainCtrl3 [0038] [1] [INFO] Reconnected! [0039] [0] [INFO] BLE : Scanning for 3 hub(s)... [0040] [0] [INFO] BLE : Scanning for 3 hub(s) aborted. [0041] [0] [INFO] BLE : Scanning for 3 hub(s)... [0042] [0] [INFO] BLE : Scanning for 3 hub(s) aborted. [0043] [0] [INFO] BLE : Scanning for 3 hub(s)... [0044] [0] [INFO] BLE : Scanning for 3 hub(s) aborted. --- Abbruch der seriellen Verbindung ---Wenn RocRail nicht gestartet ist, gibt es die Neustarts nicht. Allerdings kann ich beispielsweise die Loks und damit die LED-Farbe auch nicht wechseln.
Die serielle Ausgabe sieht wie folgt aus:
[0016] [1] [INFO] setup: WiFi Event ID: 4 [0021] [1] [INFO] Wifi: Connecting to Steinmetznetz. [0022] [1] [INFO] Wait for WiFi/ETH... WiFi lost connection. Reason: 202 [0025] [1] [INFO] MQTT: Connecting to 192.168.XXX.XXX:1883... Obtained WiFi IP address: 192.168.XXX.XXX WiFi connected IP address: 192.168.XXX.XXX MAC Address: E8:06:90:9D:B6:10 [0029] [1] [INFO] Setup: Initializing BLE... [0030] [1] [INFO] Setup: MattzoTrainController for BLE running. [0031] [1] [INFO] Setup: Number of locos to discover hubs for: 0 [0032] [1] [INFO] Setup: Number of remotes to discover hubs for: 3 [0033] [0] [INFO] BLE : Scanning for 3 hub(s)... [0035] [0] [INFO] BLE : Scanning for 3 hub(s) aborted. [0036] [1] [INFO] Try mqtt reconnect... [0037] [1] [INFO] MQTT: Connected LegoTrainCtrl3 [0038] [1] [INFO] Reconnected! [0039] [1] [INFO] MQTT: Received 'shutdown' command. Stopping all locos. [0040] [0] [INFO] BLE : Scanning for 3 hub(s)... [0041] [0] [INFO] BLE : Scanning for 3 hub(s) aborted. [0042] [0] [INFO] BLE : Scanning for 3 hub(s)... [0043] [0] [INFO] BLE : Scanning for 3 hub(s) aborted. [0044] [0] [INFO] BLE : Scanning for 3 hub(s)... [0045] [0] [INFO] BLE : Scanning for 3 hub(s) aborted. [0046] [0] [INFO] BLE : Scanning for 3 hub(s)... [0047] [0] [INFO] BLE : Scanning for 3 hub(s) aborted. [0048] [0] [INFO] BLE : Discovered hub: (a4:da:32:68:04:8e). [0049] [0] [INFO] BLE : Connecting to hub 'a4:da:32:68:04:8e'... [0052] [0] [INFO] BLE : Tying to connecto to hub 'a4:da:32:68:04:8e'. [0053] [0] [INFO] BLE : Connected to hub 'a4:da:32:68:04:8e'. [0055] [0] [INFO] BLE : Watchdog timeout not set for PU hubs [0057] [0] [INFO] port 0 is connected with device 37 [0058] [0] [INFO] port 1 is connected with device 37 [0059] [0] [INFO] port 34 is connected with device 17 [0060] [0] [INFO] PU : Found integrated RGB LED at port 34 [0061] [0] [INFO] port 3b is connected with device 14 [0062] [0] [INFO] port 3c is connected with device 38 [0056] [0] [INFO] Loop: Connected to all remote hubs. [0063] [0] [INFO] BLE : Scanning for 2 hub(s)... [0064] [0] [INFO] BLE : Scanning for 2 hub(s) aborted. [0065] [0] [INFO] BLE : Scanning for 2 hub(s)... [0066] [0] [INFO] BLE : Scanning for 2 hub(s) aborted. [0067] [0] [INFO] BLE : Scanning for 2 hub(s)...
-
- You must be logged in to reply to this topic.