Forum Replies Created
-
Posts
-
Hi Chris,
I have my roots in the golden 12V age as well.We have experienced a couple of problems on ESP32 boards when trying to connect to connect to WiFi and Bluetooth concurrently. Usually it helps to reboot the controller a couple of times.
Please make sure you are using Firmware 0.4 or above – we have improved the stability of the connection procedere with 0.4. WiFi connectivity should be working now without a problem. The controller will now establish the WiFi connection at first and only thereafter start to connect to Bluetooth devices. This seems to work more reliably on most boards.
We are actively working on improving to control bluetooth devices. The next version of the MTC4PU will likely also connect to SBricks and is (hopefully) going to work significantly better in terms of reliability and stability.
Cheers,
MattzeHallo Herbert,
ich habe nachgesehen und erstaunt festgestellt, dass ich die Steuerung mehrerer Züge über Infrarot mit einem einzigen MTC4PF tatsächlich nicht realisiert hatte. Liegt daran, dass ich selbst den MTC4PF immer in den Zug eingebaut hatte und das Multitrain-Setup selbst nicht getestet hatte. Ich nehme das mit auf die Liste. Bis dahin bitte einen Controller je IR-Empfänger verwenden.Gruß,
MattzeConfiguration looks okay, the debug message from the controller as well.
What IR LEDs did you use? I used these ones here:
Worked perfectly.
Sieht so aus als würden Rocrail und der Controller alles richtig machen. Wenn die Lok trotzdem immer vorwärts fährt, ist möglicherweise das Motor Shield falsch angeschlossen. Check doch mal, ob Du mit einem einfachen Motorshield Sketch aus der Beispiel-Bibliothek der Arduino IDE der Motor überhaupt andersherum gedreht bekommst. Ansonsten würde mich Deine MattzoController Konfigurationsdatei (MTC4PF_Configuration.h) interessieren.
Poste bitte mal die MQTT loco messages und welche Richtung du jeweils erwartest. Auch die Serial Logs vom MattzoTrainController wären hilfreich.
Hallo allerseits,
könnt Ihr mal probieren, auf dem verdächtigen Controller das ganz einfache Beispiel-Sketch laufen zu lassen und einfach den Servo ein bisschen zu drehen? Vorsicht mit dem zulässigen Winkelbereich, zerschießt Euch nicht die Weichenmotoren. Danke!Nur der MTC4PU braucht bislang einen ESP-32, alle anderen Controller benötigen einen ESP12 / ESP8266.
Gruß,
MattzeSection “emergency brake”.
Happy to hear that.
And here is your chance for compensation: 🙂
– If you build a beautiful LEGO train layout, send me the track plan and media like photos and videos, so that I can publish it in the projects section on the website! My e-mail address can be found in the imprint (Impressum) section.Thanks!
The last part of the lightEvent() function should be changed like this:
case LightEventType::REVERSE: mcLog("Light event reverse"); // UPDATE THIS CODE SO THAT IT FITS YOUR NEEDS! functionCommand[i] = ((i == 0) || (i == 3)); break; } } } }Let me know if it works.
We have plans to make the light configuration both simpler and more powerful in the future.
If you could post:
1. the relevant sections of the config file (MTC4PF_Configuration.h or similar),
2. your lightEvent() function in MTC4PF.ino,
then I could try to comment on that.Thanks!
Hello Herbert,
welcome! At present, we have no plans to support the old RC Infrared prototcol, though I am aware that people have reengineered it and replaced the infrared remote control with their own devices. So it should theoretically be possible to do that.The MattzoLayoutController will be based on the ESP8266 as well. You may order some PCA9685 port extenders as well if you’re planning larger layouts.
Cheers,
MattzeI would recommend to wait a bit. We are not finally decided on unifying the MattzoTrainControllers yet. The ESP8266 based controllers work absolutely stable and without any problems. As you know, we are still struggeling a bit with the stability of the ESP32. Before we haven’t sorted out all problems, I am not willing to give up the ESP-8266 yet. Anyways, you can always use your ESP8266 for building layout controllers (sensors, switches, signals…).