wwwchrisde

[wwwchrisde]

Hatte bei V 0.4.1 im Ordner Arduino/libraries/MattzoBricks folgende Dateien liegen:

• MattzoController_Library.h
• MattzoController_Network_Configuration.h (editiert)
• MattzoPowerFunctions.cpp
• MattzoPowerFunctions.h

Habe gerade nochmal den kompletten Library Ordner der v 0.3 aus dem Arduino Folder weggeschoben und den 0.4.1 reingeschoben. Die Konfiguration habe ich 1:1 aus der v 0.3 übernommen kompiliert und hochgeladen – connect Bluetooth funktioniert, Wifi nicht.
Das Ganze in die andere Richtung gemacht und Lok läuft sofort wieder.

Soweit mal ein Update zur Reproduzierbarkeit des Problems. Für’s erste reicht mir das mal um im Kleinen damit rumzuspielen.

Danke für die tolle Arbeit.

• This reply was modified 3 years ago by wwwchrisde. Reason: Additional information

[wwwchrisde]

Welches Library file meinst Du? Die MattzoController_Network_Configuration.h habe ich selbstverständlich mit den Daten des WLAN gefüttert.

Ich habe die Firmware Datei extrahiert und komplett den Ordner MatzzoBricks der im Archiv im Unterordner libraries war in meinen Ordner Dokumente/Arduino/libraries verschoben. Dort habe ich dann die Network Configuration bearbeitet und mit SSID und PW versehen.

Das Projekt habe ich direkt am Ort belassen wohin es extrahiert wurde und dort die entsprechenden Änderungen in der Config Datei gemacht.

Als Boardtyp habe ich auch “ESP32 Dev Module” in Arduino ausgewählt.

Die gleiche Vorgehensweise hat mit V 0.3 zum Erfolg geführt.

Grüße aus Mannheim

Chris

[wwwchrisde]

Ich habe einen AZDelivery ESP32 Dev Kit C V4 NodeMCU gekauft.

[wwwchrisde]

Danke für die V 0.3 – damit lief das Krokodil sofort und stabil.

[wwwchrisde]

Hi, kann man die V 0.3 noch irgendwo laden? Bin erst letzte Woche hier gelandet und habe auf def Seite nur die 0.4 und 0.4.1 geladen.

[wwwchrisde]

Hi, schön zu sehen dass ich nicht der einzige mit dem Problem bin. Da ich neu in diesem Gebiet bins suche ich den Grund für’s scheitern erst mal bei mir 😉 bin jetzt doch beruhigt und hoffe dass es da bald eine Lösung für gibt – vielleicht eine Pause bis das Wifi connect zurückgemeldet wird bevor die Bluetooth Verbindungen aufgebaut werden? Nur so eine noob Idee.

[wwwchrisde]

My APs create the networks on 2.4 and 5.0 simultaneously

[wwwchrisde]

Hello Mattze, I Süd- the latest Firmware 0.4.1 for the Project. I will try rebooting multiple times. shall I use the reset button or just cut power and power on again?

[wwwchrisde]

No change when trying to connect to a freshly created wifi with SSID and password. Serial monitor shows that the controller tries to connect to the right wifi but I don’t get a success message and the controller doesn’t show up in the network environment.

[wwwchrisde]

Hello Matthias, thanks for your quick answer. The network I use is password protected and I provided both SSID and password in the network configuration file. The controller did once connect to the wifi using those credentials but with subsequent flashes e.g. to add the MAC Address of the PU Hub it didn’t reconnect anymore.

I tried the reset button but that didn’t work either. Will try to set up a different wifi later in the day and see if that works.

[wwwchrisde]

Hello there in this nice little Bricktrainworld. I love this wonderful project as I come from the golden 12V LEGO train ages where switches, level crossings and their signals as well as decouplers were remotely controlled.

I just offered me the 10277 crocodile last week along with a PoweredUp Hub and an AZ-Delivery ESP32 DevKitC V4 with it and I am since then trying to get it controllable from my MacBookPro.

I installed the necessary software, included all the libraries and configured my network settings in the corresponding file.

const int NUM_LOCOS = 1;
locoConf[0] = (MattzoLocoConfiguration){
  .locoName = "Krokodil",
  .locoAddress = 10277,
  .accelerationInterval = 100,
  .accelerateStep = 2,
  .brakeStep = 2
  };

const int NUM_HUBS = 1;

