| Posted: Thursday Jan 12th, 2017 06:19 pm |
|
21st Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
Well done, Ingo, the Cbus2 firmware update has fixed it! I would have tried that before but I thought my system was up to date as that was what Comfigurator was telling me.
Anyway, at least that's established there's an incompatibility between Eth03 v2.22 and cbus2 v7.054
|
| Posted: Thursday Jan 12th, 2017 06:19 pm |
|
22nd Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
Right clicking on Cbus UCM and selecting :Check for Firmware upgrades" should work, as well as downloading the firmware upgrade and upgrading from local file
|
| Posted: Thursday Jan 12th, 2017 06:22 pm |
|
23rd Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
Just as Ingo suggested, Comfigurator says Cbus2 v7.054 is the latest if you ask it to check. Even after downloading v7.068 myself and installing it, it still insists v7.054 is the latest!
|
| Posted: Friday Jan 13th, 2017 05:58 am |
|
24th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
Oh, I see the problem. Cbus 7.068was not officially released yet even though it has been beta for more than a year
The firmware on the server is updated now, so it will allow direct upgrade without download
Apologies
|
| Posted: Friday Jan 13th, 2017 06:01 am |
|
25th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
However 7.054 did not list the updating of date to cbus as a bug, and 7.068 did not change anything in regard to that. Needs further invetigation
|
| Posted: Friday Jan 13th, 2017 03:05 pm |
|
26th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
7.054 wouldn't have listed the updating of the cbus date as a bug because it worked perfectly well until V2.22
|
| Posted: Friday Jan 13th, 2017 03:05 pm |
|
27th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
7.054 wouldn't have listed the updating of the cbus date as a bug because it worked perfectly well until V2.22
|
| Posted: Friday Jan 13th, 2017 03:05 pm |
|
28th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
7.054 wouldn't have listed the updating of the cbus date as a bug because it worked perfectly well until V2.22
|
| Current time is 05:20 am | Page:   1 2 |
|
