Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[AWVKRS]

So both Mac and Windows 10 fail to work and get the camera working with the MDL service?

Was there a case number for reference of the phone contact with D-Link support?

I have reported the IR LED issue to D-Link and they've added it to the list of cameras to review for this issue.

Case ID:  C6924676

So both Mac and Windows 10 fail to work and get the camera working with the MDL service?   Yes.  The installation wizard reports back, "Could not connect to the Internet", so I am never presented with the options where I enter the MyD-Link credentials.  This happens with Windows 10 and Mac OS.

I have reported the IR LED issue to D-Link and they've added it to the list of cameras to review for this issue.  Thank you! So there are issues of this same problem on the other D-Link cameras? I ask this because the more widespread the problem the more attention it will receive.

By the way, thank you for helping me with my problem, I appreciate it very much.

[FurryNutz]

The IR LED is affecting a few models. 

[BAMoh]

The IR LED is affecting a few models. 

Which models?

[AWVKRS]

Which models?

FurryNutz, probably knows more, but the DCS-5029L for certain.

There's a couple of ways you can see if your camera has this problem.  Manually put the camera into the daytime mode. Go to a totally dark room and look straight at the IR emitters.  If the camera is working as it should, you will see absolutely nothing.  A faint red glow indicates the problem.

I discovered this on my  many DCS-5029Ls almost immediately by the camera looking out of a window at night. The infrared light reflects off the glass and spoils the image.

[RYAT3]

The IR LED is affecting a few models. 

Which models?

I mentioned it in the previous page. 1st or 2nd response

[FurryNutz]

Beta posted for the IRLED issue:
http://forums.dlink.com/index.php?topic=65855.0

Please post your findings there.

[AWVKRS]

1.14.02_Beta Firmware for DCS-5029L appears to have solved the problem of the IR LEDs not turning fully off when disabled.

I have now installed this Firmware update on several DCS-5029L cameras with no harmful effects that I can detect.

[FurryNutz]

Thank you for posting your experience. Glad the fix worked.

Enjoy. 

[AWVKRS]

>>  This is not a Beta, this is an official release. B02 = Build 02, not beta.  <<

Very confusing.  The file that I downloaded a couple of weeks ago ( 1.14.02_Beta ) has been removed. The latest version that they show is 1.14.02.  It has NO "B02" in the name.

http://support.dlink.com/productinfo.aspx?m=DCS-5029L

I have 1.14.02 installed on some cameras WITH the IR LED bug.  The 1.14.02 they show is dated 11-14-2016.  Surely they wouldn't have two different versions of firmware with the same revision number !?!?   I am trying to help others with this problem and I need to be able to point them to the proper firmware to install.

[FurryNutz]

The beta was to help test the LED issue, once we helped to confirm it, I presume they removed the "BETA" from the file name and officially posted it as v1.14 Build 02.
Just because the .zip file naming convention isn't the same as the actual FW version, doesn't mean its different.

Review the release notes.

You are using the same version. No worries.

[AWVKRS]

The beta was to help test the LED issue, once we helped to confirm it, I presume they removed the "BETA" from the file name and officially posted it as v1.14 Build 02.

OK, but it NOT posted as v1.14 Build 02.  It is posted as 1.14.02. This is the exact same number as the Firmware WITH the bug. You CAN'T have two different versions of software with the same version number, it's mind boggling!

[FurryNutz]

The original Beta was posted on the 7th which is my original date I posted this thread notifying users of the v1.14.02 "Beta" of the LED fix and to let us know if it was definitely fixed. Then on the 14th, since getting results back, D-Link didn't make any changes to the v1.14.02 "Beta" code and just took out the "beta" from the file naming convention and leaving v1.14.02 in the .zip file name.
v1.14.02 = v1.14 Build 02
So no reason for graduating build numbers or version numbers.

Nothing confusing about it.

[AWVKRS]

Nothing confusing about it.

In early October 2016 I was pushed 1.14.02.  I installed this on multiple DCS-5029L cameras.  A few days later (10-I4-16)  I came to these forums to discuss the IR LED bug.

Now (as of 11-7-2016) we have NEW Firmware 1.14.02 where the bug has been fixed.  ( I just tested a camera with the [October 2016] 1.14.02 Firmware, IT HAS THE BUG ).  I have a another DCS-5029L with the more newly installed [November 7-2016] 1.14.02, it does NOT have the bug. 

When I access the cameras built-in webpage, BOTH the cameras with the bug and cameras without the bug report the SAME 1.14.02 Firmware. 

D-Link has two different published versions of their firmware with the same revision number. Confusing.

[FurryNutz]

Use the 11-14-16 dated version and you'll be fine.

[AWVKRS]

Use the 11-14-16 dated version and you'll be fine.

I agree!!

In my 35 years of computer experience this is the first time I've ever seen two different versions of software be given the same revision number.  Because of this, it is not possible for me to remotely tell what version of the firmware is actually on the camera without performing an IR LED test.

Because of my familiarity with the issues I can sort this out. However, I know that other people with the same problem will struggle.   

Fortunately, I kept a copy of the 1.14.02_Beta firmware. So when I install it it has the word "Beta" in the revision. I will use this for my own purposes so I can keep track of what I've got. Perhaps in the future, a newer version of the firmware will be issued that will make this problem go away.

Again, thank you for your patience and understanding, I know that you are not the person assigning these same revision numbers.