Orbcomm SkyWave IDP-782 Configuration

Nikolay 2 years ago

Hello,

I have an Orbcomm IDP-782 and I'm trying to configure traccar to pull the data from the Skywave gateway, but no success so far.

This is the configuration I am trying:

    <entry key='protocols.enable'>orbcomm</entry>
    <entry key='orbcomm.address'>https://isatdatapro.skywave.com</entry>
    <entry key='orbcomm.interval'>120</entry>
    <entry key='orbcomm.accessId'>integers</entry>
    <entry key='orbcomm.password'>string</entry>

Unfortunately I don't see any attempt to make a request to the API

https://isatdatapro.skywave.com/GLGW/2/RestMessages.svc/JSON/get_return_messages/

Anton Tananaev2 years ago

Have you checked the logs?

Nikolay 2 years ago

I don't find anything in tracker-server.log

    <entry key='logger.level'>info</entry>
2022-11-22 09:32:38  INFO: Operating system name: Linux version: 4.15.0-197-generic architecture: amd64
2022-11-22 09:32:38  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Eclipse Adoptium version: 11.0.17+8
2022-11-22 09:32:38  INFO: Memory limit heap: 7960mb non-heap: 0mb
2022-11-22 09:32:38  INFO: Character encoding: UTF8 charset: UTF-8
2022-11-22 09:32:38  INFO: Version: 5.4
2022-11-22 09:32:38  INFO: Starting server...
2022-11-22 09:32:38  INFO: HikariPool-1 - Starting...
2022-11-22 09:32:38  INFO: HikariPool-1 - Added connection org.postgresql.jdbc.PgConnection@cd7f1ae
2022-11-22 09:32:38  INFO: HikariPool-1 - Start completed.
2022-11-22 09:32:39  INFO: Set default schema name to public
2022-11-22 09:32:39  INFO: Clearing database change log checksums
2022-11-22 09:32:39  INFO: Successfully acquired change log lock
2022-11-22 09:32:39  INFO: Successfully released change log lock
2022-11-22 09:32:39  INFO: Successfully acquired change log lock
2022-11-22 09:32:40  INFO: Reading from public.databasechangelog
2022-11-22 09:32:41  INFO: Reading from public.databasechangelog
2022-11-22 09:32:41  INFO: Successfully released change log lock
2022-11-22 09:32:41  INFO: Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system instability.
2022-11-22 09:32:42  INFO: jetty-10.0.12; built: 2022-09-14T01:54:40.076Z; git: 408d0139887e27a57b54ed52e2d92a36731a7e88; jvm 11.0.17+8
2022-11-22 09:32:42  INFO: Started o.t.w.@6c8efde4{/,null,AVAILABLE}
2022-11-22 09:32:42  INFO: Session workerName=node0
2022-11-22 09:32:42  WARN: JAXBContext implementation could not be found. WADL feature is disabled.
2022-11-22 09:32:43  INFO: Started o.e.j.s.ServletContextHandler@77998ea7{/,null,AVAILABLE}
2022-11-22 09:32:43  INFO: Started ServerConnector@2aa14ae6{HTTP/1.1, (http/1.1)}{0.0.0.0:8088}
2022-11-22 09:32:43  INFO: Started Server@3e03046d{STARTING}[10.0.12,sto=0] @5987ms
2022-11-22 09:32:43  INFO: Health check enabled with period 480000
2022-11-22 10:16:56  INFO: user: 3, action: login, from: 127.0.0.1
2022-11-22 10:23:17  INFO: user: 3, report: route, from: 2022-11-22 09:21, to: 2022-11-22 10:21, devices: [29], groups: [2]
2022-11-22 10:25:10  INFO: user: 3, report: route, from: 2022-11-22 09:21, to: 2022-11-22 10:21, devices: [29], groups: [2]
2022-11-22 10:25:10  INFO: you may change the SPI on file: META-INF/services/org.jxls.util.ServiceFactory
2022-11-22 10:25:10  INFO: you may change the SPI on file: META-INF/services/org.jxls.util.JxlsConfigProvider
2022-11-22 10:25:10  INFO: you may change the SPI on file: META-INF/services/org.jxls.expression.ExpressionEvaluatorFactory
2022-11-22 10:25:52  INFO: user: 3, report: route, from: 2022-11-22 09:21, to: 2022-11-22 10:21, devices: [29], groups: [2]
2022-11-22 10:26:08  INFO: user: 3, report: route, from: 2022-11-22 09:21, to: 2022-11-22 10:21, devices: [29], groups: []
2022-11-22 10:26:35  INFO: user: 3, report: route, from: 2022-11-21 09:21, to: 2022-11-20 10:21, devices: [29], groups: []
2022-11-22 10:26:51  INFO: user: 3, report: route, from: 2022-11-20 09:21, to: 2022-11-21 10:21, devices: [29], groups: []
2022-11-22 10:27:12  INFO: user: 3, report: route, from: 2022-11-18 09:21, to: 2022-11-19 10:21, devices: [29], groups: []
2022-11-22 10:27:54  INFO: user: 3, report: route, from: 2022-11-17 09:21, to: 2022-11-19 10:21, devices: [29], groups: []
2022-11-22 11:06:05  INFO: user: 3, action: edit, object: user, id: 3
2022-11-22 11:12:10  INFO: user: 3, action: link, owner: device, id: 19, property: notification, id: 8
2022-11-22 11:12:12  INFO: user: 3, action: link, owner: device, id: 19, property: notification, id: 9
2022-11-22 11:12:14  INFO: user: 3, action: link, owner: device, id: 19, property: notification, id: 10
2022-11-22 11:12:17  INFO: user: 3, action: link, owner: device, id: 19, property: notification, id: 7
2022-11-22 11:12:20  INFO: user: 3, action: edit, object: device, id: 19
2022-11-22 11:12:29  INFO: user: 3, action: link, owner: device, id: 29, property: notification, id: 8
2022-11-22 11:12:31  INFO: user: 3, action: link, owner: device, id: 29, property: notification, id: 9
2022-11-22 11:12:33  INFO: user: 3, action: link, owner: device, id: 29, property: notification, id: 10
2022-11-22 11:12:34  INFO: user: 3, action: link, owner: device, id: 29, property: notification, id: 7
2022-11-22 11:14:45  INFO: user: 3, action: edit, object: device, id: 29

