A
Anonymous
Guest
Not sure if my signature will appear so here is our setup:
MFD12(Master) - Installed since new in 09 running 2.11
MFD8(Slave) - Installed yesterday now running 2.11
HUB101
DFF1
DRS4D
We've been having problems with the MFD12 for around 2 years that we havent quite gotten to the bottom of. That was desribed in one of my previous posts. Long story short the MFD12 was having trouble seeing the N2K network from time to time. Also (which became apparent after the MFD8 install) the MFD12 is very slow through menus and charts etc.
So we decided to complicate our problem.
We added the MFD8 for the obvious reasons, but also the plan was to move the N2K network to the MFD8 and see if our lack of N2K network followed us, or if the problem was th MFD12 all along. We didn't quite get that far.
We bought the MFD8 used. After install we powered up the MFD8 on its own without the network connected just to test it. It came on as a slave with the no master warning. Next step was to power it up on the network. On boot up, we noticed in the blue bar it was only running 2.07. So as soon as it came on (it did pick up our waypoints from the master) we booted it down and started the update to 2.11. The update seemed very quick to me as i remember it but the next boot up the blue bar said 2.11. Golden.
Here come the weird issues.
When having the MFD12 and 8 both set to full screen radar, if you zoom one screen in our out both screens mimic each other, almost like a repeater. So if you move the 12 from 1 mile to 4 miles, the 8 will move from 1 mile to 4 miles without touching it.
The fishfinder seems to not be working correctly. When both screens are on, the fishfinder will freeze and the image will not scroll. Also ETR Connection was Cut warning comes on both screens from time to time.
I did't flip the dip switch on the HUB101 for the 8 yet, though I will. (they are on the back of the HUB so I need to unmount it correct?) This allowed us to power on the Master 12 only. It worked fine with everything. As soon as we powered on the 8 it began to have the problems I mentioned.
We also tried switching the 8 to Master and the 12 as Slave and had the same issues.
The 8 seems at least twice as fast as the 12 leading us to believe something has been wrong with the 12 all along. All sensors (both N2K and Ethernet) are seen by both MFDs, They both have the same system ID and are running the same software, same version.
Could the problem be that they were both on running different software and networked for a short time? Could that have corrupted something?
Is there something a little more intrusive than just a master reset we can try with the 12?
We really need help and have exhausted everything we thought we could do. I fear the next step is to pull out the 12 and send it to Furuno which will put us in a whole right in the middle of the season. It is very apprent to me that the 12 has some type of issue that may not be able to be diagnosed by us.
Thanks for any help!
MFD12(Master) - Installed since new in 09 running 2.11
MFD8(Slave) - Installed yesterday now running 2.11
HUB101
DFF1
DRS4D
We've been having problems with the MFD12 for around 2 years that we havent quite gotten to the bottom of. That was desribed in one of my previous posts. Long story short the MFD12 was having trouble seeing the N2K network from time to time. Also (which became apparent after the MFD8 install) the MFD12 is very slow through menus and charts etc.
So we decided to complicate our problem.
We added the MFD8 for the obvious reasons, but also the plan was to move the N2K network to the MFD8 and see if our lack of N2K network followed us, or if the problem was th MFD12 all along. We didn't quite get that far.
We bought the MFD8 used. After install we powered up the MFD8 on its own without the network connected just to test it. It came on as a slave with the no master warning. Next step was to power it up on the network. On boot up, we noticed in the blue bar it was only running 2.07. So as soon as it came on (it did pick up our waypoints from the master) we booted it down and started the update to 2.11. The update seemed very quick to me as i remember it but the next boot up the blue bar said 2.11. Golden.
Here come the weird issues.
When having the MFD12 and 8 both set to full screen radar, if you zoom one screen in our out both screens mimic each other, almost like a repeater. So if you move the 12 from 1 mile to 4 miles, the 8 will move from 1 mile to 4 miles without touching it.
The fishfinder seems to not be working correctly. When both screens are on, the fishfinder will freeze and the image will not scroll. Also ETR Connection was Cut warning comes on both screens from time to time.
I did't flip the dip switch on the HUB101 for the 8 yet, though I will. (they are on the back of the HUB so I need to unmount it correct?) This allowed us to power on the Master 12 only. It worked fine with everything. As soon as we powered on the 8 it began to have the problems I mentioned.
We also tried switching the 8 to Master and the 12 as Slave and had the same issues.
The 8 seems at least twice as fast as the 12 leading us to believe something has been wrong with the 12 all along. All sensors (both N2K and Ethernet) are seen by both MFDs, They both have the same system ID and are running the same software, same version.
Could the problem be that they were both on running different software and networked for a short time? Could that have corrupted something?
Is there something a little more intrusive than just a master reset we can try with the 12?
We really need help and have exhausted everything we thought we could do. I fear the next step is to pull out the 12 and send it to Furuno which will put us in a whole right in the middle of the season. It is very apprent to me that the 12 has some type of issue that may not be able to be diagnosed by us.
Thanks for any help!