Forum Replies Created

Viewing 18 posts - 1 through 18 (of 18 total)
  • Author
    Posts
  • in reply to: controller_config.json #4962
    Steven ElstonSteven Elston
    Participant

    I set my localhost to the ip address, but I am still figuring out rocrail. I got the motor to respond but cannot get the lights to work. did you look at the debug script running to make sure everything is communicating? Rocrail is complex, I just started on the wiki tutorial and can’t even get the demo to run correctly :0

    I am glad you were able to get the MQTT working.

    in reply to: Update firmware v.0.5.0 to 0.5.1 #4960
    Steven ElstonSteven Elston
    Participant

    Thanks Raymond!

    in reply to: controller_config.json #4959
    Steven ElstonSteven Elston
    Participant

    I had a thought…maybe your router needs to have port 1883 open to pass?

    in reply to: BuWizz 3.0 Pro #4958
    Steven ElstonSteven Elston
    Participant

    Ok. Thank you for your response.

    in reply to: controller_config.json #4948
    Steven ElstonSteven Elston
    Participant

    👍

    • This reply was modified 2 years, 3 months ago by Steven ElstonSteven Elston.
    in reply to: controller_config.json #4945
    Steven ElstonSteven Elston
    Participant

    Yes-here: Controllers->firmware, under code structure: If you use one or more of the Arduino based controllers (MTC4PF, MTC4PU, MLC), then you need to MOVE (NOT COPY!) the files in the “library” folder to the Arduino library folder. On Microsoft Windows, do something similar like:

    Navigate to C:\Users\Mattze\Documents\MattzoController\libraries
    Move the “MattzoBricks” folder to C:\Users\Mattze\Documents\Arduino\libraries
    The exact directory names will vary on your computer system.

    The following table contains a list of files and their purpose as of firmware version

    **that is what I remembered** Sorry if it doesn’t help. I am learning just like you! 🙂

    in reply to: controller_config.json #4944
    Steven ElstonSteven Elston
    Participant

    Before I lead you down a wrong path, I was just referring to the newtork json mqtt broker entry that you already have. Sorry for the confusion. I do remember reading in the tutorial about having to move and not copy some certain file(s) into the Arduino folders let me see if I can reference them.

    in reply to: controller_config.json #4941
    Steven ElstonSteven Elston
    Participant

    ah, yes..I was looking at your details wrong. 🙁 I am a novice at this system as well. 😮 I was having the same issue with MQTT until I ran the command prompt. In your mosquitto.conf file, located in C:/program files -> mosquitto you have the same ‘allow_anonymous true’ and ‘listener 1883. that you have in you VS script? that was a mistake I made earlier..

    in reply to: controller_config.json #4939
    Steven ElstonSteven Elston
    Participant

    The IP address for the MQTT and the wifi are both the same on my machine as I run the entire system from a laptop. I do see that you have .210 and .233 maybe that is the issue?

    in reply to: esp32doit-devkit-v1 #4927
    Steven ElstonSteven Elston
    Participant

    OK, it is running off a USB power brick so Other than tweaking, I can say that the esp32doit-devkit-v1 (https://www.amazon.com/ESP32-WROOM-32-Development-ESP-32S-Bluetooth-Arduino/dp/B084KWNMM4) does work

    • This reply was modified 2 years, 3 months ago by Steven ElstonSteven Elston. Reason: added link
    in reply to: esp32doit-devkit-v1 #4926
    Steven ElstonSteven Elston
    Participant

    Whohoo! Got the motor running in rocrail! now I just need to fingure out how to make the lights works and the 10,000 other things I need to learn about it….

    in reply to: esp32doit-devkit-v1 #4925
    Steven ElstonSteven Elston
    Participant

    Got mosquitto to work by shutting off service in windows services and ran mosquitto -c mosquitto.conf -v from the cmd window from the mosquitto dir. probably will put that as a startup command in the window services

    in reply to: controller_config.json #4924
    Steven ElstonSteven Elston
    Participant

    brachte mosquitto zum Laufen, indem er den Dienst in den Windows-Diensten abschaltete und mosquitto -c mosquitto.conf -v aus dem cmd-Fenster aus dem mosquitto-Verzeichnis ausführte. wird das wahrscheinlich als Startbefehl in die Windows-Dienste einfügen

    got mosquitto to work by shutting off service in windows services and ran mosquitto -c mosquitto.conf -v from the cmd window from the mosquitto dir. probably will put that as a startup command in the window services

    • This reply was modified 2 years, 3 months ago by Steven ElstonSteven Elston. Reason: added poor translation
    in reply to: esp32doit-devkit-v1 #4923
    Steven ElstonSteven Elston
    Participant

    — 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
    — Miniterm on COM32 115200,8,N,1 —
    — Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H —

    [1] Setup: Starting MattzoTrainController for BLE…
    [1] Setup: Loading network configuration…
    Syslog: Server: redacted:514
    Syslog: Hostname: mtc4bt
    Syslog: Appname: MTC4BT
    [1] Logging: Configured.
    [1] Setup: Loading controller configuration…
    [1] Config: Read controller name: YourControllerNameHere
    [1] Config: Read ESP pin configuration (2).
    [1] Config: Read function configuration (1).
    [1] Config: Read function configuration (2).
    [1] Config: Read loco configuration (1).
    [1] Ctrl: Found status led attached to ESP pin 23. Initializing…
    [1] Trying to retrieve an ESP pin number from a non ESP pin device.
    [1] Setup: Initializing BLE…
    [1] Setup: Controller configuration completed.
    [1] BLE : Scanning for 1 hub(s)…
    [0] BLE : Discovered unknown device: (4f:b4:c9:f5:fc:d6).
    [1] Wifi: Connecting to Link Down.[1] MQTT: Connecting to redacted:1883…
    [1] Setup: MattzoTrainController for BLE running.
    [1] Setup: Number of locos to discover hubs for: 1
    [0] BLE : Discovered unknown device: (32:a2:95:a6:45:51).
    [0] BLE : Discovered hub: HUB NO.4 (90:84:2b:be:e2:11).
    [1] BLE : Scanning for 1 hub(s) aborted.
    [0] Wifi: Connected (IPv4: redacted.46).
    [0] OTA: Initialized.

    —-Got the ESP32 to connect the wifi (had an underscore between words on my SSID)—-

    Now I just have to figure out why MQTT is not working…..

    [0] MQTT: Subscriber configuring last will…
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [0] MQTT: Subscriber attempting to connect…
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [1] BLE : Connecting to hub ’90:84:2b:be:e2:11’…
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [1] BLE : Connected to hub ’90:84:2b:be:e2:11′.
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [1] BLE : Watchdog timeout successfully set to s/10:
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [1] Loop: Connected to all hubs of loco ‘60198 Cargo Train’.
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [0] port 0 is connected with device 2
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [0] port 1 is connected with device 8
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [0] Found RGB light at port 32
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [E][WiFiUdp.cpp:183] endPacket(): could not send data: 12
    [E][WiFiClient.cpp:258] connect(): socket error on fd 56, errno: 113, “Software caused connection abort”
    [0] MQTT: Subscriber connect failed, rc=4294967294. Try again in a few seconds…
    [0] MQTT: Subscriber configuring last will…
    [0] MQTT: Subscriber attempting to connect…
    [E][WiFiClient.cpp:258] connect(): socket error on fd 57, errno: 113, “Software caused connection abort”
    [0] MQTT: Subscriber connect failed, rc=4294967294. Try again in a few seconds…
    [0] MQTT: Subscriber configuring last will…
    [0] MQTT: Subscriber attempting to connect…
    Exception in thread rx:

    in reply to: controller_config.json #4922
    Steven ElstonSteven Elston
    Participant

    Ändern Sie Ihren MAC: „96:35:3D:19:FD:C8“ in Kleinbuchstaben: „96:35:3d:19:fd:c8“ und versuchen Sie das. Ich habe das gleiche Problem mit dem MQTT-Broker….

    change your MAC : “96:35:3D:19:FD:C8” to lower case letters: “96:35:3d:19:fd:c8” and try that. I am having the same issue with the MQTT broker….

    • This reply was modified 2 years, 3 months ago by Steven ElstonSteven Elston. Reason: added poor translation
    in reply to: esp32doit-devkit-v1 #4900
    Steven ElstonSteven Elston
    Participant

    DO these ESP32’s work on 2.4Ghz or 5Ghz? I tried the Network_config with both and didn’t see anything change. I am assuming that they work over WPA2-PSK [AES] since they need a PWD in the file. Gonna take a break for the rest of the night-too much line programming for me today.

    in reply to: esp32doit-devkit-v1 #4899
    Steven ElstonSteven Elston
    Participant

    Thanks for the reply. Yeah, I have MAC filtering on my Router and I dont see a new device trying to get on the wifi…I looked at my network_config.json file, nothing really sticks out as being incorrect.

    in reply to: esp32doit-devkit-v1 #4896
    Steven ElstonSteven Elston
    Participant

    Ok, I think I have my upload done correctly. I ran the serial Monitor after upload and this is what I got:

    > Executing task in folder Train test: C:\Users\Brickbuilder\.platformio\penv\Scripts\platformio.exe device monitor <

    — 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
    — Miniterm on COM32  115200,8,N,1 —
    — Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H —
    ts Jun  8
    [1] Setup: Starting MattzoTrainController for BLE…
    [1] Setup: Loading network configuration…
    Syslog: Server: 192.168.x.y:514
    Syslog: Hostname: mtc4bt      
    Syslog: Appname: MTC4BT
    [1] Logging: Configured.
    [1] Setup: Loading controller configuration…
    [1] Config: Read controller name: YourControllerNameHere
    [1] Config: Read ESP pin configuration (2).
    [1] Config: Read function configuration (1).
    [1] Config: Read function configuration (2).
    [1] Config: Read loco configuration (1).
    [1] Ctrl: Found status led attached to ESP pin 23. Initializing…
    [1] Trying to retrieve an ESP pin number from a non ESP pin device.
    [1] Setup: Initializing BLE…
    [1] Setup: Controller configuration completed.
    [1] BLE : Scanning for 1 hub(s)…
    [1] Wifi: Connecting {redacted}.[1] MQTT: Connecting to {redacted}:1883…
    [1] Setup: MattzoTrainController for BLE running.
    [1] Setup: Number of locos to discover hubs for: 1
    [0] BLE : Discovered hub: HUB NO.4 (90:84:2b:be:e2:11).
    [1] BLE : Scanning for 1 hub(s) aborted.
    [1] BLE : Connecting to hub ’90:84:2b:be:e2:11’…
    [1] BLE : Connected to hub ’90:84:2b:be:e2:11′.
    [1] BLE : Watchdog timeout successfully set to s/10:
    [1] Loop: Connected to all hubs of loco ‘60198 Cargo Train’.
    [0] port 0 is connected with device 2
    [0] port 1 is connected with device 8
    [0] port 32 is connected with device 17
    [0] Found RGB light at port 32
    [0] port 3b is connected with device 15
    [0] port 3c is connected with device 14

    Does this seem to be correct? I have never used Rocrail, so that is my next learning step

Viewing 18 posts - 1 through 18 (of 18 total)