hubConf[0] = (MattzoPUHubConfiguration){
    .hubName = "CROCO",
    .macAddress = "90:84:2b:22:3a:4b",
    .devicePortA = MattzoPUDevice::PU_MOTOR,
    .configMotorA = 1,
    .devicePortB = MattzoPUDevice::NONE,
    .configMotorB = 0,
    .locoAddress = 10277
  };

I started Mosquitto and were able to verify that it receives the Rocrail commands:
rocrail/service/info <lc id="CROCO" V="83" fn="false" dir="true" throttleid="rv16635" controlcode="" slavecode="" server="infwD1904330" iid="29799" uid="0" sid="0" addr="10277" secaddr="0" placing="true" blockenterside="true" blockenterid="" modeevent="false" mode="stop" modereason="" resumeauto="false" manual="false" shunting="false" standalone="false" blockid="" destblockid="" runtime="1020" mtime="0" rdate="1617832985" mint="0" active="true" waittime="0" scidx="-1" scheduleid="" tourid="" scheduleinithour="0" len="0" weight="0" train="" trainlen="0" trainweight="0" V_realkmh="0" fifotop="false" image="" imagenr="0" energypercentage="0" lookupschedule="false" pause="false" consist=""/>

I managed to upload the firmware and my network controller showed me the AZ-Delivery ESP32 V4 I use with an IP Adress and the generated MattzoID in the hostname. I managed to find the MAC Adress of the Hub and added this information to the config file. I rey-loaded the firmware to the controller but it didn’t show up as active device in my network.

Those are the following messages I got from the serial monitor:

00:18:10.936 -> ⸮IE⸮⸮r:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
00:18:10.936 -> mode:DIO, clock div:1
00:18:10.936 -> load:0x3fff0018,len:4
00:18:10.936 -> load:0x3fff001c,len:1216
00:18:10.936 -> ho 0 tail 12 room 4
00:18:10.936 -> load:0x40078000,len:10944
00:18:10.936 -> load:0x40080400,len:6388
00:18:10.956 -> entry 0x400806b4
00:18:11.269 ->
00:18:11.269 -> MattzoController booting…
00:18:11.302 -> Loaded mattzoControllerId from EEPROM: 29799
00:18:11.302 -> Connecting as MTC4PU29799 to Wifi ncis
00:18:11.405 -> [1] MattzoController setup completed.
00:18:11.405 -> [1] Discovering Powered Up Hubs…
00:18:13.512 -> [1] Powered Up Hub found. MAC Address: 90:84:2b:22:3a:4b
00:18:13.512 -> .
00:18:13.512 -> [1] Initializing hub CROCO (90:84:2b:22:3a:4b)…
00:18:13.547 -> [1] Connecting to hub 0…
00:18:14.522 -> [1] Connected to hub 0.
00:18:14.522 -> [1] sending mqtt: roc2bricks/connectionStatus MTC4PU29799 CROCO (90:84:2b:22:3a:4b) connected
00:18:14.555 -> .
00:18:15.034 -> .
00:18:15.527 -> .
00:18:16.049 -> .
00:18:16.538 -> .
00:18:17.066 -> .
00:18:17.556 -> .
00:18:18.042 -> .
00:18:18.570 -> .
00:18:19.063 -> .
00:18:19.545 -> .
00:18:20.069 -> .
00:18:20.562 -> .
00:18:21.052 -> .
00:18:21.265 -> [1] *** DEBUG-INFO ***
00:18:21.265 -> [1] WiFi + MQTT connection Status: 0
00:18:21.265 -> [1] Loco 0: Krokodil (10277). Target speed: 0, current speed: 0, max speed: 0
00:18:21.265 -> [1] next hub to initialize (if any): 0
00:18:21.265 -> [1] Hub 0: macAddress=90:84:2b:22:3a:4b: isConnecting()=0 isConnected()=1 status=1
00:18:21.265 -> [1] Free heap size: 139448
00:18:21.300 -> [1] Leargest free heap block: 113792
00:18:21.300 -> [1] Minimm free heap size since boot: 136376
00:18:21.300 -> [1] ******************

The ESP won’t connect to the Wifi anymore. I uploaded a wifi test to the board that immediately connected to my wifi with the exact settings I provided in the config file for the MTC4PU so I am sure that it’s not an hardware issue.

Any ideas on how to proceed here? Thanks for your support and good night.

wwwchrisde

[Author]

Posts