Recent content by gmaxwheel

  1. G

    Firmware for DH-TPC-SD5600(-t) thermal camera? (now with cute thermal video of deer)

    Here is a bribe for replies: thermal footage of deer. I'd also settle for a binary for my current version (2.400.0000.2.R.FFFF.3S.NR), so that I could attempt a tftp/uart reflash with some expectation of being able to restore the camera if it doesn't go well. :)
  2. G

    Firmware for DH-TPC-SD5600(-t) thermal camera? (now with cute thermal video of deer)

    I found firmware on the dahua website: https://www.dahuasecurity.com/support/downloadCenter/firmware?child=231 Unfortunately, the readme for it states "If the current version of main firmware is V2.401.0000.1.R.20160802 or older, you must first...
  3. G

    Firmware for DH-TPC-SD5600(-t) thermal camera? (now with cute thermal video of deer)

    Greetings. I have a DH-TPC-SD5600-T running "2.400.0000.2.R.FFFF.3S.NR, build : 2016-01-26". The camera works fine, but as soon as a NVR running V3.216 connects the web server on the camera crashes (and comes back up in a minute). Without pointing the NVR at it, its stable PTZ works, rtsp...
  4. G

    IPC-HDW5231R-ZE IP changed on its own, can't login

    Yep, I'm aware. I'll go ahead and do that if no other great ideas come up. Not likely in this case, -- camera network is physically disconnected from the internet. More likely that I somehow did it, though I can't imagine how or why. :)
  5. G

    IPC-HDW5231R-ZE IP changed on its own, can't login

    Correct. My recorder is a dahua NVR608-32-4KS2. The camera is on a fairly boring POE ethernet switch. I know what port it's on. I don't believe the failure coincided with a power outage on that switch, but I can't be absolutely sure of that (it was a couple months ago, I've been putting off...
  6. G

    IPC-HDW5231R-ZE IP changed on its own, can't login

    One of my HDW5231R-ZE dropped off my DVR after a couple months running, I thought it was dead but after chasing it down, I discovered that it somehow changed IP to 192.168.1.50 from where it had been running (an an entirely different subnet). It should be running a somewhat older firmware...
Top