Remote Monitoring

Instances can be confusing when multiple devices report the same PGN and how they should be or can be handled. One way is to handle them as device numbers, like you are doing. Another is to layer them like N2K was designed to do, but is more confusing in my opinion, and might not be warranted to be used that way in every system. But what I was talking about is this, temp probes also have a "type" associated with them, so the type is also used with the instance. Meaning instance 4 can be assigned to all temp probes that also have a different type. If you had 2 cabin temp probes then they would have to have different instance numbers assigned to them. By using the instance numbers this way there can be 256 temp probes for cabin temperature alone instead of 256 total device in the system. Does that matter to us, nope, but for mega-yachts and cruise ships it does. There are other PGN's that work this way as well, but because of that, instancing works this way.

Type is defined by the table below. But that's not to say you have to use them this way. There are many more type then just these, this is just what Yacht Devices YDTC-13 supports.

 

I am not that familiar with VV or SC. Except they are based on J1939 engine data parameters. J1939 in the beginning only referred to a single engine and didn't know about other engines so it only reported engine temperature without an instance because there was only one engine and there for could only have one temperature, one engine oil pressure. When VV and SC came about and started integrating other non-engine parameters into the mix, I am not sure what they did to accomplish that. Only that when it's converted to N2K it does have an instance number. It may be defaulted to 0 or 1 or 2, typical engine instances, but that is just a guess.

 

Yeah this is the case where instances are fantastic and make sense. But the ALM100 also uses types, just not in a confusing way, with how it has different sounder types. So the instance numbers are more like device numbers in this case.

I am using the DCR100 for alarms mostly. When were on the hook for a few days I wanted a way of be notified when we were low on water way before we ran out, but didn't want loud beeps to go off. So I took a channel form the DCR and ran it to two places, one at the helm and one at the electric panel. But is only a yellow light no sound. That way warnings can be shown but not hear and be handled as such. I also did the same for alarms with an alert sounder flasher so thigs like anchor drag and high water light up the boat and make a racket. I did that instead of running an N2K cable everywhere for alarms. I am using four conductor wire so that I wouldn't stretch the N2K total cable lengths past it's limits.

 

Tom, How do you use MARPA while anchoring? Don't the targets move to much at night when the boat swings? I have used ELB alarms and had false alarms. I totally get being prepared for sleeping better while on anchor. I actually try and anchor out on the edge of the anchorage field and use a stern anchor when possible, otherwise I am up every 1-2 hours checking on things ...

 

Yes "EBL" not ELB - Dam dyslexia gets me every time.

 

There is another great option for remote monitoring, the Garmin OnDeck hub. It also has five digital switched inputs for remote on/off capabilities. It operates through Active Captain as well so I guess Garmin has bigger plans for AC. It does require a subscription to access it remotely. But all in all it looks like the best option out there for accomplishing remote monitoring.

 

So I looked into this a bit more and spoke with Garmin Tech. and man what a disappointment that was. Hopefully things will change as this product matures but right now I don't know how anyone would even use it easily.

I was told the following, from your device (phone) active captain is how it communicates to with OnDeck, ok no big deal. But your phone has to connect to either the Garmin Marine Network through an MFD or the OnDeck device itself through WiFi direct connect (like the MFD's). It can not be connected to the boats internal wifi and if remote monitoring is being used you must activate and use the internal cell modem. It will not report remotely through wifi, only their cell modem. So maybe after a few FW updates things will change a bit.

On a side note, I was told you can connect the GMN to your boats ethernet and everything should work fine! SO that would mean Active Captain would be on the regular network and make life a whole lot easier when updating through AC. I am going to try this out and see how that works. But that would mean the OnDeck device would work a little better if that's an option.

 

No worries, I totally will. It's just going to be a while until I get around to doing that. I had tried it out a while back with no joy. But after thinking about how the MFD's boot, I probably tested this wrong. So I will now spend some time trying this out.

 

Yep I agree, I also saw the same thing and why I mentioned having to power the MFD on last, but not sure if I tried that or not. In speaking with the tech, he said he is N2K certified, so I am giving this another shot because he also said, he is working from home and said he can see his home network. I should have asked how that was accomplished but let it go. Meaning how he saw his home network on the MFD as to my knowledge there isn't a network browser.

 

Now that's a much nicer pic then my Foscam R4 PTZ. But I do keep it set on FD for data usage. Either way very nice indeed!