I am having trouble finding any information on how to specifically connect the ekrano GX to my Curtis controllers. Any information or links to Victron documentation would be greatly appreciated.
There is plenty of info on every other Can bus connection however I am stumped with this scenario.
It is a new feature of the firmware for a catamaran boat and it’s an exciting concept and will solve a few things for me as monitoring 2 Curtis controllers has been problematic in the past for my boat.
These motor controllers should be connected to one of the can bus ports.
Both controllers will need to be connected to the same port, so different ID’s will need to be programmed into the controllers - unless they self allocate an id.
I’m also waiting for more developments in this line, but have been looking at motor controllers for a few years now.
Are you expecting to get any regeneration from these units?
Thanks for your response. Your advice is valuable to me and I will start with allocating an ID regardless of what features the screen may have.
The controllers are in an electric catamaran (no sails) and regeneration is not a thing on my boat. Even in a 4 or 5 knot current at anchor the props don’t turn even without magnetic load.
Thanks again and I will forge forward with bits of info as I receive them.
It gives most of an explanation however there is still a bit of connecting the dots with respect to the requirements of the Curtis. More detail is given about the Sevcon for example.
First thing to do is to identify whether you have a Curtis F or E/SE series controller.
The second step will be to prepare a modified cable to connect the Curtis controller to the GX device VE.Can port.
The pinout differs between the different Curtis controllers, the details can be found on the github link above.
In your case, connecting multiple controllers, one of the requirement is that they must each have a different node ID.
I would recommend first connecting to a single controller, scanning the bus following the guide mentioned above and writing down the node ID detected (it will be visible in the UI).
Then repeat that process with just the second controller connected. If the node ID detected after the scan is the same as your first controller then you will have to reprogram one of them to use a different node ID.
Please report back if you are having any issues with the process.
I will update this thread once the manuals have been updated.