• Author
    Posts
  • AndreyAndrey
    Participant
    @andybig
    Post count: 49

    It is very likely that the speeds of the ports of the MCU and the display do not match a little.

  • Francesco FiaccabrinoFrancesco Fiaccabrino
    Participant
    @minimo55
    Post count: 19

    Baud rate is set to 115200. For more precision, I connected the display through serial adapter set to TTL, powered with an external DC power supply and connected to PC via USB. Other baud rates generate rubbish. Pressing the same button from display produces the same data packet. Any suggestion from STONE staff?

  • Francesco FiaccabrinoFrancesco Fiaccabrino
    Participant
    @minimo55
    Post count: 19

    Hi everyone,

    I resolved independently: the P2 jumper setting was wrong. They must be set to RS232 and not to TTL.

    In summary, for benefit of those who want to check the communication of the display, it is necessary to use the usb to serial adapter powered at 12 V (jumper P1= PWR). Connect the PC through the USB port, setting jumpers P2 to RS232 (not TTL). The software sscom32e.exe or equivalent is used (for example AI Thinker). The “hexdata” box is activated to correctly see the hexadecimal codes coming from the display.

     

     

  • AndreyAndrey
    Participant
    @andybig
    Post count: 49

    Useful information, thanks. Now I will know how the display with the terminal behaves with incorrect jumpers 🙂 Although I have displays with RS-485, but the information is never superfluous 🙂

You must be logged in to reply to this topic.