Rose Point Navigation Manual

0 views

Skip to first unread message

Quinton Hebenstreit

unread,

Aug 3, 2024, 5:08:38 PM8/3/24

to lesgeschvarto

The manual is built into the program, use the search button to look. you can also hit F1 key to open the manual.
When I hit MOB, it drops the ring and sets it as an active waypoint where the boat is right that moment. Perhaps you need to move the boat off of that spot to see the navigate to waypoint working. If you are at your dock, you can move the boat off the spot by right clicking on the chart somewhere else and click Move boat here, caution that you now be in ded reckoning mode and the program will no longer use your GPS to place your boat on the chart.

There is also a youtube channel with tutorials but I find that it is for beginners to the software. If you have a specific question that you need answered, the RPCE guys are great with phone support, and they actually answer the phone live, and speak english.

The EVO works very well with CE. I have navigated some very narrow passages using a CE route sent to the EVO as an experiment. It navigated the route as well as I could manually steer with one exception. When you get to a waypoint that requires a turn, it will ask you to acknowledge the waypoint coming up and begin the turn early so that at the way point will be on the new heading. If you set the waypoint past where you want to turn, it works fine. I was dealing with a channel that was about 60 feet wide, so when to turn was critical. So if you want to turn at a buoy, set the waypoint a little past the buoy.

I hooked up the VE.Can to NMEA 2000 cable between my Cerbo and my boat's bridged N2K-STNG network - and cross-over devices immediately appeared on both systems - but I'm having trouble configuring them on the Victron side.

And when I look in Devices on the Cerbo, they are there - but I am unable to change the parameters. Fuel (2) above is actually Water - when I try to change the type in the Cerbo UX it doesn't take the change and immediately goes back to the device configuration screen. I am able to change the capacity type to gallons and that persists, but if I try to change the capacity (in this case to 60 gallons) and hit the checkmark...it does NOT persist. I also looked at possibly changing the device IDs of the Cerbo pre-defined tanks but they are read only. This isn't the end of the world but it's bugging me and I'd like to get the configurations correct. How can I change the configuration?

So...reading this now at home...I'm thinking that my UX is "correct" and the Cerbo manual did NOT get updated with the current UX. And that the "Devices" isn't to configure just the devices on that interface, but is a redirection to the Devices submenu on Setup.

Regarding the tanks always being fuel. I suspect that within N2K, they are set as fuel, one of the parameters is tank type. What are other N2K displays showing the tank details as? If they are also showing as fuel, you will need to configure the N2K device transmitting the data to transmit the correct tank type.

@Bathnm Thanks for the quick response! I'm actually not sure what version I'm running! I don't seem to be able to find that in VRM - will definitely head to my boat today and verify. The install was done around Thanksgiving...I'm pretty sure I updated the SmartShunt...but that is exactly the kind of thing that would give this problem.

Regarding the "Fuel" sensors - you can actually see those three "Fluid Level" devices on the Raymarine screen I posted (a little greeked out but it's also in the attachments). I have a Maretron USB100 so I can run N2KAnalyzer and change many config values - I think these are Simrad sensors but I forget.

1) to disable the tank inputs of the Cerbo GX itself (or a Venus GX) go to Settings -> I/O. Thats a menu in Remote Console or on your GX Touch. This will remove them from the Device list on the Victron GX device, and stop those tank values from being transmitted out on N2K network with the NMEA2000-out function.

2) To configure tank type (fuel, water, etc) and capacity for third party sender, like from Navico, Yacht Devices, or anything else, you can not use the user interface Victron GX Device. Even though it may seem you can. Instead, use instructions from third party manufacturer.

3) Only thing you do can (and have to) configure on the Victron GX device for those senders is the unit (gallons, liters, etc). That setting is *not* stored in the sender, instead its stored on the GX device and affects what level is used to show remaining capacity on the Victron UIs.

But that didn't affect my ability to update the Fluid Level inputs for capacity type and capacity - any ideas on that? I am set as "user and installer"...is there some other meta-setting that would allow me to persist these changes? I CAN make those changes on the Cerbo's tanks...which, ironically, I want to hide.

And...now that I've updated the Cerbo - I have perhaps a dozen new N2K inputs on the Raymarine device, including all of the Cerbo's built-in tanks which (again) I'm not using. In the Cerbo's N2K Devices I can only assign the ID - I cannot disable. And in the Cerbo's Devices page for each tank...it says Status=Disconnected but when I look at the Device settings it says Connected=Yes. Can I truly delete / whack / hide the Cerbo's tanks?

