Данные с CAN шины

Andrey2 years ago

Объясните, мне, пожалуйста, бестолковому.

  1. В настройках default.xml добавил <entry key='navtelecom.can'>true</entry>, перезапустил сервер.
  2. Посылаю тестовый пакет с данными CAN шины
05:43:50:173 отправлено: 152 байт
 7e 41 01 00 00 00 00 00 10 e6 1a 36 64 00 00 63
 00 e6 1a 36 64 30 c4 55 01 f0 a8 fb 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f4 81 00 00 96 43 ff ff 80 00 40 1c 46 ff ff ff ff ff ff ff ff ff ff ff ff ff c8 80 00 00 00 00 ff ff 37 00 00 00 00 00 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06

~A  Size = 1
numPage = 0  Code = 4096  Time = 1681267430  State = 0  Module1 = 0  GSM = 99  StateGauge = 0  LastTime = 1681267430  Lat = 22398000  Lon = 33270000  Speed = 0  Course = 0  Mileage = 0  Power = 0  Reserv = 0  StateIn1 = 0  Motochas = 0  LevelRS485_1 = 0  LevelRS485_2 = 0  LevelRS232 = 0  CAN_FuelLevel = 33268  CAN_FuelConsumption = 300  CAN_EngineTurns = 65535  CAN_Temp = -128  CAN_FullRun = 10000  CAN_AxleLoad_1 = 65535  CAN_AxleLoad_2 = 65535  CAN_AxleLoad_3 = 65535  CAN_AxleLoad_4 = 65535  CAN_AxleLoad_5 = 65535  CAN_PedalAccel = 255  CAN_PedalStop = 255  CAN_EngineLoad = 255  CAN_LevelFiltr = 32968  CAN_EngineTime = 0  CAN_TimeTO = -1  CAN_Speed = 55  TempRS485_1 = 0  TempRS485_2 = 0  TahoState = 0  TahoMode = 0  TahoFlags = 0  DispCur = 0  AccelLinearX = 0  AccelLinearY = 0  AccelLinearZ = 0  Passager_1 = 255  Passager_2 = 255  HPrecisionTemp1 = 0  FfsState = 0  FfsError = 0  FfsFuel = 0  FfsFuelTrip = 0  RefrState1 = 0  RefrState2 = 0  RefrTemp1 = 0  CAN3State = 0  CAN3Event = 0  CAN3Crash = 0  CAN3FailureLamp = 0  CAN3FailureCode = 0  User1Byte1 = 0  User2Byte1 = 0  User4Byte1 = 0  User8Byte1 = 0  

05:43:50:300 принято: 4 байт
 7e 41 01 df
 ~A
size = 1  crc8 = 223
  1. В лог файле tracker-server.log есть строки и я понимаю, что все хорошо
2023-04-12 05:47:39  INFO: [T0a9f9056: navtelecom < 78.153.140.145] 404e5443010000000000000013004d462a3e533a313030303030303030303030303031
2023-04-12 05:47:39  INFO: [T0a9f9056: navtelecom > 78.153.140.145] 404e544300000000010000000300455e2a3c53
2023-04-12 05:47:39  INFO: [T0a9f9056: navtelecom < 78.153.140.145] 404e544301000000000000002a00c2f02a3e464c4558b01e1efffbee30080e100ffff80600007124000000000000203c060000f2000200040008
2023-04-12 05:47:39  INFO: [T0a9f9056: navtelecom > 78.153.140.145] 404e544300000000010000000900b1a02a3c464c4558b01e1e
2023-04-12 05:47:42  INFO: [T0a9f9056: navtelecom < 78.153.140.145] 7e4101010000000010ce1b366400006300ce1b366430c45501f0a8fb0100000000000000000000000000000000000000000000000000f48100009643ffff8000401c46ffffffffffffffffffffffffffc88000000000ffff3700000000000000000000000000fff>
2023-04-12 05:47:42  INFO: [T0a9f9056: navtelecom > 78.153.140.145] 7e4101df
2023-04-12 05:47:42  INFO: [T0a9f9056] id: 100000000000001, time: 2023-04-12 05:47:42, lat: 37.33000, lon: 55.45000, course: 0.0
2023-04-12 05:47:43  INFO: [T0a9f9056: navtelecom < 78.153.140.145] 7e4101020000000010cf1b366400006300cf1b366430c45501f0a8fb0100000000000000000000000000000000000000000000000000f48100009643ffff8000401c46ffffffffffffffffffffffffffc88000000000ffff3700000000000000000000000000fff>
2023-04-12 05:47:43  INFO: [T0a9f9056: navtelecom > 78.153.140.145] 7e4101df
2023-04-12 05:47:43  INFO: [T0a9f9056] id: 100000000000001, time: 2023-04-12 05:47:43, lat: 37.33000, lon: 55.45000, course: 0.0
2023-04-12 05:47:44  INFO: [T0a9f9056: navtelecom < 78.153.140.145] 7e4101030000000010d01b366400006300d01b366430c45501f0a8fb0100000000000000000000000000000000000000000000000000f48100009643ffff8000401c46ffffffffffffffffffffffffffc88000000000ffff3700000000000000000000000000fff>
2023-04-12 05:47:44  INFO: [T0a9f9056: navtelecom > 78.153.140.145] 7e4101df
2023-04-12 05:47:44  INFO: [T0a9f9056] id: 100000000000001, time: 2023-04-12 05:47:44, lat: 37.33000, lon: 55.45000, course: 0.0
  1. В базе данных в таблице tc_positions добавляется запись с атрибутами:
{"index":3,"event":4096,"sat":0,"odometer":0.0,"power":0.0,"battery":0.0,"in1":false,"in2":false,"in3":false,"in4":false,"in5":false,"in6":false,"in7":false,"in8":false,"hours":0,"fuel1":0,"fuel2":0,"fuel":0,"fuelTemp1":0,"fuelTemp2":0,"distance":0.0,"totalDistance":0.0,"motion":false}

Что нужно сделать, чтобы данные с CAN появились?

Anton Tananaev2 years ago

There's no navtelecom.can parameter. Where did you find it?

As for the CAN data, I suspect we just don't support some of the parameters currently.

Andrey2 years ago

А как указать этот параметр?

[protocol].can config
Enable CAN decoding for the protocol. Similar to 'extended' configuration, it's not supported for some devices.

Я думал в [protocol] нужно подставить название протокола...

Anton Tananaev2 years ago

Правильно, но для этого протокола этот параметр не применим.

Andrey2 years ago

Спасибо

Igor 2 years ago

Добрый день! А есть в планах поддержка CAN у navtelecom?

Anton Tananaev2 years ago

Конкретных планов нету, но если кто-то проспонсирует то можем добавить.

Igor 2 years ago

Добрый день!
Pull requests #4839 "add 53-69 fields for Navtelecom protocol" как раз добавляет CAN поля. Что то с ним не так?

PS Я для "домашнего" использования, понять АЗС где систематически и с какого объема недоливают... На спонсора не потяну, увы. (

Anton Tananaev2 years ago

Ну там комментарии есть поясняющие что не так.