开云体育

I suffer so you don't have to...:(

So I've just lost the better part of a day *Learning* about crap that wasn't designed right (IMHO!)

?

1. Shade Power supplies - Ethernet master with 1-n Cresnet slave PSs

With the SMW device definition, the Master CNET subSlot offers CNET IDs from 03-4F. These are for shades on downstream CNET slave PSs. Of course they couldn't just nest them under these power supplies, but that's another subject...? The fact is that IDs 40-4F are not usable even though they are available in SMW...

How would you know this???? Just read the firmware release notes from 2017 (4 versions back from the current FW, dated 2018)...

?

2. For the first time, I looked seriously at the 'Shade Group' feature. each shade has the ability to be associated with (6) group IDs (00h-FCh). You can set one analog and all the associated shades go to that level...Pretty Cool...or so I thought...

Each Ethernet Power Supply has two subSlots, Master CNET for downstream devices and Local CNET for the devices controlled and powered directly on the (10) local phoenix connectors.?

Problem is that the shade groups only seem to be able to control the shades on the same slot. I.e. One shade group with a 01h can only control shades on the slot that the Shade Group module is associated with.? Its essentially useless...again IMHO...

?

Love to hear that someone found this to be better than I'm finding...But just wanted others to know...

I too was disappointed to discover that shade groups don’t work across different PSUs. You really have to ensure that any group you want to be properly synchronised (e.g. a row of same drop height shades) are all on the same PSU. The fact that these 10-way PSUs are already massively expensive (imo) per output is compounded when you a forced to not use one or two outputs in order to get all your shade groups lumped in to their own PSU.

Even worse...

A shade group on the Local CNET subslot cannot control shades on the Master CNET subslot and Vice versa...

I'll just do my own logic as usual...

I would strongly recommend to still use the shade group function for groups of shades in a line, otherwise you really do notice the “ripple” as they all start/stop in turn, since unless you never want to control individual shades in a group independently, then they’ll always be getting their control from something like the output of a group button presser, which just seems to ripple it’s outputs in sequence.

Just started landing wires on 3 HUBS - read this at the RIGHT time.

?

Thank you...