Forum Replies Created

Viewing 25 posts - 26 through 50 (of 199 total)
  • Author
    Posts
  • in reply to: Different Motors different speeds #6425
    Matthias RunteMatthias Runte
    Keymaster

    Hi Max! I know that this had led to some discussion within the development team. The MTC4PF has the feature is adjusting the power by motor, but I need to look up if we implemented that for the MTC4BT as well. If not, I’ll file a feature request.

    in reply to: Which IR receiver 8884 needed? #6420
    Matthias RunteMatthias Runte
    Keymaster

    I do not quite remember, but I believe I tested it mainly with V2. Please state your results here once you have tried it.

    in reply to: Keine Controller ID im Mqtt #6416
    Matthias RunteMatthias Runte
    Keymaster

    Ich schaue noch mal, sobald ich selbst einen Controller angeschlossen habe. In der Zwischenzeit schau Dir mal das MQTT Log an. Da solltest Du auch fündig werden!

    in reply to: Keine Controller ID im Mqtt #6413
    Matthias RunteMatthias Runte
    Keymaster

    Nicht den Stecker ziehen, sondern den Reset-Taste drücken! Dann klappt es meistens besser!

    Matthias RunteMatthias Runte
    Keymaster

    Thanks for reporting this. We’ll have a look at it.

    Matthias RunteMatthias Runte
    Keymaster

    Thanks.

    Matthias RunteMatthias Runte
    Keymaster

    First of all, using 3D train studio as a simulator is a very good idea. I do this as well and it works really good. Congratulations of how far you came already.

    As a last resort, can you send me your Rocrail plan? It a file called “plan.xml” file? You can post it here or send it to me via e-mail.

    Matthias RunteMatthias Runte
    Keymaster

    True. I assume you entered the correct loco Address in Rocrail, as the serial log shows it. Please check for any leading or trailing spaces before or after the “103” in Rocrail and delete them. Besides that, I do not know what the problem might be. I suppose it’s something really simple, but one of those things that are like a needle in the haystack.

    Matthias RunteMatthias Runte
    Keymaster

    The configuration looks good to me. Are you sure that you copied the configuration file to the correct location, so that it is used during compile time?

    in reply to: Linearmotor anstatt Zugmotor ??? #6387
    Matthias RunteMatthias Runte
    Keymaster

    Derzeit leider nein. Wir sind in der “Sommerpause” und werden uns solchen Themen vermutlich erst im Herbst / Winter wieder widmen.

    in reply to: Linearmotor anstatt Zugmotor ??? #6384
    Matthias RunteMatthias Runte
    Keymaster

    Wir haben den Linearmotor bislang m.E. nicht ausprobiert. Wenn man etwas ändern muss, dann auf jeden Fall im MTC4BT Code, nicht in Rocrail.

    in reply to: Keine Controller ID im Mqtt #6383
    Matthias RunteMatthias Runte
    Keymaster

    Ich glaube, dass bei dem seriellen Monitorauszug ein paar Zeilen fehlen. Reboote doch mal den Controller und schaue, ob Du dann das volle Log bekommst. Dort sollte dann auch die MattzoControllerID stehen.

    Matthias RunteMatthias Runte
    Keymaster

    Hi Martin, could you post your full configuration file, please? Thanks!

    in reply to: Support for PFxBrick from FxBricks in Canada #6379
    Matthias RunteMatthias Runte
    Keymaster

    Hi Kim,
    we presently do not have plans to integrate the PFx brick into our eco-system.

    Cheers,
    Mattze

    in reply to: Bzgl. Fernbedienungen von PoweredUp #6324
    Matthias RunteMatthias Runte
    Keymaster

    Hallo Ralf,
    wir widmen uns derzeit anderen Projekten, so dass die Remote Control Lösung noch etwas warten muss. Die Lösung wird vermutlich eine Erweiterung des MTC4BT werden, aber das müssen wir noch final diskutieren.

    Gruß,
    Mattze

    in reply to: Two motors. Forwards and Backwards #6307
    Matthias RunteMatthias Runte
    Keymaster

    Confirmed. In firmware version V1.0.2, you need to you “reverse”. With V1.1, you can also use “backward” instead of “reverse”. We already updated the documentation, but we are running a bit late with the publication of the new firmware version V1.1.

    If you can’t wait, check out the development branch of the git repository for now.

    in reply to: VScode and OTA-update MattzoControllers #6304
    Matthias RunteMatthias Runte
    Keymaster

    Looking forward to it! By the way, I’d recommend the MTC4BT instead of the MTC4PU.

    in reply to: VScode and OTA-update MattzoControllers #6302
    Matthias RunteMatthias Runte
    Keymaster

    I am happy to hear that. You know that we have a “project” section in which I post some cool layouts of our users. Feel free to send me some media via e-mail. Thanks!

    in reply to: VScode and OTA-update MattzoControllers #6298
    Matthias RunteMatthias Runte
    Keymaster

    Hi Pieter,
    it’s always great to hear that people like our stuff.

    I am using OTA with VSCode. The idea is to configure some parameters in the [env] section of the my_platform.ini file:

    [env:esp12e]
    ; Use either the ‘upload_port’ line above if the ESP32 is connected to your PC’s USB port or enable/configure the three lines below to use OTA updates.
    ; The IP address should match that of the controller on your network.
    ; The should match the current password from the network_config.json you previously uploaded to the controller.
    ;upload_protocol = espota
    ;upload_port = 192.168.x.y
    ;upload_protocol = espota
    ;upload_flags = –auth=

    Remove the semicolons ahead of the parameters and configure them correctly.

    Does this help?

    If not, there is a lot of Mattzobricks-unspecific documentation on the web, you can find it easily via Google.

    Cheers,
    Mattze

    Matthias RunteMatthias Runte
    Keymaster

    No, that doesn’t work. The Trixbrix R40 double slip switch is, geometrically, pretty bad and incompatible to most of the situations in which you would like to use double slip switches, especially in parallel track situations. I told them and proposed an improved geometry already, but they didn’t build it yet. In the meanwhile and if you have the space, you should try R104 switches and double slip switches. They are perfect for what you are trying.

    in reply to: VSCODE errors on standard MTC4PF firmware? #6228
    Matthias RunteMatthias Runte
    Keymaster

    Sounds good! All the best for your further experiments!

    in reply to: Mosquitto 2 and MQTT #6074
    Matthias RunteMatthias Runte
    Keymaster

    You mean as documented on the Mattzobricks website?

    General Section

    (section “MQTT”).

    in reply to: MLC with Port Extender 9685 #6054
    Matthias RunteMatthias Runte
    Keymaster

    Happy to hear that!

    in reply to: MLC with Port Extender 9685 #6053
    Matthias RunteMatthias Runte
    Keymaster

    Another message from Dave:

    Thanks Matthias, your suggestion solved the issue and your explanation also helped me to understand how the process works too – seems obvious now!

    After making the necessary changes, happy to confirm that it works and I’ve put another switch servo and signal in too, just to check!

    in reply to: MLC with Port Extender 9685 #6051
    Matthias RunteMatthias Runte
    Keymaster

    Hi Dave,
    it’s great that you pasted the debug console output and your config file.

    To fix the servo problem, please find this line:

    .servoIndex = 7,

    and replace the 7 with a 4.

    .servoIndex = 4,

    To fix the signals, you need to replace this line:

    .aspectLEDPort = {4, 5},

    so that it looks like this:

    .aspectLEDPort = {0, 1},

    The reason is that you need to refer from the logical component (switch, signal) to the zero-based index of the array of the physical component (servo, LED).

    Hope this fixes your issues.

Viewing 25 posts - 26 through 50 (of 199 total)