I’m working on a OpenEMS module for a hardware device that will manage a range of different lithium ion batteries. To do so, I’ve (re)written a generic comms bridge for our proprietary protocol, MC-Comms (io.openems.edge.bridge.mccomms in feature/mccomms-bridge). This bridge module is similar to the existing Modbus bridge module in that it provides an abstract component class (api/AbstractMCCommsComponent) for devices using MC-Comms protocol . The bridge seems to be working fine as far as I can tell, but when trying to implement a device using the abstract component class in io.openemes.edge.battery.microcare.ubmu (also in feature/mccomms-bridge), I cannot get the device to activate, and all hardcoded debug log points are never hit.
Steps to reproduce:
1.Start edge application
2.Activate alphabetical scheduler
3.Activate ‘Bridge MC-Comms’ with a valid serial port
4.Activate ‘BMS Microcare UBMU’
5.Console does not produce debug info, and osgiValidateWorker produces non-activation warnings (OpenemsComponent is implemented in io.openemes.edge.battery.microcare.ubmu)
Can anyone please shed light on why this is perhaps happening? TIA