4.0.6 boot time?

  • Went from about 1 min on v3.3 to 77sec on v4.06
    remote adds an extra 25secs on top of that.


    it appears the remote has a timeout if not connected within x-seconds. The remote appears to get power earlier on in the boot cycle than previously but turns off after about 60sec then repowers when boot is near to complete adding 25 secs. I did connect the remote after 40-50 secs of boot and it stayed powered as it continued to search for a connection without going off and increased the start time by several seconds. Anyone else confirm this?

  • A kemper remote will start much faster when it is being connected to a running profiler, than the time it adds to the boot-process when connected from power-on. The method used to establish a connection between the remote and the profiler seems anything but efficient. After initialisation the remote has nothing else to do than to try to establish a connection to the profiler. Why not have it retry often with a short (<1sec) timeout. It shouldn't take more than a sec maximum from the profiler has booted till the remote is ready for use, except from the few cases where the profilers firmware include upgraded firmware for the remote that require download and reboot before it is activated.