The Swords Of Ditto 1.1.1 Apk Data For Android
Frauke Vilandre
Note that the Cortex Hub can connect directly to as many as 5 Cortex handsets, and simultaneously to 5 more handsets or app devices via a boat network. And that Vesper is saying the next feature up is intercom between handsets.
Well, I not only received an early Cortex, but had also faithfully entered what I thought to be a zero, many times, until that prompt got me to notice how CORTEX is printed near the password and realize that Vesper had also used a compressed font. As Homer Simpson would say: DOH! Or Cortex manual style: D0H!
I am the Build Manager for North Pacific Yachts, so I have been enthusiastically suggesting Cortex to our new boat buyers. For context, the Cortex system is a $350 upgrade from the less integrated items we have been installing (including the AIS8000). A no brainer IMHO. I am so glad that Vesper is just making this better and better. And that sites like Panbo are giving context for its use. In other news, I am close to justifying a Cortex on my own boat! Question: Why get the wired handset? The Vesper rep says that wired only means power.
Thanks Ben and Sabado, yes tried that and no success. There just seems no menu to select sound output options-as there was in earlier version of firmware before i upgraded. Have drawn a blank on that. Does anyone have a menu allowing selection of sound output?
If you press the volume up or volume down button, the option between handset, hub, and hailer volume should pop up. It has been started, but probably worth restating, that the tethered handset uses WiFi for audio, the cord only supplies power.
PS I think that NEMO can deliver engine info because Rose Point came up with their own way to do it from N2K engine PGNs. And I also think that NEMO, or NEMO2, may become one of the first NMEA OneNet devices that can put all NMEA 2000 data onto Ethernet/WiFi in a standard way.
Ray, they will probably work fine for you, but do keep a close eye for possible problems with individual batteries. Also suggest you check out the many Firefly threads on the Cruisers Forum, like this one:
However, the Cortex hub includes an antenna splitter so that maybe you could keep the B&G radio for VHF backup and hailing. I have my test Cortex set up that way, so one antenna is handling Cortex VHF and AIS while a Standard Horizon is still able to do VHF and AIS receive (and hailing if I had one attached).
At any rate, I think that Vesper will expand the N2K data it can read because now it can bridge that info to its remote monitoring system where much more than basic nav info is useful. In fact, I suspect that some of the offboard monitoring will eventually work with the Cortex handsets so that we could be told in a nice but insistent voice that, say, a bilge alarm had been triggered.
But I think that you should stick with your current Signal K setup or explore other ways to get an SK server on your boat. There seems to be activity on that front recently, as seen on the Digital Yacht blog and the CPN site.
As stated before, I own 2 units on different boats (sail & open console). Aside from lack of some critical table-stakes features, I experienced VHF problems and general reliability issues requiring restart or had updates failing. I love the hardware, but am increasingly disappointed with the software quality.
Vesper customer technical service support, accessible from their web site, has a form for technical questions. They are very responsive, but remember, it is in New Zealand, so the response is typically next a.m. in U.S. east coast.
We have a Garmin chartplotter and Vesper Vision2, so debating going to the Vision2 or just a Garmin VHF to allow the easy DSC hailing that supposedly works between chart-plotter and VHF. The Garmin radio would allow separate antennas to be used.
Option 2: Sell iCom 604, Watchmate Vision 2, install Cortex. Plus: gain anchor watch/remote monitoring to some degree, 5 watt SOTDMA AIS with message 27 so maybe picked up be satellites in remote regions, cons: still some bugs, no hailer support
A direct DSC call via the VC does indeed work, but the inability (at present) to perform a direct DSC call via the VC from an MFD in my thinking conflicts with one of the basic premises behind an MFD; all functions from a single user interface. Juggling between devices at the helm takes valuable time, is awkward and distracts from focusing on essential navigation tasks while underway. Will I hit that crab trap while fumbling between multiple user interfaces on different devices? My ten year old retired Garmin MFD did direct DSC calling from an AIS target on the MFD via NMEA 2K to the 10 year old Garmin VHF. My brand new Axiom+ network linked by NMEA 2K to either my VC or SH GX2400 cannot yet do the same. Another item that hopefully VC will update in software with multiple MFD vendors.
Does anyone really use DSC for calling? My chart plotter and VHF are linked but I gave up using it after I found that both recreational and commercial vessels respond much more frequently to just hailing them on ch 16 or ch 13 using their name.
Apparently this is Release Version Cortex v1.6.14 which contains handset 1.6.5 and Hub 1.6.2229. Details can be found at support.vespermarine.com support portal>resources>Firmware Updates. I was away for a few days, it was released on 22 June 2021.
Any rumors on when 1.7 or the new squelch might hit release branch? How does one sign up for beta? I have everything torn apart for some new antenna and coax installs, so this would be an opportune time to move the hailer from the Garmin to the Cortex.
1.8, that according to NZ Tech Support will address the squelch granularity (lack thereof) and other items; based upon how 1.7 is being handled, my best guess is we will be lucky to see it in 1Q 2022.
Regarding the audio quality issue, I cannot attest, as due to the squelch issue I use my non-Vesper stand alone VHF for fear of losing an important incoming VHF message to poor squelch. In essence, my VC is an excellent primary AIS, but it is my standby VHF. I shall perform some audio quality tests among my marina neighbors and post my anecdotal results as soon as I can.
Looking forward to the squelch features and channel scanning. Vesper has improved the squelch quite a bit. Early on certain Channels were unusable in quite a few places. Most are now on with the current settings.
Hi Sven, The release version of 1.7 went out to beta testers a few days ago, so I think it will be out quite soon. My test situation is poor right now, with the boat in a steel shed, but the new features looked well done to me. Info on the wiring here:
Hoping his means some additional investment and integration. I saw it as inevitable as the concept for Vesper has been great, but their execution a little lacking and this is the kind of innovation that usually results in an acquisition. It will be interesting to see how the M1 and Garmin VHF/AIS/OnDeck products all merge.
Ray: I am not tracking the beta firmware, but can confirm wifi is problematic here too. Not quite as bad as your description, but the cortex wifi network is pretty weak, using the boat network helps get better range but even then the handset has both a very poor range (30 feet line of sight is too much for it) even with a very strong signal on every other device.
It is also a bit unfortunate that having the Cortex Monitor plans existing provides a strong disincentive for Vesper to open up the Cortex system to more third party integrations, since they could then be used to effectively replace the subscription.
I kind of agree with you Marc but what other VHF or AIS system provides this kind of connectivity? Does the Victron system provide tracking and anchor watch out of the box? Believe me, I have my share of complaints against Vesper but I also believe they ARE innovating.
I was disappointed that the GPIO data on the Cortex is not available on the H1 handset. You need your phone connected to cellular to view your GPIO data in real-time. This makes no sense at all for an offshore cruiser.
When you go to configure the GPIO settings it is on the H1 handset. In that same screen there is an icon that shows if the sensor is enabled or not. When I connected it to my bilge pump I can see the icon change color when my bilge punp is enabled in real time. It would be really easy for the developers to make another screen on the H1 with the GPIO sensor data since it is already present in the config screen. Unfortunately it is not very usable in the config screen and would need a dedicated screen. I am an android developer if Garmin is looking for help.
My main disappointment has been the unrealized promise of substantive updates. The big draw for me was that it was touted as being software based, and as such, would be easy to add new features. Those new feature updates have been few and far between.
I have been waiting not so patiently, for the ability to scan channels. You know, like almost every other VHF out there. What we got was an update where the device no longer forgets that you were in dual-watch mode.
I hope they launch a version that works better, but I expect most current owners including myself to be very disappointed with having to pay big bucks to replace existing hardware in order to get previously promised features.
I also did not receive any weather channels during my brief test of v2.0, but thought it was because my boat is inside a steel building.
Will experiment further soon, and hope other v2.0 users report in.
Have you tried a new charging cradle? Early on I had charging problems despite a multimeter showing power. I bought a new cradle and had no further problems over the last 18 months. I also keep a thin coat of NoOXID electrical grease on both sets of contacts to protect against oxidation..
Fine to call me out, Tim, but to be clear I used Cortex on my boat all last season and for a couple of months when it first came out in late 2020. The shop testing was only to try v2.0 and the Cortex will go back on the now-launched boat very soon. At any rate, I recall that the handset had trouble connecting to the hub a couple of times on start up, but never underway or when I was trying to use the radio. Meanwhile, the AIS never failed and I usually run it 24/7.
b37509886e