No, unless they are connected physically to the Cerbo. But since they are coming from N2K, you have to deal with them. The only way to hide/delete/whack the tanks is via your N2k network. If that's not possible because you can't program them, then there is no other way but to disconnect them physically.

Your screen shots above are slightly different from mine. On the Device you show "Name" (and not "Hardware version" which is probably scrolled). I do not have "Name", but I do have that option on the built-in Fuel tanks. What are your sensors? Mine are Lowrance Navico Fluid Level Sensor [000-11518-001].

I am sorry to bother you, but I am using the YD YDTA-04 and it fails to be configured from the CerboGX UI
Basically, I select the tank that I want to update, input the capacity or fluid type, press OK, but nothing happens :(
I am using CerboGX FW version 3.12

Do you know what would be the maximum wire length to connect the tank sensors to the cerbogx directly? one of the tanks will need around 10m wire if I want to connect to the Cerbo, and I would like to confirm that this will work OK

@Stefanie mentions that YD level sensors are configurable - I see there are two ways to do that, a microSD card on the sensor and by putting some "YD:" config lines in "Installation Description 2", and I think this means that YD sensors are likely not configured when these fields are changed in the Cerbo GX UI. If that's true, then I suggest @mvader (Victron Energy) that these fields be marked in the Cerbo UI as read-only since they will immediately be overwritten by the next received PGN. Or add an option to "override received settings" if you want to add some value.

For my Navico / Lowrance fluid level sensors I suspect there is a parallel N2K-based configuration that Lowrance MFDs can accomplish but I haven't discovered the corresponding protocol. My Raymarine MFDs however allow me to set these parameters - they are obviously NOT persisted back to the sensors - hence my confusion when Victron seemed to allow the same configuration but instead throws away the changes. Rather than source a Lowrance MFD or find a buddy with one to temporarily hook up my sensor(s), I'll probably replace the Water sensor with the YD unit I have and simply live with the percentages on the fuel tank rather than gallons.

I also got a chance to look at the N2K output of the Victron gear, after turning off the phantom tank sensors (thank you @Bathnm!) I'm left with the Cerbo, SmartShunt, and two Multiplus devices. The Cerbo itself seems to have nothing useful:

But the SmartShunt has battery status and state of charge information that will be useful. In particular, it appears I can use the second input on the SmartShunt for the "Starter Battery" I was trying to configure in another thread:

I'm not quite sure why there are two Multiplus devices: they share the same useful PGNs except that one has a third PGN 127508 "Battery Status", this time with the Battery Current and Battery Case Temperature. Maybe both the Battery Current in the Multiplus and SmartShunt are correct and it was simply that I snapped them at different times.

Next time I get to my boat I'm going to attempt to configure the Lowrance sensors via N2KAnalyzer, probably setup the YD fluid sensor, and then tackle getting a N2K GPS (I have...4?) into the Cerbo. I also have several Victron temperature sensors that I'm going to hook up but I think I read that these aren't output to N2K from the Cerbo.

One caution is that it appears devices that have a GPS and output NMEA2000 GPS related PGNs will not work unless they are specifically class 60 and device function 145. Just generating the proper PGNs is not enough. I believe this is why I can't get my Vesper Cortex M1's GPS output to show up on my CCGX despite being seen as a device on the n2k bus. I'd love to be wrong. If this is correct it is a shame with the growing number of multi function devices.

IMO Vesper Marine (now Garmin) is complying with the regulations that state that AIS must have a dedicated GPS. Cortex reports device class Navigation (Class 60) and device function 195, which means dedicated AIS (according to NMEA 2000 Appendix B.6 Class & Function Codes)..."for the purpose of collision avoidance" and not primarily as a navigation device in order to comply with international regulations.

I can understand that Victron is going exactly the same route here and trying to comply as much as possible.with NMEA 2000 specifications. In a common ship setup nowadays this shouldn't be a problem as there are usually more than one device reporting navigation position.

I am not a NMEA 2000 expert and hope to never become one, so this comment is strictly from a user's perspective. I have two sources of n2k GPS info on my boat, one from the Vesper Cortex and one translated from 0183 by a Rose Point NEMO. Every other device I have that takes GPS input doesn't care what the device type is and will accept either, so this behavior was quite surprising to me when I first figured it out, especially coming from a 0183 world where the concept doesn't even exist.