Page 1 of 1

Problem with Aggregate Agent

PostPosted: Fri Jan 27, 2017 9:25 am
by ivan_karadenizov/frodexim_com
Hi all,

There is a problem with communication between Aggregate Server and Agent devices.

During server operation, ID of communication request/respond is increasing. In Aggregate Library (aggregate.tbs line 74) the id have size 8. When id reach 99999999, it does not roll over to 0, but increase to 100000000, the server "hangs" and all devices become offline, because controllers can't process the request. And then the server must be restarted.

I rebuilded the project with bigger string (10) and it is working fine for now. But the problem is there, just will take more time to occur.

Re: Problem with Aggregate Agent

PostPosted: Wed Feb 08, 2017 5:44 am
by anton_logoyskiy/tibbo_com
Hi Ivan,

Please tell what Tibbo devices are you using?
What version of firmware you used with them?
Also please provide version of AggreGate server and AggreGate API?


Re: Problem with Aggregate Agent

PostPosted: Mon Mar 27, 2017 9:05 am
by ivan_karadenizov/frodexim_com
Hi Anton,

Sorry for may very late reply.

Devices, that we use are based on EM1000 with firmware 3.60.
Tibbo project is developed with TIDE 5.00 and it is based on the Aggregate Library that comes with it.
Aggregate server is version 5.31.04.

As I explained in my first post, the problem is, that the server increments id of the message even if the number is bigger than 8 symbols. The id in response from controller is truncated to 8 symbols (as defined in the library).

The error in server log is:
WARN ag.commands.agent Reply cannot be matched to a sent command: R/10000000/A/<R=<0>>, commands in progress: [ReplyMonitor [command: M/100000000/O/G//RI02, reply: null]] - [AsyncCommandProcessor/Agent: (Agent)/Thread-57] (

In bold is different id in command and reply.