specifically so I can see any follow ups to @ptrenz comment:
“due to the high demand, we are right now working on adding support for the DSE 4520 MKII. As this specific model does not support starting and stopping via Modbus, it will use one of the GX relays for the start/stop signal. Therefore, it will require some additional wiring in contrast to the other DSE models. I will keep you informed.”
Hi @glenborrodaleit, thanks! I’m happy to let you know, that development work is almost completed and this feature will be available for beta testing soon.
Here is a preview of how it will work:
The DSE 4520 MKII will get available in the device list as soon as it was found via Settings > Modbus TCP/UDP devices, as with all other connected genset controllers. As it does not allow start/stop commands via Modbus, you will be prompted to enable a new relay function for Relay 1: Connected genset helper relay. After wiring the GX Relay 1 to the genset controller, the generator can thereby be started and stopped.
Hi @arboldoly, not yet in a stable release. But since the beta release of v3.60~21, we support basically all DSE controllers except for the DSE8xxx range. With the upcoming release of v3.60, it will then be officially supported. Feel free to give it a try!
Hi @ptrenz ,
When will 3.60 be officially released, this version works with the dse6110 MKIII.
I want to make it work in a system with 4 MG(304ah) LFP batteries with a Master lv distributor on 3 Quattro’s for a small passenger boat. But I don’t know if the beta version is stable enough.
Hi @Remy, welcome at the community forum! Unfortunately, we do not specify future release dates here, sorry. Also see our community guidelines on that.
Just picking up the conversation from this thread regarding integration with deep sea electronics controllers specifically the DSE 4520 MKII.
@ptrenz mentioned that due to high demand, support for this model is in the works. Since it doesn’t support start/stop over Modbus, it’ll use one of the GX relays instead, which means a bit of extra wiring compared to other DSE units.
Appreciate the update — just following along here to stay in the loop on any progress or wiring/setup details as they become available. Would love to hear from anyone already trying this out.
Hi @chris211, support for DSE 4520 MKII was added with v3.50. To start and stop the generator, you wire it as it would use the Relay-controlled start/stop feature, but then select “Connected genset helper relay”. This will then be closed as long as the generator should run and open otherwise. Happy integrating!
How do I wire my DSE 4520 MKII to the Cerbo? Can I use the CAN port on the DSE that is meant for motor comunication? Or do I NEED a DSE855 USB to Ethernet communication device and connect it through Ethernet? Or can I connect it via USB?
The controller’s CAN bus for motor communication is not an option.
Skimming through previous posts and my memory I would say you would indeed need to connect the controller and the Cerbo together via the DSE855 USB to Ethernet converter.
More info here: 18. GX - Generator auto start/stop
OK. The DSE855 is my next option if I can’t get it to work otherwise.
When I’m reading the manual for the 4520 MKII I get the impression that it should be able to connect to other CAN-devices but maybe I’m just interpreting it wrong.
On page 20:
CAN Port
Engine CAN Port
Standard implementation of ‘Slow mode’, up to 250 kb/s
Non-Isolated.
Internal Termination provided (120 )
Max distance 40 m (133 feet)
Page 22:
The modules are fitted with a CAN interface as standard and are capable
of receiving engine data from engine ECU/ECMs compliant with the CAN
J1939 standard.
ECU/ECMs monitor the engine’s operating parameters such as speed,
oil pressure, coolant temperature (among others) to closely monitor and control the engine. The industry standard communications interface (CAN) transports data gathered by the engine’s ECU/ECM using the J1939 protocol. This allows engine controllers such as DSE to access these engine parameters with no physical connection to the sensor device.
The ECU Port is used for point-to-point cable connection of more than one device and allows for connection to CAN Scanner, PLC, and CAN controllers (to name just a few devices). The operator is then able to view the various operating parameters.
Page 23:
When the J1939-75 is enabled in the module’s configuration, the module’s AC measurements and alarms are sent onto the CANbus using the ECU Port to be received by an external monitoring device.
There are two check boxes to enable each of the two parts of the interface as shown below, AC
measurement and AC related alarms. The module AC alarms are translated into J1939 DM1
diagnostic messages. There are no additional display screens visible on the module when these options are selected. The default CAN source address for additional J1939-75 messages is 44 however this may be changed by the generator supplier.
Especially the part on page 22 that says “for connection to CAN Scanner, PLC, and CAN controllers (to name just a few devices)” and the part on page 23 “…module’s AC measurements and alarms are sent onto the CANbus using the ECU Port to be received by an external monitoring device” implies that the data on the CANbus should be able to be distributed to other devices than the engine ECU. Is this not correct?
I know that I can’t start and stop the 4520 MKII via MODBUS and that I need to use relays for that, but I would like to receive genset data into the Cerbo GX. But if you tell me it doesn’t work I guess I have to take your word for it. I will first try MODBUS RTU with an RS485→USB converter I have at hand and if that doesn’t work I might try the DSE855.
Call me thick headed. Or call me curious. But I can’t really let go why this shouldn’t work.
The physical layer should be the same. CAN. And both units “speak” J1939. But the DSE controller says J1939-75 and from what I can gather the -75 is the “application layer”. I this the “vocabulary” you’re mentioning?
If so, would it not be possible to teach the Cerbo this vocabulary? The only hindering to making it work is software implementation in the Cerbo?
Yes, the physical layer should be able to support it and it’s “only” a matter of software. If you’re adventurous enough, please feel free to give it a try – the GX device is an open platform. However, as there is already a working solution, you will be on your own on that journey.
Unfortunately I don’t have the time to get into the weeds of modifying the software so I will definitely try to make it work with some kind of bus adapter. I just wanted to know why it didn’t work.
I chose the specific model of DSE controller based on what I read in the specs (and on price) but in hindsight I should have gone for another controller with ethernet or MODBUS. But now the controller is in place and mostly interfaced with the genset so I’m too pot committed to switch…
And now I realize that I also need a controller for my main engine and I might as well go for a DSE there aswell.
DSE4520 mkII + DSE855 for the genset and DSEE100 + DSE855 for the main engine seems reasonable. That way I have the same ecosystem for both engines and I can add other MODBUS TCP units at will.
Any hope of getting support for the DSEE100 in the Cerbo GX?
Is it possible for me to contribute and add support myself through making config files or something?
