Содержание
- Hik-Connect Offline Issue Resolved
- SADP Error Codes
- Hikvision SADP Tool Common Errors and Solutions :-
- 2009 device refuse to process
- 2011 device timed out
- 2015 sending error
- SADP pop up with error ”the software is running, please exit first” after installation
- 2022 The encrypted string is empty
- Interlogix TruVision Password Reset ( DVR, NVR, IP Camera)
- Hikvision OEM Password Reset Tool
- How to Reset Password on SADP — Hikvision
- 1. Reset Hikvision Password by SADP
- XML Key Generator Tool Ver 4.0 User Manual
- XML Key Generator Tool is a utility which helps you to get Encrypted XML file to unlock your IP Camera, DVR and NVR Network Devices.
- First you need to download SADP tool (Download Link: SADP Tool ) after downloading Right click on SADP Tool Setup file chose “Run as Administrator“ and install it, after installation complete right click on shortcut icon of SADP tool and run choosing “Run as Administrator”. (Note: — Your Network Device must be in same network to reset the password by SADP Tool)
- 2. Reset Hikvision Password by Hik-Connect App
- How to View Password Hidden Behind Asterisk
- How to View Password Hidden Behind Asterisk
- Desktop/Laptop
- On Google Chrome
- On Safari
- Android
- iPhone
Hik-Connect Offline Issue Resolved
When our customer adds a device to the Hik-Connect account and the APP returns device is offline, we can follow steps below to solve the problem or locate the causes.
1. Go to device to see the register status. The status can be saw on web GUI, local GUI.
a) If the Enable box hasn’t been checked, enable it and see the register status. Path: Configuration à Network à Advanced Settings.
On NVR 3.0: Menu-Configuration-Network-Platform Access.
On NVR 4.0: Menu-System-Network-Advanced.
b) If it has been enabled and the Register Status keeps offline, go to step 2.
2. Make sure the device has been connected to the Internet and it can connect to the Hik-Connect Server.
Go to device to see whether the IP parameters belong to LAN. The IP address, subnet mask and default gateway need to be set correctly. Path: Configuration-Network-Basic Settings-TCP/IP.
On NVR 3.0: Menu-Configuration-Network-General.
On NVR 4.0: Menu-System-Network-TCP/IP.
b) The DNS Server address is suggested to set as 8.8.8.8 or local frequently-used DNS address.
c) Try to change Server address, change dev.hik-connect.com to litedev.hik-connect.com or change litedev.hik-connect.com to dev.hik-connect.com.
d) Upgrade device to latest firmware.
3. If the Register Status is still offline, you may need to check the network.
a) Check the Hik-Connect Server accessible or not.
i. Connect your PC to the same LAN of the device.
ii. Go to windows start menu, input cmd and click Enter key.
iii. Input command ping dev.hik-connect.com and click Enter. If there is response, it means the DNS server address is correct and the Hik-Connect Server IP address is returned to the device.
If there is no response, the DNS server address need to be modified correctly.
b) Check if the fire wall blocks the connection between device and Hik-Connect Server.
i. Connect your PC to the same LAN of the device.
Go to windows start menu, input cmd and click Enter key.
iii. Input command telnet dev.hik-connect.com 8555 or telnet litedev.hik-connect.com 8666 and click Enter.
When the telnet works, it will display as the snapshot below.
v. If the telnet failed, you may need to check if there are settings on fire wall block the connection between the device and Hik-Connect server.
The Telnet function is disabled on PC as default, so it need to be enabled firstly. Path: Control Panel à All Control Panel Items à Programs and Features à Installed Updates à Turn Windows features on or off.
Источник
SADP Error Codes
Allocation of resource error
SADP not started
Get NIC info failed
Open NIC Failed
Sending Packet Failed
Get system interface failed
Device refuse to process
Install NPF failed
Device time out
Create socket failed
Bind socket failed
Join multi-cast failed
Multi-cast XML parse error
Device is locked
Device is not activated
High risk password
Device has been activated
The encrypted string is empty
Export file overdue
Long security answer
Security question number error
Load Wpcap failed
Illegal verification code
Hikvision SADP Tool Common Errors and Solutions :-
Parameter such as password, serial number, is empty.
When reset the password, imported file is empty or the file’s content has more than 512 bytes.
2009 device refuse to process
Password error, HTTP port number is invalid, IPv6 address is empty, IPv6 gateway is empty.
2011 device timed out
When SADP sends an request, and no response from the device after 10 seconds, it will give this error, in this situation we need to use Wireshark to capture the packets to analyze the response time from the device.
2015 sending error
When the IP address of the PC is changed, and SADP is not restarted, the error will occur.
SADP pop up with error ”the software is running, please exit first” after installation
When the installation directory is same as the installation package, ensure the software installation directory and installation package are not in the same directory.
2022 The encrypted string is empty
When import the XML file, and cannot find the corresponding encrypted string, the error will occur, we need restart the device and reset the password again.
Источник
Interlogix TruVision Password Reset ( DVR, NVR, IP Camera)
Reset password If an admin (not a specific user) device password is lost, contact CCTV Networking Technical Support ([email protected]) to restore the password. There are two ways to restore the password. The method to be used depends on the device and its currently installed firmware.
Software Download Link :-
To restore the default password (method 1):
1. Select the device for password reset in the main Device Manager window.
2. Click Device Manager Tools, and then click the Reset Password tool button.
3. Copy the serial number from the Device Serial No. field in the Device information panel and paste it into an email to send to [email protected] CCTV Networking Technical Support ([email protected]) will provide a security key by email.
4. Enter the security key received from CCTV Networking Technical Support ([email protected]) in the Security Code field and click OK to restore the default password. The default password is 1234.
Note: The security key provided is related to the date the serial number was sent to CCTV Networking Technical Support ([email protected]) and expires the day it was created. If the current date was not specified in the request, CCTV Networking Technical Support ([email protected]) provides a security key valid for one day following the date of the request.
To set a new password using an XML file (method 2):
1. Select the device for password reset in the main Device Manager window.
2. Click Device Manager Tools, and then click the Reset Password tool button.
3. Click the Reset Password button. 12 TruVision Device Manager User Manual
4. Click Export Reset File in the Reset Password window to save the XML file, and then email the file to CCTV Networking Technical Support ([email protected]). CCTV Networking Technical Support will provide a new XML file.
5. Save the XML file received from CCTV Networking Technical Support on the computer, click Browse, and select the new XML password file.
6. Type a new password and then confirm it in the New Password and Confirm Password fields. Click Apply.
Note: Do not restart the device after the password recovery XML file has been exported, otherwise the steps above must be repeated. The password recovery XML file expires after 48 hours.
Источник
How to Reset Password on SADP — Hikvision
1. Reset Hikvision Password by SADP
XML Key Generator Tool Ver 4.0 User Manual
XML Key Generator Tool is a utility which helps you to get Encrypted XML file to unlock your IP Camera, DVR and NVR Network Devices.
First you need to download SADP tool (Download Link: SADP Tool ) after downloading Right click on SADP Tool Setup file chose “Run as Administrator“ and install it, after installation complete right click on shortcut icon of SADP tool and run choosing “Run as Administrator”. (Note: — Your Network Device must be in same network to reset the password by SADP Tool)
After run the SADP tool, select your Network Device which need to reset.
After that click on Forgot Password Link. Export XML file and save on desktop.
Now keep SADP Tool Forgot Password windows open of SADP tool and use XML File Generator Tool v4.0
(Important Note: If you accidently close SADP Tool Forgot Password windows XML Key file will not work. You may need to generate new Exported file and use Network XML file generator v4.0 software again to get new XML Key file.)
Start XML Key Generator Tool Ver 4.0 Program.
First Screen (If you use Program within Time zone +5:30 IST you will get quick response from Key Server otherwise it can be not response or delay response.)
Fill All fields:-
1. Write your email id (This Email ID will receive XML Key file.)
2. Full Serial Number of Network Device (Copy from SADP Tool)
3. Attach Exported XML file from SADP Tool (.XML file)
Click on Generate Button and wait you will receive 2 Emails.
1. Do not download of 1st Email Attached XML file, this is just a confirmation email of Program successfully sent your XML Exported file to xml key server.
2. You will receive 2nd email from [email protected], Please download attached XML Key file to import in SADP tool for reset Network Device Password.
2. Reset Hikvision Password by Hik-Connect App
3xLogic Password Reset, ABUS Password Reset, Acegear Password Reset, Activecam Password Reset, ADJ Password Reset, Advidia Password Reset, VideoInsight Password Reset, Alarm Password Reset, Alibi Password Reset, Allnet Password Reset, Alula Password Reset, Anaveo Password Reset, Annke Password Reset, Arcdyn Password Reset, Armix Password Reset, AukooTechnology Password Reset, AventuraTechnologies Password Reset, Avue Password Reset, Cantek Password Reset, CCTVStar Password Reset, ClearWay Password Reset, CovertSecurity Password Reset, DaxNetworks Password Reset, DMP Password Reset, DodwellBMS Password Reset, DSS Password Reset, Dunlop Password Reset, DVRUnlimited Password Reset, EllipseSecurity Password Reset, Epcom Password Reset, Esypop Password Reset, Ezviz Password Reset, GlobalNetworkSecurity Password Reset, GovCommIntelligentTransportationSystems Password Reset, Grundig Password Reset, GVSSecurity Password Reset, Hinovision Password Reset, Hitachi Password Reset, Hitosino Password Reset, Honeywell Password Reset, HuntCCTV Password Reset, HyundaiSecurity Password Reset, InfinitePixels Password Reset, Inkovideo Password Reset, Innekt Password Reset, Interlogix(UTC) Password Reset, Invidtech Password Reset, IPCamTalk Password Reset, JFL Password Reset, Jlinks Password Reset, LaView Password Reset, LTS Password Reset, MercurySecurityandFacilitiesManagement Password Reset, MicroView Password Reset, Nelly’sSecurity Password Reset, NorelcoSafeCam/SpiderVue/Invezia Password Reset, Northern(Tri-Ed/Anixter) Password Reset, Novicam Password Reset, NTT Password Reset, Oculur Password Reset, A1SecurityCameras Password Reset, Onix Password Reset, Paxton Password Reset, Pnet Password Reset, PowerTechnology Password Reset, ProtectGroup Password Reset, Raster Password Reset, RemarkThermal Password Reset, RVi Password Reset, SafetyVision Password Reset, Safire Password Reset, Scati Password Reset, SecurityTronix Password Reset, SentryCCTV Password Reset, Sharp Password Reset, Siqura/TKH Password Reset, SmartCTSolutions Password Reset, SnapAV/Luma Password Reset, SpaceTechnology Password Reset, Syscom Password Reset, Technomate Password Reset, Toshiba Password Reset, Trendnet Password Reset, VantageSecurity Password Reset, VezcoCCTV Password Reset, Videoteknika Password Reset, Winic Password Reset, Xyclop Password Reset, Zicom
Источник
Desktop/Laptop
It is extremely simple to view a password hidden behind asterisks on a desktop browser. Here’s how to do it:
On Google Chrome
Follow the steps outlined below to view a password hidden behind asterisk on Google Chrome.
1. Launch Google Chrome and n avigate to the website from which you desire to view the hidden password. For example, I’m using Facebook.
2. Once the password autofills, select it and right click on it, then click on “ Inspect “.
3. This will open up Google Chrome’s Developer Tools.
- The console should automatically be focussed on the line related to the password field.
- If it is not, simply scroll down and find the line highlighted by Google Chrome.
5. Hit Return/Enter and on the Facebook Website, you should now be able to see the hidden password in plain text.
On Safari
The process on Safari is exactly the same, except, instead of “Inspect”, Safari’s menu will say “Inspect Element”, as shown in the screenshot below:
Android
The problem with using this technique on a mobile device like an Android or an iPhone, is simply that the mobile browsers do not have options such as “Inspect Element”. But, what they do have, is a neat little feature that allows remote USB Debugging of websites when the mobile is connected to a computer running compatible browsers.
For this Android example, I’m going to use Google Chrome, as it is one of the most used browsers on Android, and I happen to have Google Chrome on my laptop as well, which means no additional downloading required.
The steps you’ll need to follow to view a password hidden behind asterisks on an Android are given below:
1. In your Android device, enable USB Debugging through Settings->Developer Options.
2. Connect your Android device to your Laptop using a USB cable. Your phone will ask you whether or not it should trust the computer for USB Debugging; tap “Ok”.
3. Launch Google Chrome on your phone and navigate to the website from which you desire to view the hidden password. For example, I’m using Twitter.
4. Launch Google Chrome on your laptop and in the address bar, type “chrome://inspect”.
- This will open up a window with your Android device showing up under “Devices”.
- There will also be details about the tabs open on your phone.
5. Select “Inspect” under the tab that says “https://mobile.twitter.com”
6. This will open up the Developer Tools.
7. Press “Command + F ” to search and type “ password ” to go directly to the line corresponding to the password field.
8. Locate the field that says “type = password”, double click on it to begin editing, and replace the word “password” with “text”.
9 Hit Return/Enter and the password will now be visible in plain text, both in the Developer Tools, and on your Android phone .
iPhone
The procedure on an iPhone is easy as well, but in typical Apple fashion, can only be done with a Mac, using Safari. I know, right?
Anyway, the steps you will need to follow are:
2. On your Mac, launch Safari.
Note : You’ll first need to enable the Develop menu by going to Safari -> Preferences -> Advanced -> Show Develop menu in menubar.
3. Connect your iPhone to your Mac. Then, click on the Develop menu in Safari on your Mac.
- You should see the name of your iPhone visible in the Develop menu.
- Hover on it, to reveal the website you have opened on your iPhone.
- Click on the website, and you will be able to view its HTML code on your Mac.
4. Search for “ Password ” to find the line corresponding to the password field.
5. Change the value of type=”password”, from “ password ” to “text”.
6. Hit Return/Enter and you will now be able to see the password in plain text on your iPhone.
Note : Some websites, such as banking websites, disable right clicking for security purposes, therefore this method will not work for them.
Источник
Get the error codes via OpenSDK_GetLastErrorCode and get the error code information via OpenSDK_GetLastErrorDesc. The API only returns 0 and -1 by default (except some special API). The error code of SDK is listed according to modules. Major and frequently-occurred error codes are shown below.
error code is defined in the header file of OpenNetStreamError.h.
return via information callback function, refer to header file of INS_ErrorCode.h for details.
error code format{xbbbbb}, x represents the module type of error code, bbbbb represent what the error is, the value of x is shown below:
type | definition | remark |
---|---|---|
0 | correct condition | correct |
1 | network exception | This error is the same with network or configuration information error, so CURL ErrorCode is still available, for example, DNS is not configured. |
2 | user operation error | User level error code. It is usually caused by improper usage of SDK by the users. |
3 | platform server error | The error returned by OpenApi. For details, refer to error code of server port |
4 | system resource exception | Usually caused by inadequate system resource, e.g., inadequate memory. |
5 | get stream exception | error code of streaming module |
6 | method not supported | SDK unsupported |
7 | push error | push relevant error information |
9 | undefined error | error code without specific definition |
The following table shows the definition of the detailed error code value.
Description | Value | Definition | Remark |
---|---|---|---|
Network Level | |||
OPEN_SDK_COULDNT_RESOLVE_HOST | 100006 | unable to resolve to specified remote host | Here it refers that the domain name of the platform fails to be resolved. The reason maybe that the DNS is not configured or the device is disconnected. |
OPEN_SDK_COULDNT_CONNECT | 100007 | the remote host is unavailable | Here it refers to failing to access the platform. It may be caused by incorrect platform address. |
OPEN_SDK_OPERATION_TIMEOUT | 100028 | request timed out |
The expiry time is 20s. Request timed out. Check the address configuration of the platform. |
User Operation Level | |||
OPEN_SDK_BAD_PARAMS | 200001 | Invalid incoming parameter of API | |
OPEN_SDK_SESSION_INVALID | 200002 | The current session doesn’t exist or has been released. | incoming value of SessionId error or the Session has been deleted. |
OPEN_SDK_VIDEO_RECORD_NOT_EXIST | 200003 | No video file exists in the specified period. | |
OPEN_SDK_VIDEO_RECORD_SEARCHING | 200004 | Searching video records… | |
OPEN_SDK_STOP_ALARM_REC_FAILED | 200005 | Failed to disable alarm. | |
OPEN_SDK_PERMANENT_KEY_INVALID | 200006 | Incorrect verificaiton code. | |
OPEN_SDK_PIC_DECRYPT_FAILED | 200007 | Failed to decode the picture. | |
OPEN_SDK_PIC_CONTENT_INVALID | 200008 | Invalid picture content. | |
OPEN_SDK_PIC_NO_NEED_DECRYPT | 200009 | The picture doesn’t need to be decoded. | |
OPEN_SDK_PIC_COULDNT_ALLOC_BUFFERS | 200010 | Failed to allocate memory of picture resources. |
Insufficient memory or the picture size is too large. |
EZVIZ API Level | |||
OPEN_SDK_RESPINFO_BAD | 300001 | The information requested to return. json cannot resolve it. | It may be caused by the configuration problem ofPlatformAddr. |
OPEN_SDK_RESPINFO_INVALID | 300002 | Incorrect return information format of the request. | |
OPEN_SDK_ACCESSTOKEN_INVALID | 310002 | accesstoken exception or accesstoken has been expired. | |
OPEN_SDK_SIGNATURE_ERROR | 310008 | Incoming parameter error. System displaying signature error. | |
OPEN_SDK_USERID_PHONE_UNBIND | 310014 | The third-party userId and phone under APPKEY are unbound. | |
OPEN_SDK_CHANNEL_NOT_EXIST | 320001 | The channel doesn’t exist. | The channel corresponds with a specific camera. |
OPEN_SDK_USER_NOTOWN_DEVICE | 320018 | The user doesn’t have the device. | |
System Resource Level | |||
OPEN_SDK_COULDNT_CREATE_THREAD | 400001 | Failed to create a thread. | |
OPEN_SDK_COULDNT_ALLOC_BUFFERS | 400002 | Failed to apply memory resources. | |
Streaming Function Level | |||
OPEN_SDK_NS_OPERATIONCODE_FAILED | 500045 | Failed to get operation code. | It will report this error if users enabled terminal binding. |
OPEN_SDK_NS_STREAM_LIMIT | 500410 | Limit of streaming channel number | The device connection number reaches upper limit. |
OPEN_SDK_NS_DEV_NO_ONLINE | 503121 | Device offline | |
OPEN_SDK_NS_PERMANENTKEY_EXCEPTION | 502012 | Input key again. 1. Clear-text key and MD5 key mismatched. | Verification code error. |
OPEN_SDK_NS_VTDU_TIMEOUT | 502021 | Stream media sending or receiving signal timed out. | Check the device network status. It is usually caused by network problems. |
OPEN_SDK_NS_VTDU_CLIENT_TIMEOUT | 502025 | vtduThe client receiving response timed out. |
The camera and DVR/NVR may have connection problems. |
Unsupported Level | |||
OPEN_SDK_DEV_NOT_SUPPORT | 600001 | Only support device of version 1.7. | |
OPEN_SDK_API_NO_IMPLEMENT | 600002 | The API is not realized. | |
Push message level error. | |||
OPEN_SDK_PUSH_PARAM_ERROR | 710001 | Invalid incoming parameters. | |
OPEN_SDK_PUSH_DATA_UNINIT_ERROR | 710002 | The data is uninitialized. | Initialize by calling the API Init first. |
OPEN_SDK_PUSH_NO_REGISTER_ERROR | 710003 | Unregistered on the push system. | Call register API first. |
OPEN_SDK_PUSH_NO_MQTT_CREATE_ERROR | 710004 | Push object hasn’t been created. |
You haven’t call create API. |
OPEN_SDK_PUSH_MQTT_DISCONNECTED_ERROR | 720003 | sdk disconnected with push server. | Network disconnected or unstable network. |
OPEN_SDK_PUSH_MQTT_MAX_MESSAGES_ERROR | 720004 | The number of the received push messages reaches upper limit. | |
OPEN_SDK_PUSH_MQTT_BAD_UTF8_STRING_ERROR | 720005 | Invalid UTF-8 string. | |
OPEN_SDK_PUSH_MQTT_NULL_PARAMETER_ERROR | 720006 | The incoming parameter is empty pointer. | |
OPEN_SDK_PUSH_MQTT_VERSION_INVALID_ERROR | 730001 | Connection fails. Unsupported by the protocol version. | |
OPEN_SDK_PUSH_MQTT_IDENTIFIER_ERROR | 730002 | Connection fails, the only ID is incorrect. | |
OPEN_SDK_PUSH_MQTT_SERVER_UNAVAILABLE_ERROR | 730003 | Connection fails. The service doesn’t exist. | |
OPEN_SDK_PUSH_MQTT_BAD_USERNAME_PASSWORD_ERROR | 730004 | Connection fails. Incorrect mqtt username and password. | |
OPEN_SDK_PUSH_MQTT_NOT_AUTHORIZED_ERROR | 730005 | Connection fails. Unauthorized. | |
OPEN_SDK_PUSH_PLATFORM_RESPINFO_BAD | 740001 | The information returned by the request cannot be resolved normally by json. | It may be caused by invalid configuration of PlatformAddr. |
OPEN_SDK_PUSH_PLATFORM_RESPINFO_INVALID | 740002 | The format of the informaiton returned by the request is incorrect. | |
OPEN_SDK_PUSH_PLATFORM_SESSION_INVALID_ERROR | 740003 | Invalid session. | The session might has been released. |
OPEN_SDK_PUSH_PLATFORM_UNAUTHORIZED_ERROR | 740401 | Invalid certificate. |
It may be caused by invalid configuration of PlatformAddr. |
OPEN_SDK_PUSH_COULDNT_CREATE_THREAD | 750001 | Failed to create the thread. | |
OPEN_SDK_PUSH_COULDNT_ALLOC_BUFFERS | 750002 | Failed to apply memory resources. | |
OPEN_SDK_PUSH_COULDNT_RESOLVE_HOST | 760006 | The specified remote host is not been resolved. | Here it refers that the platform domain fails to be resolved normally. It may be caused by unconfigured DNS or disconnected device. |
OPEN_SDK_PUSH_COULDNT_CONNECT | 760007 | The remote host is unavailable | Here it refers that the platform is inaccessible. It may be caused by the configuration error of the platform address. |
OPEN_SDK_PUSH_OPERATION_TIMEOUT | 760028 | Request timed out. The expiry time is 20s. |
Sending request to platform timed out. Failed to access the EZVIZ OPEN platform. Check the configured address or the network. |
Undefined Level | |||
OPEN_SDK_ALLOCSESSION_FAILED | 900001 | AllocSession failed. | |
OPEN_SDK_SEARCH_RECORD_FAILED | 900002 | Failed to search playback records. | |
OPEN_SDK_START_ALARM_REC_FAILED | 900003 | Failed to enable alarm. |
Deleted previous comment since it seems those arose from trying to start with a project that had too much going on dependency-wise. Now where I’m at:
Re-compiled esp-open-sdk from the PR. Was getting linker errors for free
and calloc
like this:
/home/jeff/build/esp8266/sdk2/xtensa-lx106-elf/xtensa-lx106-elf/sysroot/usr/lib/liblwip2.a(mem.o): In function `mem_malloc':
/home/jeff/build/esp8266/sdk2/lwip2/lwip2-src/src/core/mem.c:136: undefined reference to `free'
/home/jeff/build/esp8266/sdk2/xtensa-lx106-elf/xtensa-lx106-elf/sysroot/usr/lib/liblwip2.a(mem.o): In function `mem_free':
/home/jeff/build/esp8266/sdk2/lwip2/lwip2-src/src/core/mem.c:151: undefined reference to `free'
collect2: error: ld returned 1 exit status
I think it’s looking for those in irom so I added malloc
+ free
methods in flash in my project that call os_xxx
methods. I was previously getting that to link some other way and it was crashing things immediately.
Next was fixing includes for my project. I think the issue is that esp-open-sdk copies esp-open-lwip
includes into sysroot
, so I needed to include the lwip2
folder in CFLAGS.
Now my test project can boot, and including <lwip/init.h>
gets MAJOR==2. But it seems something is broken still: Calling wifi_station_dhcpc_start()
shows the message that dhcp is starting up, and then calling wifi_station_connect()
I get the EVENT_STAMODE_CONNECTED
event. However after that, no IP address. I also tried setting a static IP/GW/mask and then calling connect, but I get:
connected with TestWiFi, channel 11
ip:192.168.1.55,mask:255.255.255.0,gw:192.168.1.1
lwESP: netif_set_up is called??ip:192.168.1.55,mask:255.255.255.0,11Wifi connected to ssid TestWiFi, ch 11
Wifi got ip:192.168.1.55,mask:255.255.255.0,gw:192.168.1.1
The router shows the ESP as associated but no IP. Is this a symptom of the older version in use? Or should I be getting an IP with dhcp? Or maybe something else I’m missing?
update:
I started working on some other stuff and just left my ESP sit on serial. Amazingly, I got an IP address finally, after about 30-35 minutes of nothing. Shows up on router and ping working. So that’s a good sign, but need to figure out what is up with DHCP. Thoughts? I let another esp sit and it took the exact same amount of time- perhaps something todo with a timer somewhere..?
update2:
Started working back up the commits with open-sdk. After c3f36d4 and rebuilt, DHCP works right away
-
#1
Hi, i have a Hikvision DVR 7208 HQHI, everything worked find for months, now without ! any changes, IVMS 4200 (no changes done too) tell me this, when i try to watch recorded Videofiles over the IVMS client:
Hikvision DVR Playback failed Error Code open SDK String Error 105 — Playback failed
When i go over the network straight to the DVR i can watch this recorded files, on the montior that is connected to the DVR, only IVMS 4200 on the PC tell me this error.
Nothing was changed, in one moment it dosent work anymore (the playback over IVMS)
Sorry for my English, iam from Germany.
Hope you understand whats the problem.
Regards
-
#2
Hi, I am having the same issue! I just noticed that the recorded video clips listed on the right of the screen are not in chronological order (see picture below). This seems to be causing the system to throw a string error. If you narrow your time span to include only 1 clip, it will play the recorded clip.
This is only occurring on devices that are Hik-Connect, local devices (on the same LAN as the iVMS-2400 client software) work fine.
Can anyone explain where this is coming from? It was working fine until recently.
Thanks. Brendan
-
#3
Hi Brendan, thats the same Problem over here, the files are not correct chronological, only by Hik devices, via Lan everything okay. Hikvision support is shxt ! No help.. wrote to UK,.com and Europe… no help !
-
#4
Hello? Can anyone on this forum help us? Are slot99 and myself the only ones having this bizarre behaviour of our iVMS clients?
Thanks.
-
#6
same here guys, new member, new install , in the uk, and installed last week,
remote playback over the internet via hik connect same error,
local lan playback no error
convinced its a hik connect issue somehow
-
#7
This is a known problem that will be fixed with Hikvisions next IVMS upgrade. The is a OpenNetStream.dll file that needs to be updated in the C:Program FilesiVMS-4200 StationiVMS-4200iVMS-4200 directory. If you email me at FredWentworth@NewEnglandcctv.com with your email, I can send you the file.
We have had to do this for every client using Hik-Connect for remote viewing/ playback in the past 6 weeks or so. Its a simple fix.
-
#8
This is a known problem that will be fixed with Hikvisions next IVMS upgrade. The is a OpenNetStream.dll file that needs to be updated in the C:Program FilesiVMS-4200 StationiVMS-4200iVMS-4200 directory. If you email me at FredWentworth@NewEnglandcctv.com with your email, I can send you the file.
We have had to do this for every client using Hik-Connect for remote viewing/ playback in the past 6 weeks or so. Its a simple fix.
Hi @FredWentworth, can you send me the file? I have the same problem!
Last edited: Feb 19, 2018
-
#9
This is a known problem that will be fixed with Hikvisions next IVMS upgrade. The is a OpenNetStream.dll file that needs to be updated in the C:Program FilesiVMS-4200 StationiVMS-4200iVMS-4200 directory. If you email me at FredWentworth@NewEnglandcctv.com with your email, I can send you the file.
We have had to do this for every client using Hik-Connect for remote viewing/ playback in the past 6 weeks or so. Its a simple fix.
Cant you just upload the file, so anyone can download?
-
Forums
-
Manufacturer Specific Forums
-
Hikvision
You should upgrade or use an alternative browser.
Device error, OpenSDK stringerror 510004
-
Thread starterrkg
-
Start dateJan 23, 2022
-
#1
-
#2
What model is your NVR and which firmware version is it running?
Which version of iVMS-4200 are you running?
Is this on a Windows or macOS device?
- Thread starter
-
#3
IiVMS-4200 version V3.6.0.6 build20210630 (iVMS says that is latest version)
OS: Windows 10
-
#4
- Thread starter
-
#5
-
#6
- Thread starter
-
#7
-
#8
Sorry, I’m not sure what else the issue could be I can’t find any other mention of that error code, so it may be specific to HiWatch devices.
If you can, I’d ask your supplier to ask Hikvision Support about the error code. Or, take it to them directly, as they’ll probably know what it means — support.uk@hikvision.com
- Thread starter
-
#9
-
#10
-
#11
Similar threads
-
Forums
-
Manufacturer Specific Forums
-
Hikvision
Просмотров: 158 552
SERSIIG SAC eyessecuritechcom
1 месяц назад
excelente video
Robert Stefan
4 месяца назад
Hello i hope u can help i get The error with (7), the camera îs New im using a UTP ca le linked to my laptop în order to log în to make The network config and im getting this error
Saroj Tamrakar
5 месяцев назад
How to fix DS Logins failed. Error Code iVMS-4200.exe[100]. (Device type error.)
Андрей Юхновский
6 месяцев назад
I can’t find the problem anywhere. Help please. If the PC and the camera are connected to the same Wi-Fi router (it has a 4G SIM card), then there is no problem. If the PC and the camera are on different Internet networks, then such a problem appears only when viewing the recording, when viewing online there is no problem at all.
ivms 4200 string error 525416
Thank you.
Sundar Rajan
7 месяцев назад
HOW TO RESOLVE ERROR CODE 525416
Moha Med
1 год назад
I have an other error code HCNetSDK.dll[5] no more user can be connected. Can you help me pls
muhammad arifshah
1 год назад
Can any one help me in opensdk 200013 error code.
Office Terlesky
1 год назад
Hello, while trying to access settings I get an error code «HCNetSDK.dll[23] not supported» I can not do firmware update in Guarding Vision- it says upgrade failed. Thank you
Wi Castle
1 год назад
Hello.Thanks for the video. can you help me? I get this error openSDK|20013| what´s the meaning?
RAJU PANDIT
1 год назад
Sir error code 260015 aa raha hai kese thik kare
Rashmi Editing Point
1 год назад
Thanks….Is video is solved my issue
Виктор Автушко
1 год назад
абсолютно полная хуйня
перезагрузка не решает проблему , а отодвигает ее на неопределенный срок
потом будет все тоже самое, и опять придется перезагружать
уверен, что проблема кроется либо в прошивке камер, либо в самой программе iVMS-4200
M. Ahsan
1 год назад
Bhai agr verification key disable kr daen tu pir nvr online rahy ga.keun k ivms 4200 main bar bar key dalni parti ha
M M
1 год назад
Just subscribed to your channel. I have a dvr that I am trying to reset using the reset file sent to me from hikvision. I keep getting a 2022 error though when I try to upload it. Can you please tell me what that error means and how can I fix it?
You can Do it
1 год назад
What the hell is this background music
kaif momin
1 год назад
thanks a lot your video help me to solve this eror
Rodolfo Grimán
2 года назад
mi error es hcnetsdk.dll 7
Muhammad Dusooqi
2 года назад
Reconnecting.Error Code HCNetSDK.dll[28].(No enough device resource.)
Erick Carballo
2 года назад
I have the error code 18 and 64, but I can’t find information about that, can you help me?
I try to use the library HCNetSDK.dll
Работа с облаком и настройки удаленного доступа
Удаленный доступ на камеры и регистраторы Hikvision и HiWatch можно реализовать следующими способами.
1) Если используется белый (публичный) статический IP, то на роутере настраиваете проброс портов 80 554 и 8000 (uPnP рекомендуем отключить)
2) Если используется серый IP, то единственный способ настроить доступ — p2p сервис Hik-Connect, возможен удаленный просмотр и удаленный просмотр архива. Запись в облако не происходит.
Личный кабинет Hik-connect
Инструкция по настройке p2p сервиса Hik-connect / Guarding vision
Рекомендации по первоначальной настройке сети панелей Ax Pro
Как отвязать устройство от облачной учетной записи
Российские адреса серверов:
dev.hik-connectru.com
litedev.hik-connectru.com
Для домофонии — litedev.hik-connectru.com
IVMS 4200
Перепрошивка камер и все что с ней связано
Обновить прошивку можно через web интерфейс устройства, как обычный роутер, либо через клиентское ПО IVMS-4200.
Обновление необходимо производить последовательно. 5.1.X -> 5.2.X -> 5.3.X -> 5.4.X
C прошивок 5.3.X на 5.2.X и с 5.4.X на 5.3.X откатиться НЕ ПОЛУЧИТСЯ!!!
Инструкция по обновлению
Вы можете откатить прошивку (к примеру) с 5.3.8 на 5.3.3 с помощью TFTP, с 5.3.8 до 5.2.0 откатиться НЕЛЬЗЯ!
Перепрошивка через TFTP
Перепрошивка регистраторов все что с ней связано
Мы рекомендуем проводить обновление через клиентское ПО IVMS-4200 или утилиту BatchConfigTool
Инструкция по перепрошивке
Восстановление устройства с помощью прошивки через TFTP
IP Камеры: аудио вход и выход
IP Камеры: схема обжима
RTSP ссылки
RTSP-ссылки
Основная и универсальная ссылка для IP камер, NVR и DVR:
rtsp://admin:12345@192.168.200.11:554/ISAPI/Streaming/Channels/101
где:
rtsp — тип используемого протокола
admin — имя учетной записи
12345 – пароль используемой учетной записи
192.168.200.11 — IP-адрес камеры
554 — RTSP порт камеры (по умолчанию 554, может быть изменен в настройках)
101 — это 1 камера 1 поток
201 — это 2 камера 1 поток
102 — это 1 камера 2 поток
IP каналы HD-TVI регистраторов
7204 — 501 601;
7208 — 901 1001;
7X16 — 1701 1801 и т.д
Для вызывных панелей:
rtsp://admin:12345@192.168.200.11:554/Streaming/Channels/101
Устаревшие ссылки:
rtsp://admin:12345@IP-камеры:554/mpeg4/ch01/main/av_stream
получение потока с первого канала
rtsp://admin:12345@IP-камеры:554/mjpeg/ch1/sub/av_stream
получение потока mjpeg со второго потока. прошивка должна поддерживать mjpeg на втором
потоке.
MJPEG и фото:
Для получения MJPEG-потока по HTTP (суб-поток камеры должен быть настроен как mjpeg)
Перевести в MJPEG можно только суб-поток камеры.
IP Камеры: тревожный вход и выход
Подбор кронштейнов и монтажных коробок
Таблицу совместимости камер Hikvision с аксессуарами вы можете скачать тут
Таблицу совместимости камер HiWatch с аксессуарами вы можете скачать тут
С паспортами для аксессуаров вы можете ознакомиться по данной ссылке
Список протестированных HDD и SD карт
Как просматривать устройство в браузере
Для Windows
Для просмотра через web требуется установить плагин Web Components
- В Internet Explorer в разделе Свойства обозревателя->Дополнительно разрешите запуск сторонних плагинов.
- В Chrome и браузерах на его основе, например Yandex browser разработчиками была отключена поддержка сторонних NAPI плагинов. По данной причине потребуется установить расширение IE Tabs Инструкция по настройке просмотра в Chrome
- В Opera плагин не работает
- В Safari плагин не работает
Для MacOSX
Используйте клиент iVMS-4200 для macosx
Домофония
Перед настройкой обновите прошивки устройств до актуальных версий.
После обновления обязательно сделайте полный сброс настроек устройств.
Для работы с первым поколением устройств используйте клиент iVMS-4200 3.1.1.9
Для настройки второго поколения домофонии скачивайте актуальную версию
Настройку необходимо осуществлять на АНГЛИЙСКОМ ЯЗЫКЕ. Сменить язык на русский вы можете после.
Второе поколение устройств:
Домофоны: DS-KH6320-(W)TE1, DS-KH8350-(W)TE1, DS-KH8520-(W)TE1
Вызывные панели (V серия): DS-KV6113-(W)PE1, DS-KV8X13-WME1 и дверной звонок DS-KV6103-PE1
Модульная вызывная панель DS-KD8003-IME1
Прошивки вы можете скачать тут
Инструкция по настройке 2 поколения домофонии Intercom 2.0
Инструкция по настройке 2 поколения домофонии Intercom 1.0
Настройка терминалов доступа DS-K1T50X в качестве вызывных панелей для второго поколения домофонов
Подключение считываетелей к вызывным панелям и терминалам доступа
Если планируете подключать интерком устройства через Wi-Fi, просьба ознакомиться с данной инструкцией.
Первое поколение домофонии было представлено моделями:
Домофоны: DS-KH6210, DS-KH6310-(W,L), DS-KH8301-(WT), DS-KH8300-T
Вызывные панели (V серия): DS-KV8X02-IM, DS-KV8102-VP(IP)
Многоабонентские вызывные панели (D серия) : DS-KD3002-VM, DS-KD8002-VM, DS-KD8102-V
Актуальные прошивки на перечисленные устройства вы можете скачать тут
Инструкции по настройке вы можете найти на нашем ftp