0
edits
Changes
Created page with "==Mode== {| style="width: 100%" |right RS-485 supports only half-duplex communication, which means data is transferred only one way at a time.<br />Whe..."
==Mode==
{| style="width: 100%"
|[[File:RS485 Mode.png|right]]
RS-485 supports only half-duplex communication, which means data is transferred only one way at a time.<br />When activated RS-485 driver chip draws constant current, when entering Sleep or Deep sleep RS-485 will be powered off.
|}
==120Ohm Termination Resistor==
{| style="width: 100%"
|[[File:RS485_120ohm_resistor.png|right]]
<i>* This parameter works only with 31 hardware version.</i><br><br>
Enables or disables the termination resistor.
|}
==RS485 Mode==
[[File:RS485_Settings_Mode.png|right]]
*<code>Log Mode</code> - RS-485 prints TFT100 device log and does not respond to commands (Transmit mode).
*<code>NMEA</code> - RS-485 prints GNSS NMEA log and does not respond to commands (Transmit mode).
*<code>TCP ASCII/Binary</code> - In TCP ASCII/Binary mode a link with an external device using text messages can be established. In TCP ASCII/Binary mode all data received from external device through RS-485 is sent directly to server (if link is currently active). Data is encapsulated in codec 12 format.
*<code>Super Soco</code> - Super Soco mode which is used by Super Soco e-scooters. Default settings are: 9600 Baudrate, Parity: none. When this mode is selected user will be able to read Super Soco e-scooter specific data via RS485.
==RS485 Baudrate==
{| style="width: 100%"
|[[File:RS485 Baudrate.png|right]]
RS485 Baudrate selection.<br>
<i>Not available in the Log Mode.</i>
|}
==RS485 Parity==
{| style="width: 100%"
|[[File:Parity.png|right]]
Parity selection.
|}
==TCP Binary Mode settings==
[[File:TCP_Binary_Mode.png|right]]
TCP Binary has a setting Prefix. It is possible to set '''Prefix 1''', '''Prefix 2''' or '''Prefix 3'''. These prefixes can be used separately or in unison.
To configure this setting a value from 0 to 255 in decimal has to be entered. Device will convert this value to HEX and compare the 1st, 2nd or 3rd byte from incoming data. If the values do not match, device will not accept incoming data.
Example:<br>
Incoming packet through RS485 using TCP Binary mode - <code><font color="red">50</font> <font color="green">72</font> <font color="blue">65</font> 66 69 78 20 57 6f 72 6b 69 6e 67</code>
*If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX. TFT100 device will then check the 1st byte of incoming data and compare to the set Prefix 1.
*If Prefix 2 is set to 114 in decimal, it is equal to <font color="green">72</font> in HEX. TFT100 device will then check the 2nd byte of incoming data and compare to the set Prefix 2.
*If Prefix 3 is set to 101 in decimal, it is equal to <font color="blue">65</font> in HEX. TFT100 device will then check the 3rd byte of incoming data and compare to the set Prefix 3.
When values match, data will be accepted and sent to server.<br>
<br>
Incoming packet through RS485 using TCP Binary mode - <code><font color="red">50</font> <font color="green">0</font> <font color="blue">65</font> 66 69 78 20 57 6f 72 6b 69 6e 67</code>
*If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX. TFT100 device will then check the 1st byte of incoming data and compare to the set Prefix 1.
*If Prefix 2 is set to 114 in decimal, it is equal to <font color="green">72</font> in HEX. TFT100 device will then check the 2nd byte <font color="green">0</font> of incoming data and compare to the set Prefix 2.
Since Prefix 2 does not match incoming 2nd byte, data will not be accepted.
{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |Description how to test '''TCP link mode''' (transparent mode) with RS232 and RS485 can be found [[Testing TCP link mode with RS232 and RS485|here]].
|}
[[Category:TFT100 Configuration]]
{| style="width: 100%"
|[[File:RS485 Mode.png|right]]
RS-485 supports only half-duplex communication, which means data is transferred only one way at a time.<br />When activated RS-485 driver chip draws constant current, when entering Sleep or Deep sleep RS-485 will be powered off.
|}
==120Ohm Termination Resistor==
{| style="width: 100%"
|[[File:RS485_120ohm_resistor.png|right]]
<i>* This parameter works only with 31 hardware version.</i><br><br>
Enables or disables the termination resistor.
|}
==RS485 Mode==
[[File:RS485_Settings_Mode.png|right]]
*<code>Log Mode</code> - RS-485 prints TFT100 device log and does not respond to commands (Transmit mode).
*<code>NMEA</code> - RS-485 prints GNSS NMEA log and does not respond to commands (Transmit mode).
*<code>TCP ASCII/Binary</code> - In TCP ASCII/Binary mode a link with an external device using text messages can be established. In TCP ASCII/Binary mode all data received from external device through RS-485 is sent directly to server (if link is currently active). Data is encapsulated in codec 12 format.
*<code>Super Soco</code> - Super Soco mode which is used by Super Soco e-scooters. Default settings are: 9600 Baudrate, Parity: none. When this mode is selected user will be able to read Super Soco e-scooter specific data via RS485.
==RS485 Baudrate==
{| style="width: 100%"
|[[File:RS485 Baudrate.png|right]]
RS485 Baudrate selection.<br>
<i>Not available in the Log Mode.</i>
|}
==RS485 Parity==
{| style="width: 100%"
|[[File:Parity.png|right]]
Parity selection.
|}
==TCP Binary Mode settings==
[[File:TCP_Binary_Mode.png|right]]
TCP Binary has a setting Prefix. It is possible to set '''Prefix 1''', '''Prefix 2''' or '''Prefix 3'''. These prefixes can be used separately or in unison.
To configure this setting a value from 0 to 255 in decimal has to be entered. Device will convert this value to HEX and compare the 1st, 2nd or 3rd byte from incoming data. If the values do not match, device will not accept incoming data.
Example:<br>
Incoming packet through RS485 using TCP Binary mode - <code><font color="red">50</font> <font color="green">72</font> <font color="blue">65</font> 66 69 78 20 57 6f 72 6b 69 6e 67</code>
*If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX. TFT100 device will then check the 1st byte of incoming data and compare to the set Prefix 1.
*If Prefix 2 is set to 114 in decimal, it is equal to <font color="green">72</font> in HEX. TFT100 device will then check the 2nd byte of incoming data and compare to the set Prefix 2.
*If Prefix 3 is set to 101 in decimal, it is equal to <font color="blue">65</font> in HEX. TFT100 device will then check the 3rd byte of incoming data and compare to the set Prefix 3.
When values match, data will be accepted and sent to server.<br>
<br>
Incoming packet through RS485 using TCP Binary mode - <code><font color="red">50</font> <font color="green">0</font> <font color="blue">65</font> 66 69 78 20 57 6f 72 6b 69 6e 67</code>
*If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX. TFT100 device will then check the 1st byte of incoming data and compare to the set Prefix 1.
*If Prefix 2 is set to 114 in decimal, it is equal to <font color="green">72</font> in HEX. TFT100 device will then check the 2nd byte <font color="green">0</font> of incoming data and compare to the set Prefix 2.
Since Prefix 2 does not match incoming 2nd byte, data will not be accepted.
{| class="wikitable" style="border-style: solid; border-width: 0px;"
|+
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!'''
| style="width: auto; text-align: left; background: #F6F6FB;" |Description how to test '''TCP link mode''' (transparent mode) with RS232 and RS485 can be found [[Testing TCP link mode with RS232 and RS485|here]].
|}
[[Category:TFT100 Configuration]]