Run a Python script after APLR Licence plate detection, just won't work as a service, OK in console.

[bignose3]

I cannot get my python script to run in Windows 10. tried for 2 days & driving me made as think must be something obvious.

AI LPR works fine, recognized & on the ALPR dashboard
Same trigger emails a picture

These 2 both Work in windows 10 console using TEST : pyw being the run time/no window option & just runs, service may not understand this so use py.exe with the same file but just py.
eGate.pyw
\\homecamspc\Users\Oem\Documents\eGate.pyw

works in cmd prompt
C:\windows\py.exe "c:\Users\Oem\Documents\eGate.py"
BUT error's in the TEST -
I think this might be the reason behind the problem, not finished the question & going to try a few things but posted in case someone knows straght off.

tried all variation above with the UNC instead
\\homecamspc\Users\Oem\Documents\eGate.pyw








Sorry incomplete but don't think can save as draft.

 

[biggen]

I don't have any direct knowledge running python from BI but C:\windows\py.exe "c:\Users\Oem\Documents\eGate.py" looks funky. That runs like that in cmd, huh?

 

[jaydeel]

This configuration of the Run action is working for me for a python script… ‘py.exe’ also works in the ‘File’ field.



I posted earlier about a recent change to the ‘File’ field - it now accepts direct editing.

5.4.8 - June 16, 2021 - A DeepStack status page has been added

5.4.8 - June 16, 2021 A DeepStack status page has been added. This allows you to inspect DeepStack results and performance following an alert confirmation or when using the testing & tuning options in the clip viewer. You may now specify 2 objects together with “and” logic on the “to confirm”...

ipcamtalk.com

Here’s a screenshot of running the script in cmd.exe…

 

[bignose3]

Many, Many, thanks

this works so simply & in service mode, have no idea why my single command line stuff did not, especially as it did under cmd but not going to think about that anymore.