Tago Downlink issue - Payload changed

1

Hi, Looking for anyone who can help on what seems to be a silly issue, but I am stuck.

I am using TagoIO connected to TTI private network to control a Milesight UC1114 Remote IO device.

When sending downlink commands, I can message from TTI without issue. eg 090100ff closes one of the relay switches.

When I try and do the same thing from Tago to TTI, the json message seems ok (I get “frm_payload”: “090100ff”,) however the actual downlink payload is “D3DD35D347DF” which obviously is ignored by device.

Can anyone point me in the right directions to fix this?

Regards
Dayne

{
“name”: “as.down.data.forward”,
“time”: “2021-04-05T15:04:37.043648943Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “insideuc1114”,
“application_ids”: {
“application_id”: “canso-test”
}
}
}
],
“data”: {
“@type”: “type.googleapis.com/ttn.lorawan.v3.ApplicationDownlink”,
“f_port”: 1,
“frm_payload”: “090100ff”,
“priority”: “NORMAL”,
“correlation_ids”: [
“as:downlink:xxxxxxx”
]
},
“correlation_ids”: [
“as:downlink:xxxxxxxxx”
],
“origin”: “ip-10-22-7-252.us-west-1.compute.internal”,
“context”: {
“tenant-id”: “xxxxxx”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“authentication”: {
“type”: “Bearer”,
“token_type”: “APIKey”,
“token_id”: “xxxxx”
},
“remote_ip”: “100.25.118.118”,
“user_agent”: “axios/0.20.0”,
“unique_id”: “xxxxxxxx”
}

  • rrow_downward

09:04:37

Successfully scheduled data downlink for transmission on Gateway Server

DevAddr

2609D304

  • arrow_downward

09:04:37

Schedule data downlink for transmission on Gateway Server

DevAddr

2609D304

FPort

1

MAC payload

ABC5DB393B86

  • arrow_downward

09:04:37

Forward downlink data message

FPort

1

Payload

D3DD35D347DF

  • arrow_downward

09:04:37

Receive downlink data message

FPort

1

Payload

D3DD35D347DF

2

Would you consider formatting your message for readability?

3

Hi,

Yes, for sure,

I have separated items to make clearer, but suspect you are referring to different formatting. Can you advise what you are looking for in terms of formatting?

Thanks
Dayne

I am using TagoIO connected to TTI private network to control a Milesight UC1114 Remote IO device.

When sending downlink commands, I can message from TTI without issue. eg 090100ff closes one of the relay switches.

When I try and do the same thing from Tago to TTI, the json message seems ok (I get “frm_payload”: “090100ff”,) however the actual downlink payload is “D3DD35D347DF” which obviously is ignored by device.

Can anyone point me in the right directions to fix this?

Regards
Dayne

Json received by TTI
{
“name”: “as.down.data.forward”,
“time”: “2021-04-05T15:04:37.043648943Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “insideuc1114”,
“application_ids”: {
“application_id”: “canso-test”
}
}
}
],
“data”: {
“@type”: “type.googleapis.com/ttn.lorawan.v3.ApplicationDownlink”,
“f_port”: 1,
“frm_payload”: “090100ff”,
“priority”: “NORMAL”,
“correlation_ids”: [
“as:downlink:xxxxxxx”
]
},
“correlation_ids”: [
“as:downlink:xxxxxxxxx”
],
“origin”: “ip-10-22-7-252.us-west-1.compute.internal”,
“context”: {
“tenant-id”: “xxxxxx”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“authentication”: {
“type”: “Bearer”,
“token_type”: “APIKey”,
“token_id”: “xxxxx”
},
“remote_ip”: “100.25.118.118”,
“user_agent”: “axios/0.20.0”,
“unique_id”: “xxxxxxxx”
}

Downlink message from TTI data browser

  • rrow_downward

09:04:37

Successfully scheduled data downlink for transmission on Gateway Server

DevAddr

2609D304

  • arrow_downward

09:04:37

Schedule data downlink for transmission on Gateway Server

DevAddr

2609D304

FPort

1

MAC payload

ABC5DB393B86

  • arrow_downward

09:04:37

Forward downlink data message

FPort

1

Payload

D3DD35D347DF

  • arrow_downward

09:04:37

Receive downlink data message

FPort

1

Payload

D3DD35D347DF

4

Did you even attempt to read message I linked to?

5

No, I was reading off my phone and didn’t see, I will have a look. Sorry about that.

btw, the rudeness I see in replies including this one is putting a lot of people off this board.

6

Would you care to explain? You get a polite request to format your post for readability, repost essentially the same message and are surprised when you get a terse reply?

Please when making statements regarding a lot of people either substantiate or refrain from making that claim. If you consider a reply rude, which does happen more often in electronic communication, just say so. Don’t involve vague third parties.

7

Here is my attempt at formatting. Not sure it meets the standards.

I am using TagoIO connected to TTI private network to control a Milesight UC1114 Remote IO device.

When sending downlink commands, I can message from TTI without issue. eg 090100ff closes one of the relay switches.

When I try and do the same thing from Tago to TTI, the json message seems ok (I get “frm_payload”: “090100ff”,) however the actual downlink payload is “D3DD35D347DF” which obviously is ignored by device.

Can anyone point me in the right directions to fix this?

Regards
Dayne

Json received by TTI

{
“name”: “as.down.data.forward”,
“time”: “2021-04-05T15:04:37.043648943Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “insideuc1114”,
“application_ids”: {
“application_id”: “canso-test”
}
}
}
],
“data”: {
“@type”: “[type.googleapis.com/ttn.lorawan.v3.ApplicationDownlink](http://type.googleapis.com/ttn.lorawan.v3.ApplicationDownlink)”,
“f_port”: 1,
“frm_payload”: “090100ff”,
“priority”: “NORMAL”,
“correlation_ids”: [
“as:downlink:xxxxxxx”
]
},
“correlation_ids”: [
“as:downlink:xxxxxxxxx”
],
“origin”: “ip-10-22-7-252.us-west-1.compute.internal”,
“context”: {
“tenant-id”: “xxxxxx”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“authentication”: {
“type”: “Bearer”,
“token_type”: “APIKey”,
“token_id”: “xxxxx”
},
“remote_ip”: “100.25.118.118”,
“user_agent”: “axios/0.20.0”,
“unique_id”: “xxxxxxxx”
}

Downlink message from TTI data browser

  • List item

09:04:37:Successfully scheduled data downlink for transmission on Gateway Server:DevAddr:2609D304

  • List item

09:04:37:Schedule data downlink for transmission on Gateway Server:DevAddr:2609D304:FPort:1:MAC payload:ABC5DB393B86

  • List item

09:04:37:Forward downlink data message:FPort:1:Payload:D3DD35D347DF