locoduino / labox Goto Github PK

Could this disturbing shift of a 2 pace between the display of LaBox and the smartphone be removed ?

Typical sequence :

Power on LaBox
Display On icon
Power on smartphone + EngineDriver
Wifi connexion
Blinking quote on display
Engine 36 selection on EngineDriver
Display 36 pace 2
Hit Arrêt on EngineDriver, EngineDrivershows pace 0 then 5" later 2. Still pace 2 on display
After changing speed and back to 0 with EngineDriver, 5" later 2. Still pace 2 on display.

Hit Arrêt on EngineDriver, and immediately Arrière shows pace 0 on display but 5" later pace 2 on EngineDriver, and still 0 on display.

On the tracks we have the speed which is shown on the display i.e. Stop for pace 0, and 2 for pace 2.
LaBox does not go to 0 with the slide bar of EngineDriver and stays to 2 .

With Withrottle, IOS, fonctions buttons seems to be taken into account:

• Light : display a star on Oled screen and light is on on the loco
• F1..F18 : display the number of the last function on Oled

But another press on the button never stop the function

If <1> and <0> from serial puts the track ON and OFF, other orders are not taken into account although ESP32 blinks.

For the future versions of LaBox (but let finish the current one)

It could be interesting to foresee the use of another display even not I2C (Now : SSD1306Wire.h)

like this 1.44/1.80
https://www.ebay.fr/itm/1-44-1-8inch-TFT-Full-Color-128x160-128x128-SPI-LCD-Display-Module-for-Arduino/193545945157
which needs :
#include <TFT_eSPI.h> // Graphics and font library for ST7735 driver chip
#include <SPI.h>
TFT_eSPI tft = TFT_eSPI(); // Invoke library, pins defined in User_Setup.h
Reference to display should appear in a single point in order to make the change easy.

Pour le 12V :
un bug du bootloader non corrigé laisse GPIO0 HIGH :
https://www.esp32.com/viewtopic.php?t=2205
il peut être contourné avec :
REG_WRITE(GPIO_FUNC0_OUT_SEL_CFG_REG, SIG_GPIO_OUT_IDX);

The AutotestSensor example allows you to test LaBox in complete autonomy.
The blinking of the lights and the back and forth movements of loco 3 validate its operation.
Incidentally, in the test I did, pin 12 (PIN_BTN_SEL) remained inactive.
It would be interesting to put this autotest as a function accessible from a HMI menu.
Anyone could customize this function whose script is clear.