2 Replies Latest reply on Jan 13, 2018 11:49 AM by qzhang RSS
    qzhang Newbie

    Duty cycle modulation design/mechanics?

    We have been looking at duty cycle modulation (available in Edge SDKs) as a way to conserve resources (energy/power/battery life, bandwidth, etc.) on an edge device. However, it seems that the way the off-period of the duty cycle is implemented is to simply disconnect the communication endpoint from the server, and reconnect at the start of a new duty cycle (at least in the Java Edge SDK).


    Is this design intended? We would like if during the off-period, the client would still be able to receive some sort of keep-alive/force-connect message from the ThingWorx platform. I know that the client is able to initiate such connections by setting forceConnect to true when calling invokeService, but is there a similar mechanism available for the platform?