cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
sunny_li
Contributor
  • 1
  • 98
  • 0
Registered since

Jun 26, 2011

CC-16 can't control ESP880 after power-recycling

Hi all,

Recently we've had some problems with ESP880 and CC-16.

Several ESP880 cannot be controlled by CC-16 after power recycling(ESP880). But if we reload the configuration, the CC-16 worked well again (but after power recycling, no control again).
We tried the same CC-16 with a different ESP880,no problem. So we think it's not the bug of CC-16.

We've encountered this problem with 5 or 6 ESP880/1240.

The version of CSD is the latest 4.3.1. And the firmware of both ESP880 and CC-16 is the latest.

According to the Customer Service department, this may be a problem of the motherboard of ESP880.

Has anyone ever heard this problem?

Thank you!
5 REPLIES 5
sunny_li
Contributor
  • 1
  • 98
  • 0
Registered since

Jun 26, 2011

Re: CC-16 can't control ESP880 after power-recycling

And by the way, there is no 'Comm Error'on CC-16's screen. And the volume displays 99.
Marcin-at-Bose
Member
  • 0
  • 12
  • 0
Registered since

Nov 20, 2008

Re: CC-16 can't control ESP880 after power-recycling

Hello Sunny,

Please check if ESP is set to fixed IP adress - we've had similiar problem, when ESP was in DHCP mode.

Best regards,
Marcin
sunny_li
Contributor
  • 1
  • 98
  • 0
Registered since

Jun 26, 2011

Re: CC-16 can't control ESP880 after power-recycling

Hi Marcin,

Thanks for your reply. Yes, the ESP is set to fixed IP (192.168.0.X)...
Trevor-at-Bose
Collaborator
  • 5
  • 55
  • 0
Registered since

Mar 19, 2014

Re: CC-16 can't control ESP880 after power-recycling

Engineering is currently looking into this. I will let you know as soon as I have an update.

I apologize for the inconvenience.

Best Regards,

Trevor
sunny_li
Contributor
  • 1
  • 98
  • 0
Registered since

Jun 26, 2011

Re: CC-16 can't control ESP880 after power-recycling

Hi all,

First I want to apologize for the inconvenience.

We recognized that when we encountered this problem (which is late July), the latest firmware was V4.3, so we said that the firmware of ESP880 was the latest.

When I posted the problem on the forum, I still thought the firmware version was the latest (V4.3.1).

But when we tested again, we updated the firmware of all defective ESP880 V4.3.1, the problem was gone.

So I believe it’s really a firmware problem…

Thank you all for your attention.