Verfasste Forenbeiträge
-
Beiträge
-
Hi Achim,
first of all: I like your WiFi SSID. According to the log, the controller did not connect to the WiFi correctly. Did you install a status LED on pin D8? That’s sometimes quite helpful. Flashing means: no wifi connection. Blinking means: no mqtt connection.Good luck!
Cheers,
MattzeHi Ulrich, thanks for the heads up. I fixed that in the wiring diagram. Now it should be at least a bit easier to get going without the need if understanding every little detail in the code and configuration.
Cheers,
MattzeYour observation is correct. The Powered Up hubs must be connected in exactly the order they are listed in the configuration. The reason for this are technical limitations in the Powered Up and Bluetooth libraries that we use to connect to the Powered Up hubs.
I am quite positive that we will find a better for this in the future.
Cheers,
MattzeHi Nikos,
that’s interesting. I did not experience that hub name problem here, and neither did any of the testers. We will observe if we get more feedback into this direction.I agree that the PU hubs sometimes do not reconnect so quickly after uploading a new firmware to the ESP-32, but as they are specifically addressed with their MAC ID, a real bluetooth pairing as such should not be required at all. But please keep on posting your findings, they are all interesting.
Cheers,
MattzeHello Erik,
looks as if you did not choose the correct ESP32 controller in the Arduino IDE.Cheers,
MattzeWiring and pin configuration depend on each other. I think you are right that the example configuration does not exactly match the wiring diagram. I try to fix that with the next release. Anyway, there will be never be one example configuration file that fits all possible scenarios, so a bit of adaption is always required.
Ok. Can you post the lines from the serial monitor where the controller parses the command and tries to flip the switch?
Hi Paul,
we believe that we do no longer need the logic level controller. Sufficient power should do. You should power up a switch controller with an USB-Charger of 2 Amps minimum. Higher voltage is helpful as well.But I am not sure that this is the problem here. Did you connect your MattzoSwitchController to your PC and checked the output on the serial monitor? Do you see that it is connected to WiFi and MQTT and actually parsing the switch commands and trying to turn the servo?
One more important thing is the mapping of the port numbers. Port No. 1 in Rocrail corresponds to port no. 0 internally in the controller.
Good luck!
Cheers,
MattzePaul Verkaik,
did you monitor MQTT, e.g. with mosquitto_sub? What do you see there? And does the switch visibly switch on the Rocrail layout?Cheers,
MattzeHello Henk Jansen, did you try to upload a simple sketch from the standard demos that just turns a servo back and forth? You should probably try to get such a sketch working first. Be careful not to break your switch motor, you should only use angles between 70 and 80 for testing if it’s a TrixBrix switch motor.
Cheers,
MattzeAs written in the documentation, the wiring to measure the battery voltage on pin A0 are not required for the present version of the firmware, as they are not really used to recalibrate the train speed when the battery voltage decreases. Anyways, you can build the controller now as specified and wait for the firmware upgrade in which the logic will be introduced.