Question on the Marcum update

Has any confirmed with Marcum that the sensitivity range was actually shifted with the 4.07 update? I’ve read a few reports that people are having to reduce the sensitivity setting with the new update but there is no mention of this in the description of updates. I’m a little nervous to update if this is the case as I’m already running at the lower end of the sensitivity range with 3.17 and if it shifts any lower I might have trouble with larger baits that I sometimes fish. Just want to confirm before I update.

Thanks,

Joe

The sensitivity did change. Some people are really liking the update and that the devices run better. Then you have some people like me that are having issues.

http://youtu.be/vU5UqOJQwVk

I’m bringing mine into Marcum tomorrow. I’ll post what the results are in the firmware thread.

Quote:

---

The sensitivity did change. Some people are really liking the update and that the devices run better. Then you have some people like me that are having issues.

http://youtu.be/vU5UqOJQwVk

I’m bringing mine into Marcum tomorrow. I’ll post what the results are in the firmware thread.

---

Forgive me but I am struggling to see the problem, it appears the vertical chart reading is good at a 2-3 sensitivity but the trouble is with the chart which looks to be at a 5′ zoom. I do agree when you make a minor adjustment to the sensitivity it shouldn’t make as large of an impact. Are you concerned with the depth of the return on the chart zoom? I used mine yesterday and it seemed to work well, although I did only used it for a few hours.

look again, it quite reading bottom all together when it was set to 0?

And that it wouldn’t read the jig at all when switched to 20 degree. And yes the sensitivity jump is rather large.

^^^^ I noticed that ^^^^^^

Quote:

---

look again, it quite reading bottom all together when it was set to 0?
And that it wouldn’t read the jig at all when switched to 20 degree. And yes the sensitivity jump is rather large.

---

My bad, I didn’t think anything of that coming from an LX3 last year where the gain was 0 there was no reading, I will have to check mine for that next time out. I did notice on my 7 yesterday that I needed to turn the sensitivity up when switching from the 8 to 20 degree cone.

Quote:

---

Quote:

---

look again, it quite reading bottom all together when it was set to 0?

And that it wouldn’t read the jig at all when switched to 20 degree. And yes the sensitivity jump is rather large.

---

My bad, I didn’t think anything of that coming from an LX3 last year where the gain was 0 there was no reading, I will have to check mine for that next time out. I did notice on my 7 yesterday that I needed to turn the sensitivity up when switching from the 8 to 20 degree cone.

---

Looks pretty normal to me. Gain 0 or sensitivity 0 mean just that, no read. About the only difference I notice is that on the 20 degree it needs sensitivity of 3 to pick up while on 9 degree it picked it up at 2. I dont expect both cones to perform exactly the same. Sensitivity of 2 and 3 are pretty low to me. I set mines at 4 or higher with target ID of 1.

Sensitivity of zero before the update still read the bottom.
If zero now effectively shuts the sonar off, whats the point of having it do that? I might as well just hit the power button.
The one thing I noticed is that I was in the new dynamic mode. I forgot to switch it over to one of the other modes and see if it made a difference.

Marcum REALLY needs to do a better job of making documentation available for us on what the changes are in each release.

Quote:

---

Sensitivity of zero before the update still read the bottom.
If zero now effectively shuts the sonar off, whats the point of having it do that? I might as well just hit the power button.
The one thing I noticed is that I was in the new dynamic mode. I forgot to switch it over to one of the other modes and see if it made a difference.

Marcum REALLY needs to do a better job of making documentation available for us on what the changes are in each release.

---

I have never set sensitivity to 0 on the digital Marcums, never had the need to so I can’t provide feedback on that. But if things fall in line as it always has for Marcum as well as their mechanical sonars then 0 means 0. None of the mechanical Marcum show read at 0. Always has been like that for as long as I know. It only makes sense for the digital Marcums to do the same. This allows Marcum to dial in the precision range of gain settings. If you want something that can’t adjust gain to 0 at all get a Vexilar? This may be one of the reasons why Vex incorporates a low power mode and others don’t.

I think Marcum should fix the problem with some of the lx-7’s that are out there. Some part in this machine is causing some or most of the problem. Some of the lx-7’s have worked great right from the get-go…a lot of others haven’t. So if the units are made the same and one has issues while others are not, find and fix the problem instead of writing programs to cover up. Now you got people down loading these fix’s on perfectly working units and screwing them up. You have to explain to the public that the d/l is a fix not some magical upgrade. This could end in a disaster…it has already started.
Im on Marcums side but they have to stop…and start over.

The latest update focused on adding new features, the sensitivity change is just getting all the attention.

The sensativity change is kind of a big deal. It is the main reason I’m not updating mine.

I think the update works fine. Things have been changed. I ran my updated unit side x side last night with a lx7v3.07 and it did run less well in 28′. The update had issues clearing out suspended particles in roygb and 3 color compared to the old version. This has been the only setup where the new firmware obviously under performs compared to the old.

Classic problem here…