TFT100 CAN I/O settings

From Wiki Knowledge Base | Teltonika SAS
Main Page > SAS Micro Mobility > TFT100 > TFT100 Configuration > TFT100 CAN I/O settings

CAN I/O


CAN Protocol.gif

CAN I/O category offers users an ability to select one of CAN protocols to read specific data through TFT100 CAN interface.
To select the preferred CAN protocol, click one of the given values in CAN Protocol field.

TFT100 currently has 5 implemented CAN protocols:
- Bosch CAN Powertrain
- Askoll
- Default J1939
- Manual CAN
- Manual J1939

  • Bosch, Askoll and Default J1939 CAN protocols come with specific CAN I/O parameters that can be read, monitored, configured and their values sent to the configured server.
  • Manual CAN and Manual J1939 protocols does not include dedicated specific I/O parameters however it welcomes user to configure what has to be read from the transport based on their transport CAN communication protocol.


More information can be found in the protocol sections below.

Bosch CAN Powertrain


Bosch CAN Powertrain protocol.gif

Bosch CAN Powertrain protocol allows users to read parameters from their transport, if the transport uses Bosch motor. The protocol is enabled by selecting Bosch parameter in CAN Protocol field as shown in the image on the right hand side.




Bosch CAN Powertrain I/O


Specific Bosch CAN Powertrain I/O parameters were implemented to our device's firmware that can be read, configured and sent to the server just like regular I/O parameters. The parameters that were added can be seen in the image below.

NOTE! The parameters were added upon clients' request. Bosch CAN protocol contains way more parameters that can be added by us if necessary.

Bosch CAN Powertrain IO.gif

  • The AVL ID list of Bosch CAN Powertrain parameters can be found in here.
  • SMS/GPRS commands that were developed for Bosch CAN Powertrain protocol can be found in here.

Askoll


Askoll protocol v2.gif

Askoll CAN protocol allows users to read parameters from their e-scooters manufactured by Askoll. The protocol is enabled by selecting Askoll parameter in CAN Protocol field as shown in the image on the right hand side.




Askoll I/O


Specific Askoll I/O parameters were implemented to our device's firmware that can be read, configured and sent to the server just like regular I/O parameters. The parameters that were added can be seen in the image below.
Askoll CAN IO.gif

  • The AVL ID list of Askoll parameters can be found in here.
  • SMS/GPRS commands that were developed for Askoll protocol can be found in here.

Default J1939


Default J1939 ss.png

Default J1939 protocol support was added to TFT100 device's firmware since it is one of the most popular CAN protocols used in heavy duty (i.e. forklifts) machinery industry. If the machinery communicates via J1939 CAN protocol, the device will be able to read provided parameter's data and transmit readings to your configured server. To use Default J1939 CAN protocol user should select Default J1939 parameter in CAN Protocol field as shown in the image on the right hand side.

NOTE! Default J1939 can be tested on FW 55.00.09.rev.04 or newer

To read data with this functionality, the user must have:

  • TFT100 device with CAN interface;
  • 55.00.09.Rev.04 or newer firmware;
  • Machinery with CAN interface, which communicates via J1939 protocol.

J1939 Settings


J1939 Settings.png

Some J1939 PGN’s are not sent periodicaly, so they must be requested. In order to request PGN device must be registered to J1939 network. To register device user should configure J1939 Source Address and J1939 Name parameters:

  • J1939 Source Address parameter is used to set TFT source address on J1939 network. If device with selected source address already exists on network, user should change it to another address which might be free, or PGN’s which must be requested will not be received.
  • J1939 Name parameter is used to set TFT name on J1939 network.

Default J1939 I/O


All Default J1939 CAN I/O parameters can be configured like standard I/O parameters. User can set priority, high level, low level parameter limits, eventual record, operand, SMS text and number to which SMS notification would be sent. Default J1939 IO gif.gif

  • The AVL ID list of Default J1939 parameters can be found in here.

Manual CAN


Manual CAN protocol v2.gif

The Manual CAN protocol is enabled by selecting Manual CAN parameter in CAN Protocol field as shown in the image on the right hand side. Then user can configure CAN parameters in Manual CAN Settings tab.

NOTE! Manual CAN can be tested on FW 55.00.09.rev.04 or newer

The main benefit, of using Manual CAN functionality is that user is able to read data via CAN BUS without requiring additional CAN protocol development from the device's firmware side. To read data with this functionality, the user must have:

  • TFT100 device with CAN interface;
  • 55.00.09.Rev.04 or newer firmware;
  • Transport with CAN interface;
  • Transport's CAN communication protocol (with information about frames, parameters, ID's, baud rate).

Manual CAN I/O


Up to 30 I/O parameters (Priority, Event Only, Operand, Send SMS To, SMS text) for Manual CAN functionality can be configured in CAN I/O tab.

NOTE! It is important to not forget that Manual CAN Settings tab must be configured as well.

Manual CAN IO.gif

  • The AVL ID list of Manual CAN parameters can be found in here.
  • Full Manual CAN and Manual CAN Settings description can be found in here.
  • Example on how to configure Manual CAN functionality can be found in here.

Manual J1939


Manual J1939.gif

Manual J1939 protocol support was added to TFT100 device's firmware as an addition to Default J1939 protocol in case the given Default J1939 I/O elements are not enough. With this functionality, the user is able to configure which J1939 parameters he would like to read from the transport that uses J1939 protocol. Manual J1939 protocol is enabled by selecting Manual J1939 parameter in CAN Protocol field as shown in the image on the right hand side. Then user can configure CAN parameters in Manual CAN Settings tab.

NOTE! Manual J1939 can be tested on FW 55.00.09.rev.08 or newer

To read data with this functionality, the user must have:

  • TFT100 device with CAN interface;
  • 55.00.09.Rev.08 or newer firmware;
  • Machinery with CAN interface, which communicates via J1939 protocol;
  • Machinery's J1939 protocol documentation (with required SPN's and PGN's).

J1939 Settings


J1939 Settings.png

Some J1939 PGN’s are not sent periodically, so they must be requested. In order to request PGN device must be registered to J1939 network. To register the device user should configure J1939 Source Address and J1939 Name parameters:

  • J1939 Source Address parameter is used to set TFT source address on J1939 network. If device with selected source address already exists on network, user should change it to another address which might be free, or PGN’s which must be requested will not be received.
  • J1939 Name parameter is used to set TFT name on J1939 network.

Manual J1939 I/O


Up to 29 I/O parameters (Priority, Event Only, Operand, Send SMS To, SMS text) for Manual J1939 functionality can be configured in CAN I/O tab the same way as for Manual CAN functionality.

NOTE! It is important to not forget that Manual CAN Settings tab must be configured as well.

Manual J1939 29 IO.gif