Forum Replies Created
-
Posts
-
Welcome to Mattzobricks! You should try digital sensors instead of Hall sensors. We recommend reed sensors. I recently posted a video about sensors on the Youtube Channel, and I have also put some work into rewriting the sensor page.
Please check out the SENSOR WIRING CONFIGURATION in the MattzoLayoutController configuration. There you will find the sensors that are defined for your controller. The first sensor in the array has Rocrail port 1, the second 2 etc. This is hard-wired in the code. You should also try to monitor the MQTT queue using mosquitto_sub. This also helps to find errors.
Good luck!
Habe noch einmal geschaut. Grundsätzlich scheinst Du schon alles richtig gemacht zu habe. Die Example-Datei wird kopiert und kann dann modifiziert werden, ohne unter Quellecode-Kontrolle zu fallen. Einen Kommentar, dass man dort etwas nicht ändern soll, habe ich allerdings nicht gefunden.
Wünsche noch viel Erfolg!
Ist bekannt und die Kritik ist auch berechtigt. Ich habe gerade vor ein paar Wochen die Website-Struktur umgestellt. Daher herrscht derzeit ein bisschen Chaos bei der Doku. Wird besser, sobald ich etwas Zeit finde. Allgemein ist es allerdings tatsächlich eine Herausforderung, die gesamte Bandbreite der Dinge, die wir hier anbieten, didaktisch eingängig aber trotzdem übersichtlich darzustellen.
Richtig ist auch, dass wir nur einen Teil der Webseiten übersetzt haben – geht leider nicht anders. Die doppelsprachigen Webseiten sind sehr aufwendig zu pflegen und synchron zu halten.
>> The status LED indicates to WiFi connection status, the MQTT connection status and lights up when one or more sensors are triggered. The status LED is very handy in practice. <<
Abschnitt “Configuration”.Just to close this topic: I reviewed the issue, but couldn’t reproduce it. After having set-up dozens of trains with the current develop branch while doing regression testing for the upcoming firmware release, everything looks fine.
Hi Uli, the Mattzobricks community and the core development team is very active every day. I just didn’t have a lot of time lately to produce more video content. I hope it gets better, especially next autumn and winter.
Links on L-Gauge sound good. Could you contact lgauge and ask them? They can contact me for details any time if they wish.
Thanks!
Ich schaue mir das in den kommenden Tagen mal an und melde mich dazu. Es ist möglich, dass wir die Dinge an dieser Stelle etwas überkompliziert haben. Wir hatten da internm im Core Development Team auch schon mal zu diskutiert. Mit dem kommenden Release räume ich das ggf. mal etwas auf.
Du kannst übrigens immer noch die alte, Arduino-basierte Version vom MTC4PU verwenden. Schau mal in die Versionshistorie von der Firmware, bis zu welcher Version wir die noch dabei hatten.
For whatever reason, I had to scale the parts with a factor of 2,56. I am not sure if this is because of the stl files, or my cura settings… but then it just worked out fine.
Some hints:
1. The blade should be 40mm long (5 studs).
2. The distance between the holes of the spectacle holders must be precisely 8mm from middle to middle (1 stud).Let me know how it turned out.
It is great that you try this advanced feature. Overshoot sensors can be local or remote sensors.
Virtual sensors do not exist in the physical world, they represent events of some rocrail objects that are created within MattzoControllers (e.g. a switch has actually been switched, boom barriers are closed or a bascule bridge is fully open etc.).
Let me know if it works! 🙂
An passenden (d.h. 8mm breiten) Steckern, Buchsen und Schaltern gibt es einiges, so dass man es ganz gut integrieren kann. Ich selbst bevorzuge elektrische Magnetverbinder. Wenn ich Zeit habe, mache ich dazu noch ein Video.
Allgemein ist das Thema Batterien und Ladung natürlich ein Dauerthema. Da gibt es noch einiges zu erforschen, zu entwickeln und zubasteln.
Hi Dirk,
I will add some official examples to the source code with the next official firmware release. In the meantime, I will send you some example files via e-mail.The basic idea is as follows.
The controller_config.json file could look like this:
{
“name”: “MTC4BT-MULT3”,
“espPins”: [
],
“fn”: [
],
“locos”: [
],
“locoConfigs”: [
“/loco_e03.json”,
“/loco_br146.json”,
“/loco_est.json”
]
}The single files contain the structure that is usually located within the locos array in the main controller_config.json file, e.g.:
{
“address”: 103,
“name”: “E03”,
“speedStep”: 10,
“brakeStep”: 20,
“bleHubs”: [
{
“type”: “SBrick”,
“address”: “84:2e:14:4f:d6:04”,
“channels”: [
{
“channel”: “B”,
“attachedDevice”: “motor”,
“direction”: “forward”
},
{
“channel”: “D”,
“attachedDevice”: “motor”,
“direction”: “reverse”
}
]
},
{
“type”: “SBrick”,
“address”: “84:2e:14:51:79:8b”,
“channels”: [
{
“channel”: “A”,
“attachedDevice”: “motor”,
“direction”: “forward”
},
{
“channel”: “D”,
“attachedDevice”: “motor”,
“direction”: “reverse”
}
]
}
],
“fn”: [
{
“name”: “f2”,
“device”: “bleHub”,
“address”: “58:8e:81:58:b2:00”,
“channel”: “B”
}
]
}Voila.
No. I am presently busy motorizing and automating the Orient Express. After that, I will finish a couple of other projects and then hopefully be able to start working on important backlog issues like this one. Thanks for your patience.
We have supported 4DBrix Wifi Train Controllers for a long time, but apparently nobody was really interested in that. After I sold most of my 4DBrix stuff, I removed the 4DBrix support from the firmware in February 2022. 4DBrix is supported in older versions of the MTC4PF firmware only (versions before V1.0, I believe).
Not yet. We have created a feature request for this request. Once we find the necessary time, we’ll care about it. Maybe around Christmas. Thanks for your patience.
Hello Stefaan and all,
we have updated the Gerber files for the MLC mega, and linked it on this page:Hi Stefaan, I just uploaded the new Gerber files and linked it on the do-it-yourself page:
The old files missed indeed some layers, including the drilling layer.
I hope the new files works now.
Please let me know your results as soon as possible.
Thank you for your patience and your support.
We have already identified the problem. The drilling layer file is missing. We are going to fix that and put new Gerber files online.