Forum Replies Created
-
Posts
-
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.
Thanks again for your feedback. I have taken the file off the network for now. We are going to research the matter and get back to you here.
Hallo Ralf, seit 0.51 hat sich sehr viel geändert. Sobald die “Saison” wieder begonnen hat, schaue ich da mal näher rein und sehe mir das mal an. Wenn ich Dich richtig verstanden habe, kommst Du aber durch Ändern der Werte erst einmal klar, oder?
Thank you for the information. We are presently researching the issue.
After reviewing the Gerber files again, we are not sure yet if there is a problem at all and what might be the cause for your ordering problems. We successfully used the downloadable Gerber files on the website to order a larger stack of PCs for ourselves.
We will get back to you in this forum as soon as we have new findings.
Hello Stefaan,
please try to order the PCBs at https://jlcpcb.com. Our PCB expert has ordered all of the PCBs there the we use in the Mattzobricks lab, and he said it worked without problems. Just leave all configuration options at default, this should do.Michael, ich habe noch einmal oben geschaut. Du hast da ja einen MTC4PF gebaut. Der erzeugt zwar inter auch eine MattzoControllerID, diese ist aber für die Einrichtung in Rocrail unerheblich.
Für MLCs ist die MattzoControllerID hingegen entscheidend. Sie wird beim MLC mit an den Hostname gehängt und kann dann einfach über das MQTT-Log herausgefunden werden.
Es gibt in der Doku dazu einen Abschnitt “Fetching the MattzoControllerID via MQTT”.
Viel Erfolg!