Bullseye Posted August 7, 2022 Share #351 Posted August 7, 2022 It works perfect on dva1622 on Intel J3544 an amd A2…. But it wont start on P620 and DVA3221, why ? I dont know 😕 Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted August 7, 2022 Share #352 Posted August 7, 2022 (edited) 1 час назад, Orphée сказал: It still detects persons and vehicules. Play with words if you want, the task does its job. Of course not as good as in daylight, but still, the configured task is working as good as it can do. Feel free to consider it is not enough for your standards. But yes AI advanced detection still works in IR night condition, no matter what you think. Friend, the only one who plays with words is you, showing your night time People detections with supported GPU which we discussed early not only 1650 is supported, will not solve other people's problems, I dont really care how it works on your system, like I said before if you happy with the result, its good for you and I am happy for you too) but it looks like you have some feelings towards me personally because you started to tell me what can I expect with my T400 if it only works with 1650, while my other 1660 works too. And you upset that I told you that you didn't pay attention and didnt read all previous posts, because it looked like it and it was a constructive note, not an insult in any way. But when a different person with P620 says gpu detected but has some troubles you are trying to suggest something (even if your result is far from acceptable and totally different AI function from what a person has trouble and its very strange why didnt you tell that person that his gpu is not supported), because you want to troll or argue with what synology official recommendations say or my words, double standards or its just personal)? You didnt advice that person anything that might help him resolve his problems, except "look at your gpu memory" and "it works at night" but my words insulted you. Well if I hurted your feelings in anyway I apologize, but if you have something to say which really helps others without trying to troll others, please do) and stay on topic or otherwise there is PM. Thank you. Edited August 7, 2022 by dimakv2014 Quote Link to comment Share on other sites More sharing options...
Bullseye Posted August 7, 2022 Share #353 Posted August 7, 2022 Strange, there i see my CAR on J3455 and HD 500, and on E2-6110 and R2 radeon, but it wont run on J3455 and P620 and E2-6110 and P620.... Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted August 7, 2022 Share #354 Posted August 7, 2022 2 минуты назад, Bullseye сказал: Strange, there i see my CAR on J3455 and HD 500, and on E2-6110 and R2 radeon, but it wont run on J3455 and P620 and E2-6110 and P620.... As far as I understand: AI works for you on dva1622 with both Intel J3455 with igpu and amd E2-6110 with igpu, but it doesnt want to detect on dva3221 with J3455 and P620? But you said it was working before on dva3221? Quote Link to comment Share on other sites More sharing options...
Orphée Posted August 7, 2022 Author Share #355 Posted August 7, 2022 (edited) 33 minutes ago, dimakv2014 said: ... Actually, I gave him some suggestion to look at factual logs, to check if there is some kind of errors in it. With these logs, we might be able to catch something. But feel free to ignore it. By showing memory usage, I actually suggest something must be wrong on his configuration compared to mine... Then back to logs that might give some help/error/hints. He talked about his 4 cameras and about night, you answered it does not work at night. Well, the fact that it does not identify face or read license plate (I did not test it actually) does not mean AI detection does not work. as shown above, the AI detection task still "works". So it is not like you said "does not work", so technically talking about "facts" the DVA features work at night IR, it was all I wanted to point at. I don't have anything against you, but you choose to ignore or arrange what I say to your needs/feelings. Feel free to ignore or consider I troll, wich I'm not. I actually give some template about how it should like when it work. Feel free to answer/troll again, case closed for me, I won't read/answer anymore. Edited August 7, 2022 by Orphée Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted August 7, 2022 Share #356 Posted August 7, 2022 (edited) 13 минуты назад, Orphée сказал: Actually, I gave him some suggestion to look at factual logs, to check if there is some kind of errors in it. With these logs, we might be able to catch something. But feel free to ignore it. By showing memory usage, I actually suggest something must be wrong on his configuration compared to mine... Then back to logs that might give some help/error/hints. He talked about his 4 cameras and about night, you answered it does not work at night. Well, the fact that it does not identify face or read license plate (I did not test it actually) does not mean AI detection does not work. as shown above, the AI detection task still "works". So it is not like you said "does not work", so technically talking about "facts" the DVA features work at night IR, it was all I wanted to point at. I don't have anything against you, but you choose to ignore or arrange what I say to your needs/feelings. Feel free to ignore or consider I troll, wich I'm not. I actually give some template about how it should like when it work. Feel free to answer/troll again, case closed for me, I won't read/answer anymore. my bad, by meaning "AI works at daytime" (Face Rec and Lic Plate Rec) I meant with acceptable result (always event detection, with fully recognized face from database or new one, same for license plate), otherwise why would anyone need it? Again, this information is in Synology dva admin recommendations, how camera must be positioned and which day time or night time for each AI function is in official recommendations on synology website. As for logs yes, sorry about that you are correct you gave a person suggestion to look in logs. Edited August 7, 2022 by dimakv2014 Quote Link to comment Share on other sites More sharing options...
error403 Posted August 7, 2022 Share #357 Posted August 7, 2022 Here's the information about my P2000. It does get recognized correctly, but does not work in SS at all. At the moment I gave up on building a NAS. The info is for a better understanding of those cards. Quote Link to comment Share on other sites More sharing options...
Bullseye Posted August 7, 2022 Share #358 Posted August 7, 2022 6 hours ago, dimakv2014 said: As far as I understand: AI works for you on dva1622 with both Intel J3455 with igpu and amd E2-6110 with igpu, but it doesnt want to detect on dva3221 with J3455 and P620? But you said it was working before on dva3221? Yes, once it work Ok im stay on E2-6110, its much faster (im dont know why). And the final question is, i should turn off iGPU and stay with just P620 ? Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted August 7, 2022 Share #359 Posted August 7, 2022 Только что, Bullseye сказал: Yes, once it work Ok im stay on E2-6110, its much faster (im dont know why). And the final question is, i should turn off iGPU and stay with just P620 ? If you want to save a little watt power and lower cpu temps you can do that ) igpu doesnt do much in dva3221 ) Quote Link to comment Share on other sites More sharing options...
Bullseye Posted August 7, 2022 Share #360 Posted August 7, 2022 (edited) 5 minutes ago, dimakv2014 said: If you want to save a little watt power and lower cpu temps you can do that ) igpu doesnt do much in dva3221 ) Ok, so finnaly DS3221 stared fine, but i have roblem with add ONVIF camera now.... holy crap :( I have u cant connect to the camera. But i have it on Onvif list, with correct IP, etc... Can be onvif too old version for modern SStation ? Edited August 7, 2022 by Bullseye Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted August 7, 2022 Share #361 Posted August 7, 2022 3 минуты назад, Bullseye сказал: Ok, so finnaly DS3221 stared fine, but i have roblem with add ONVIF camera now.... holy crap :( I have u cant connect to the camera. But i have it on Onvif list, with correct IP, etc... Can be onvif too old version for modern SStation ? Could be port 554, you can try Generic Dahua instead Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted August 7, 2022 Share #362 Posted August 7, 2022 1 час назад, error403 сказал: Here's the information about my P2000. It does get recognized correctly, but does not work in SS at all. At the moment I gave up on building a NAS. The info is for a better understanding of those cards. Thats very strange situation, especially when P620 works and its supported in 440.44 drivers as well as linux kernel, I guess its something else, maybe bios settings? if anyone else with p2000 from Dell could comfirm that its working please post. Quote Link to comment Share on other sites More sharing options...
Bullseye Posted August 7, 2022 Share #363 Posted August 7, 2022 7 minutes ago, dimakv2014 said: Could be port 554, you can try Generic Dahua instead 554 is for rtsp that works fine. Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted August 7, 2022 Share #364 Posted August 7, 2022 (edited) 25 минут назад, Bullseye сказал: 554 is for rtsp that works fine. Yes sorry its 80 port in your case for onvif connections. What I did with my Dahua, changed it to 1025 and then add port number 1025 and choose http in settings when adding new cam Edited August 7, 2022 by dimakv2014 Quote Link to comment Share on other sites More sharing options...
Bullseye Posted August 7, 2022 Share #365 Posted August 7, 2022 And again, with P620 i have just this: Quote Link to comment Share on other sites More sharing options...
Orphée Posted August 7, 2022 Author Share #366 Posted August 7, 2022 And about the logs ? Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted August 8, 2022 Share #367 Posted August 8, 2022 4 часа назад, Bullseye сказал: And again, with P620 i have just this: Download this video from youtube in at least 720p better 1080p (google how to save video from youtube): You will have .mp4 file upload it to your nas, add camera User Defined and put this .mp4 and create a task on this cam. Then after few hours of working show results. This is for testing purpose) Quote Link to comment Share on other sites More sharing options...
Bullseye Posted August 8, 2022 Share #368 Posted August 8, 2022 6h works that movie in 1440p, nothing detected still nvidia-smi use just 98mb vram so something is wrong. maybe SS try start on iGPU ? (but in smi shows that SS works in that graphic). Quote Link to comment Share on other sites More sharing options...
Orphée Posted August 8, 2022 Author Share #369 Posted August 8, 2022 6h works that movie in 1440p, nothing detected [emoji20] still nvidia-smi use just 98mb vram so something is wrong. maybe SS try start on iGPU ? (but in smi shows that SS works in that graphic).Can you PLEASE look at the logs ?!in /var/log/surveillance/ folderalso in /var/log/messagesalso in /var/log/synoscgi.log Quote Link to comment Share on other sites More sharing options...
Bullseye Posted August 8, 2022 Share #370 Posted August 8, 2022 5 hours ago, Orphée said: Can you PLEASE look at the logs ?! in /var/log/surveillance/ folder also in /var/log/messages also in /var/log/synoscgi.log Im think this will be most intresting: Aug 8 14:39:29 [5168][5179][synodva][error] common.cpp:28:log(): severity: 1, msg: INVALID_CONFIG: The engine plan file is generated on an incompatible device, expecting compute 6.1 got compute 7.5, please rebuild. Aug 8 14:39:29 [5168][5179][synodva][error] common.cpp:28:log(): severity: 1, msg: engine.cpp (1324) - Serialization Error in deserialize: 0 (Core engine deserialization failure) Aug 8 14:39:29 [5168][5179][synodva][error] common.cpp:28:log(): severity: 1, msg: INVALID_STATE: std::exception Aug 8 14:39:29 [5168][5179][synodva][error] common.cpp:28:log(): severity: 1, msg: INVALID_CONFIG: Deserialize the cuda engine failed. What can i do with that ? synoscgi.zip Quote Link to comment Share on other sites More sharing options...
Orphée Posted August 9, 2022 Author Share #371 Posted August 9, 2022 (edited) 16 hours ago, Bullseye said: Im think this will be most intresting: Aug 8 14:39:29 [5168][5179][synodva][error] common.cpp:28:log(): severity: 1, msg: INVALID_CONFIG: The engine plan file is generated on an incompatible device, expecting compute 6.1 got compute 7.5, please rebuild. Aug 8 14:39:29 [5168][5179][synodva][error] common.cpp:28:log(): severity: 1, msg: engine.cpp (1324) - Serialization Error in deserialize: 0 (Core engine deserialization failure) Aug 8 14:39:29 [5168][5179][synodva][error] common.cpp:28:log(): severity: 1, msg: INVALID_STATE: std::exception Aug 8 14:39:29 [5168][5179][synodva][error] common.cpp:28:log(): severity: 1, msg: INVALID_CONFIG: Deserialize the cuda engine failed. What can i do with that ? synoscgi.zip 467.74 kB · 1 download In your logs : ug 7 21:03:32 S82surveillance.sh: Start Surveillance [9.0.1-7673] end. Aug 7 21:03:48 [27043][27054][synoface][error] memory_controller.cpp:61:VacuumImpl(): CUDA error code=100 name="cudaErrorNoDevice" string="no CUDA-capable device is detected" Aug 7 21:03:48 [27029][27039][synodva][error] memory_controller.cpp:61:VacuumImpl(): CUDA error code=100 name="cudaErrorNoDevice" string="no CUDA-capable device is detected" Aug 7 21:03:52 [27074][27076][ss-service][notice] ssdaemonmonitord.cpp:54:CheckDaemon(): Daemon [faced] stopped abnormally, auto restart. Aug 7 21:03:53 [27485][27496][synoface][error] server.cpp:51:Listen(): expect path /tmp/synofaced.sock not exist Aug 7 21:03:53 [27074][27076][ss-service][notice] ssdaemonmonitord.cpp:54:CheckDaemon(): Daemon [dvad] stopped abnormally, auto restart. Aug 7 21:03:53 [27501][27511][synodva][error] server.cpp:51:Listen(): expect path /tmp/synodvad.sock not exist Aug 7 21:04:08 [27501][27512][synodva][error] memory_controller.cpp:61:VacuumImpl(): CUDA error code=100 name="cudaErrorNoDevice" string="no CUDA-capable device is detected" Aug 7 21:04:08 [27485][27498][synoface][error] memory_controller.cpp:61:VacuumImpl(): CUDA error code=100 name="cudaErrorNoDevice" string="no CUDA-capable device is detected" Aug 7 21:04:13 [27074][27076][ss-service][notice] ssdaemonmonitord.cpp:54:CheckDaemon(): Daemon [faced] stopped abnormally, auto restart. Aug 7 21:04:13 [28622][28633][synoface][error] server.cpp:51:Listen(): expect path /tmp/synofaced.sock not exist Aug 7 21:04:13 [27074][27076][ss-service][notice] ssdaemonmonitord.cpp:54:CheckDaemon(): Daemon [dvad] stopped abnormally, auto restart. Aug 7 21:04:13 [28638][28648][synodva][error] server.cpp:51:Listen(): expect path /tmp/synodvad.sock not exist Aug 7 21:04:29 [28622][28636][synoface][error] memory_controller.cpp:61:VacuumImpl(): CUDA error code=100 name="cudaErrorNoDevice" string="no CUDA-capable device is detected" Aug 7 21:04:29 [28638][28650][synodva][error] memory_controller.cpp:61:VacuumImpl(): CUDA error code=100 name="cudaErrorNoDevice" string="no CUDA-capable device is detected" Are these old logs ? Did you change anything in the meantime ? Because it seems "no CUDA-capable device is detected" Your ssdevice.log is flooding about SOAP xml failed errors. whereas my ssdevice.log is "empty". Your /var/log/messages is flooded by : 2022-08-08T19:13:43+02:00 SynologyNVR kernel: [77879.964802] synodvad[22218]: segfault at 0 ip 00007fbf75b05c60 sp 00007fbf000206e8 error 4 in libdvacore-dl.so[7fbf75aef000+57000] 2022-08-08T19:13:43+02:00 SynologyNVR coredump[22228]: Process synodvad[22206](/volume1/@appstore/SurveillanceStation/synodva/bin/synodvad) dumped core on signal [11]. Core file [/volume1/@synodvad.synology_denverton_dva3221.42661.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synodva/bin/synodvad ] 2022-08-08T19:13:55+02:00 SynologyNVR coredump[22228]: Core file [/volume1/@synodvad.synology_denverton_dva3221.42661.core.gz] size [63958633] segfault means the process totally crash. So the process tries to start and instant crash in loop... also Between 14h39 and 19h13 service ssdaemonmonitord "stopped abnormally" 844 times. Edited August 9, 2022 by Orphée Quote Link to comment Share on other sites More sharing options...
Bullseye Posted August 9, 2022 Share #372 Posted August 9, 2022 Ok, i will clean all logs, and i will start again add that AI. Because ill testet a lot of thinks before with disconnect ssd also (to see how system will work if one hdds broken). But all the time P620 is inside the PC, nvidia-smi shows P620 also. mayby this cars is broken? Quote Link to comment Share on other sites More sharing options...
Orphée Posted August 9, 2022 Author Share #373 Posted August 9, 2022 Or the card is not supported by surveillance station...Restart your NAS and check logs again 1 Quote Link to comment Share on other sites More sharing options...
Bullseye Posted August 9, 2022 Share #374 Posted August 9, 2022 32 minutes ago, Orphée said: Or the card is not supported by surveillance station... Restart your NAS and check logs again 00007f63a4032b28 error 4 in libdvacore-dl.so mostly. Logi.zip Quote Link to comment Share on other sites More sharing options...
rok1 Posted August 10, 2022 Share #375 Posted August 10, 2022 (edited) I built a DVA3221 system based on an i3-10100 w/ PNY GTX1650 super. Plex works fine with hw encoding. Updated to 7.1.0-42661-u3 without issue. After a week or so of testing, I'll rebuild it in my server case that has an i7-10700 with RTL8125 2.5gbe nics. Edited August 10, 2022 by rok1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.