Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Yamaha command link engine ID problem
11-28-16, 10:58 AM (This post was last modified: 11-30-16 02:27 PM by Chuck - Raymarine - Moderator.)
Post: #11
RE: Yamaha command link engine ID problem
Bill,

When you performed the Engine Identification procedure and completed identification of the port engine, did you then leave the port engine running, or was the port engine not running but switched ON, when you attempted to identify the starboard engine?
Visit this user's website Find all posts by this user
Quote this message in a reply
11-29-16, 12:51 PM (This post was last modified: 11-29-16 01:07 PM by Chuck - Raymarine - Moderator.)
Post: #12
RE: Yamaha command link engine ID problem
port engine NOT running but switched on when I ID'd the starboard engine. This has always worked before.
The yamaha command link gets power from the port ignition switch so it has to be on when any engine identification proceedure is happening.
Find all posts by this user
Quote this message in a reply
11-29-16, 01:13 PM (This post was last modified: 11-30-16 02:28 PM by Chuck - Raymarine - Moderator.)
Post: #13
RE: Yamaha command link engine ID problem
Bill,

Thanks for the requested information. Our engineering team has requested information regarding whether one or two ECI-100s have been installed.
Visit this user's website Find all posts by this user
Quote this message in a reply
11-30-16, 01:46 PM (This post was last modified: 11-30-16 03:03 PM by Chuck - Raymarine - Moderator.)
Post: #14
RE: Yamaha command link engine ID problem
I'm using one ECI-100. This set up has been working until very recently when I updated the ECI-100 software to the latest version.
Find all posts by this user
Quote this message in a reply
11-30-16, 01:48 PM (This post was last modified: 11-30-16 03:05 PM by Chuck - Raymarine - Moderator.)
Post: #15
RE: Yamaha command link engine ID problem
One more thing.........Although the raymarine date page have worked reading both engines in the past, it has never registered enging temp. I get everything but that.
Find all posts by this user
Quote this message in a reply
11-30-16, 03:17 PM
Post: #16
RE: Yamaha command link engine ID problem
Bill,

In support of your claim that the V16 software in conjunction with the last ECI-100 software update did not suffer the reported issues with engine data from your dual engine Command Link system, I have provided links to the v16.47 and previous ECI-100 software update below.

Note: the last software update for the ECI-100 (v1.20) was released in August 2015 and as such would have been expected to have been installed within the ECI-100 when v16.47 was running in your MFD.

- a/c/e/eS/gS-Series MFD v16.47

- ECI-100 v1.12
Visit this user's website Find all posts by this user
Quote this message in a reply
12-12-16, 01:19 PM (This post was last modified: 12-12-16 01:37 PM by Chuck - Raymarine - Moderator.)
Post: #17
RE: Yamaha command link engine ID problem
I put the V16 back on my E127. My command link data seems to work somewhat better. Now when I start the port engine it reads data OK. then when I start the starboard engine, the port engine loses data signal. So I know I'm getting data from both engines.
I can't figure out how to load the V1.12 software on to the ECI 100 though. 1.20
It does have the V1.20 now. I think it had the V1.12 on it when I bought it though.
I'd like to try reinstalling it.
I have it on a chip. And both green lights are on when I turn on the E127 with the V1.12 in the slot. It doesn't load to the E-100 though.
What am I doing wrong?

Thanks Bill
Find all posts by this user
Quote this message in a reply
12-12-16, 01:37 PM
Post: #18
RE: Yamaha command link engine ID problem
Bill,

Unlike the latest software update for the ECI-100, the v1.12 software update was not not an ISO file. The ECI-100 v1.12 software update download was a zip file. You will need to extract the three files contained within the zip file to the root level directory of the microSD memory card. With the MFD powered OFF, the microSD memory card would then be inserted into the MFD's memory card reader and the MFD would then be powered ON to start the software update process.
Visit this user's website Find all posts by this user
Quote this message in a reply
12-12-16, 02:43 PM (This post was last modified: 12-13-16 09:09 AM by Chuck - Raymarine - Moderator.)
Post: #19
RE: Yamaha command link engine ID problem
I did exactly as above, inserted into E127 with it off. Powered it on and got no update. When I put the SD card back in my PC to make sure it had everything on it, one file had been added "Lighthouse ID text"
So I guess the mfd saw it.
I still have V1.20 on the E-100 tohough
What next?
I'm thinking that if I can get the V1.12 on it will fix my problem
Find all posts by this user
Quote this message in a reply
12-13-16, 09:07 AM (This post was last modified: 12-13-16 09:08 AM by Chuck - Raymarine - Moderator.)
Post: #20
RE: Yamaha command link engine ID problem
Bill,

It turns out that the autorun files found within the ECI-100 v1.12 software zip were intended for MFDs operating with software prior to LightHouse Release 16. Download the attached R15.autorun.files.zip file and replace the rayatom.autorun.00.sh and rayatom.autorun.00.sh.sig files on your microSD memory card with those found within the R15.autorun.files.zip file.


Attached File(s)
.zip  R15.autorun.files.zip (Size: 215.18 KB / Downloads: 101)
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us