The data sent by device on HTTP data anycodings_zkteco buffer looks like 2\t 16:00:20\t1\t15\t\t0\t0\t\t\t43\nĪs you can see you parse this string anycodings_zkteco with '\t' as the separator of anycodings_zkteco informations User logs (clock_in / clock_out) Device anycodings_zkteco request POST /iclock/cdata?SN=XXXXXXXXXX&table=ATTLOG&Stamp=9999 Your server should just parse this data anycodings_zkteco and respond OK to this request something like this one PIN=2\tName=Johny Deep\tPri=0\tPasswd=\tCard=\tGrp=1\tTZ=0000000100000000\tVerify=0\tViceCard=\tStartDatetime=0\tEndDatetime=0\n With user information on the HTTP anycodings_zkteco buffer. When a user is registered on the device, anycodings_zkteco the device send this request POST /iclock/cdata?SN=XXXXXXXXXX&table=OPERLOG&Stamp=9999 Note that your ZkTeco Device should have anycodings_zkteco ADMS support, so that you will first anycodings_zkteco configure SERVER-IP and PORT on the anycodings_zkteco device (see your official device anycodings_zkteco documentation on ZKTeco website) You anycodings_zkteco can use a tool like Wireshark to scan anycodings_zkteco HTTP requests made by your device and anycodings_zkteco implement same request/response on your anycodings_zkteco own server.įor exemple, the ZKTeco device model anycodings_zkteco MB560-VL send requests like this one GET and if like the BioTime software, your anycodings_zkteco server just send OKĪs response in text/plain, your device anycodings_zkteco will view your server as a "BioTime"
The push SDK is just HTTP request made anycodings_zkteco by ZKTeco device to the Bioserver. Here is the solution anycodings_zkteco I had implement and it work properly. so I had try to anycodings_zkteco proceed otherwise. I took one month to find that fot that anycodings_zkteco PUSH SDK and ADMS, clearly ZKTeco is not anycodings_zkteco open to share that.
0 kommentar(er)
