I think you are the first one to talk of the hex refresh.
To recap:
- OP had a hex S that was PoE powered and powered in cascade.a cap AX
- then he replaced the hex S with a L009, but the L009 could not power the (same) cap AX
- the hex S and the L009 have the SAME specs regarding PoE in and out (with a slight difference with amount of current in output, which is irrelevant since the cap AX needs half the amount of current)
The documentation of both the devices at hand (the hex S and the L009) DOES NOT state that the PoE in on either device can be either 802.3af/at or passive (this is something that is NOT written on the product page) and BTW the page for the cap AX as well states PoE in as 802.3af/at ONLY:
https://mikrotik.com/product/cap_ax
Powering
Details
Number of DC inputs 2 (PoE-IN, DC jack)
DC jack input Voltage 18-57 V
Max power consumption 36 W
Max power consumption without attachments 11 W
Cooling type Passive
PoE in 802.3af/at
PoE in input Voltage 18-57 V
One needs to infer that since the device accepts 18-57 V PoE in and the 802.3af/at standard (the one that Mikrotik does not fully complies to) has a minimum-minimum voltage of 37 for af or 42.5 for at, then the device can also be powered by passive power, but is not explicitly written anywhere on the page.
Still the basic issue remains, if the same cap AX can be powered (passive) by a hex s and cannot be powered (passive) by a L009, it means that the (passive) PoE out of the hex s is somehow different from the (passive) power of the L009, notwithstanding the fact that they are equally (mis-) described on their respective pages.