I tried with finest logger.level but found nothing

Anton Tananaev2 years ago

Where did you get your configuration from? The config should look something like this:

    <entry key='orbcomm.address'>isatdatapro.orbcomm.com</entry>
    <entry key='orbcomm.port'>443</entry>
    <entry key='orbcomm.ssl'>true</entry>
    <entry key='orbcomm.interval'>20</entry>
    <entry key='orbcomm.devices'>123,456</entry>
    <entry key='orbcomm.accessId'>accessId</entry>
    <entry key='orbcomm.password'>password</entry>
Nikolay 2 years ago

Super, it works.

For the configuration I improvised from here

In Orbcomm there is a message definition functionality. I guess it's not implemented in the protocol?

Anton Tananaev2 years ago

What is a message definition functionality? I'm assuming not supported.

Nikolay 2 years ago

The message definition files are used by the system and various tools such as the Traffic Viewer to know how to decode message payloads.

Example:

Count Terminal Received Interface SIN MIN Message Name Latitude Longitude Speed Heading EventTime GpsFixAge Odometer DigitalPorts AvlStates hardwareVariant hardwareRevision hardwareResetReason firmwareMajor firmwareMinor firmwarePatch LSFVersion softwareResetReason sinList packageVersion hardwareMajorVersion hardwareMinorVersion softwareMajorVersion softwareMinorVersion product wakeupPeriod lastResetReason virtualCarrier beam vain reserved operatorTxState userTxState broadcastIDCount
88 --- 2022-11-23 03:30:56 Satellite 16 8 terminalRegistration ##.### ##.### IDP-782 2 PowerOn 1 5 7 "9.4.8" None 16 17 18 19 20 21 22 23 24 25 26 27 29 32 33 34 127 199 237 238 239 "5.4.5.20273"
87 --- 2022-11-23 03:30:35 Satellite 0 0 modemRegistration ##.### ##.### 5 0 14 6 4 None PowerOn 201 3 0 0 0 0 0
86 --- 2022-11-23 03:28:23 MTBP 237 48 StationaryIntervalCell ##.### ##.### 0 361 1669174098 0 0 12345
85 --- 2022-11-23 03:27:39 MTBP 237 6 MovingStart ##.### ##.### 3 234 1669174024 0 0 12349
84 --- 2022-11-23 03:25:37 MTBP 237 48 StationaryIntervalCell ##.### ##.### 0 361 1669173932 0 0 4157
83 --- 2022-11-23 03:19:02 Satellite 237 198 TagDetected ##.### ##.### 0 361 1669173525 0 0 12349 0
82 --- 2022-11-23 03:18:57 Satellite 237 199 TagRemoved ##.### ##.### 0 361 1669173523 0 0 4157 0

This is for SIN 237, which is associated with the position. When registering, the terminal passes all the sins it reports

Anton Tananaev2 years ago

I don't think it's supported at the moment.