RE: Using ultimateALPR‑SDK.dll via Node.js (ffi‑napi) – licence workflow and sample code

[Mamadou DIOP]

Hi,

The SDK will returns plates even if you don't have a license. 

You cannot move/transfer a license 

We don't have Javascript sample, not officially supported 

Sent from my Galaxy

-------- Original message --------

From: Tilen <tilen.m...@gmail.com>

Date: 4/18/25 14:14 (GMT+01:00)

To: doubango-ai <douba...@googlegroups.com>

Subject: Using ultimateALPR‑SDK.dll via Node.js (ffi‑napi) – licence workflow and sample code

Hi,

We have successfully loaded ultimateALPR‑SDK.dll from Node.js using ffi‑napi, but—since we are running the unlicensed build—the SDK returns no plates and prints the usual “unlicensed version” warning.

Could you clarify three points for us, please?

1. Once a valid token is supplied, will the SDK immediately start returning recognised plates?
2. Licence logistics:
   • may we activate a licence on our in‑house development machine for testing and later move it to the customer’s server, or
   • does each physical machine require its own permanent runtime/slave licence?
3. Would it be possible to provide a minimal working JavaScript (ffi‑napi) example that shows the correct DLL call sequence and plate extraction?

Thank you very much for your help.

Tilen

--
You received this message because you are subscribed to the Google Groups "doubango-ai" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doubango-ai...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/doubango-ai/8e55e3ab-26f3-423f-9934-2f9996c21651n%40googlegroups.com.

[Mamadou DIOP]

Hi,

- No use for RAM or MAC address. Any other hardware change (CPU, motherboard, hard drive....) will invalidate your license. The exact hardware depends on the OS and obviously I'll not give you such information as it's confidential.

- No support for VMs.

- Support for Docker on x64 only and must not be within a VM

On 4/22/2025 12:34 PM, Tilen wrote:

Hi Mamadou,

Thanks again for your quick reply!

To better assist our customers and ensure continuous operation without licensing interruptions, could you please clarify a few more points regarding license binding and virtualization:

1. Hardware Binding:

   • Exactly which hardware components (e.g., motherboard, CPU, MAC address, hard drive identifiers) does the license activation rely upon?

   • What types of hardware changes, like adding RAM, replacing disks, swapping motherboards, or reinstalling the operating system, would cause the license to become invalid?

2. Virtualization:

   • We understand licenses can be activated on physical servers, AWS/Azure VMs, and Docker containers.

   • For "wild" virtual environments like VMware or VirtualBox, I noticed it specifies to contact you directly. Could you detail any special requirements or procedures we should communicate to our customers in these scenarios?

3. Maintenance and Disaster Recovery:

   • Are there specific steps or best practices customers should follow during routine maintenance, hardware upgrades, or disaster recovery situations to prevent license issues?

Additionally, we are planning a software upgrade incorporating your ALPR solution, and some licensing-related issues have arisen. Could you help us resolve this situation with the customer, or advise us on the best way to communicate this to them?

Your guidance on these topics will help us strategically advise customers and avoid unnecessary disruptions.

Thanks again for your help!✌️

Best regards, 

Tilen

--
You received this message because you are subscribed to the Google Groups "doubango-ai" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doubango-ai...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/doubango-ai/5025d307-0ba0-4d63-b231-611c725d11b0n%40googlegroups.com.