Forum Replies Created
-
Posts
-
Thanks Hilbert, a quick reset of the controller and all seemed well. Only got a bit of time to mess around with it again this weekend but managed to get a second train up and running so thank you! I don’t suppose you have any tips on reducing the wait between blocks on auto routing? All routes are mapped and reserve second block / release block on enter are set etc but still seems to take an age for the engine to be assigned a new block to take. My next guess when I get some time is to individually edit the block wait parameters.
Dave
Well that clears that up then! In terms of Rocrail, I have added a train and can see that the MTC4BT has located the physical PU hub. How do I now control the hub via Rocrail? The routes are set and I can see the assignment is correct for the train to a block and then the subsequent block it should travel to. I have set the address in the Address in the Interface Tab as ‘1’ as that is the only loco configured in the code. I can see that Rocrail is sending a speed command to the hub as it is writing it out in the serial log – but there is no movement from the motors? I have tried both A and B ports. I have a feeling it has something to do with the ‘virtual’ mode next to the speed properties etc in the Loco window. Sorry to keep pestering!
Dave
Thanks for that, I have the MAC address of my PU hub and I am happy in being able to find future hub addresses when ready. Instead, I think I am looking for the ControllerID as referenced in the section “The Serial Monitor” at the webpage https://mattzobricks.com/automation/controllers/general where the ID referenced is 9990. I presume this information is then necessary for the configuration of the locomotives in Rocrail, under the Properties tab > Node ID box or am I barking up the wrong tree?
Dave
Thanks Hilbert, to avoid any confusion, I have just freshly downloaded the latest Firmware and the serial no longer has that line, but neither does it have an ID? Here is the current serial and all I did this time was copy/paste the example controller_config into my own data folder. Apart from changing the name, nothing different to the example controller_config this time around. Have also double checked that the board (AZ Dev4) and Platform (espressif32) are current and correct.
— Terminal on COM3 | 115200 8-N-1
— Available filters and text transformations: colorize, debug, default, direct, esp32_exception_decoder, hexlify, log2file, nocontrol, printable, send_on_enter, time
— More details at https://bit.ly/pio-monitor-filters
— Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H[1] Setup: Starting MattzoTrainController for BLE…
[1] Setup: Loading network configuration…
[0000] [1] Logging: Configured.
[0001] [1] Setup: Loading controller configuration…
[0002] [1] Config: Read controller name: TestMTC
[0003] [1] Config: Read ESP pin configuration (2).
[0004] [1] CTRL: Local channels initialized.
[0005] [1] Setup: Initializing BLE…
[0006] [1] Setup: Controller configuration completed.
[1] Wifi: Connecting to GC.[0007] [0] BLE : Scanning for 3 hub(s)…
[0008] [0] BLE : Discovered unknown device: (11:76:b8:fa:c2:f1).
.
[0009] [1] MQTT: Connecting to 192.168.1.100:1883…
[0010] [1] Setup: MattzoTrainController for BLE running.
[0011] [1] Setup: Number of locos to discover hubs for: 3
[0012] [1] Setup: Number of locos to discover hubs for: 3
[0013] [1] MQTT: Subscriber configuring last will…
[0014] [1] MQTT: Subscriber attempting to connect…
[0015] [1] MQTT: Subscriber connected
[0016] [1] MQTT: Subscriber subscribed to topic ‘rocrail/service/command’
[0017] [0] BLE : Scanning for 3 hub(s) aborted.
[0018] [0] BLE : Scanning for 3 hub(s)…
