PTZ 3D Positioning

Today

July 06, 2026 08:42

Hello, technical staff,

Did you see my question?

Thank you.

Version: 6.1.2.42921

0

Norman

Network Optix team

July 06, 2026 12:29

Hi Today,

To help point you in the right direction, please note that for any urgent or time-sensitive questions, your Authorized Reseller is always your best and fastest resource. While we love having you here, this forum is primarily a peer-to-peer community driven by fellow users, with the Nx Staff mainly stepping in for moderation.

To make sure your post gets the right visibility, I am going to move this topic over to the correct section. Placing it in the appropriate category helps ensure you get a more accurate and timely response from community members who specialize in this area.

Regarding your question: I assume that by "3D PTZ," you are referring to what we call Advanced PTZ in our system.

Here are a few resources to help you get this sorted out:

How to use it: For step-by-step instructions on operating these controls, please refer to THIS section of our user manual.
Troubleshooting: If your camera doesn't seem to support these features out of the box, check out THIS support article which explains the specific requirements needed to enable Advanced PTZ controls.

Best regards.

0

Today

July 07, 2026 01:29

Hello, NX Technical Team

I saw in https://support.networkoptix.com/hc/en-us/articles/1500008438961-How-to-prepare-PTZ-cameras-for-Advanced-PTZ-calibration that the device requires absolute move support, and a colleague has calibrated the pan/tilt unit. They provided a resource_data.json file, which I compared and found to be consistent with the resource_data.json file in the 6.1.2.42921 installation directory. Is the problem due to an incorrect configuration file provided by them, or do I need to perform any additional configuration?

0

Norman

Network Optix team

July 07, 2026 07:24

Hi Today,

To confirm whether the resource_data.json file has been successfully applied, please check the version number reported by the VMS. You can do this by following the steps below:

Open a web browser and go to the WebAdmin interface at:
https://<serverIp>:7001
(replace <serverIp> with the actual IP address of your server)
After logging in, open a new browser tab and navigate to the following endpoint:
https://<serverIp>:7001/rest/v3/system/resourceData
Depending on your browser, a large block of text may be displayed; this is expected. Simply scroll to the bottom of the output.
Locate and share the version number displayed there.

This information will confirm if the update has been applied correctly.

Once you collected the information, please share it with our authorized reseller who provided the file, and they can investigate the issue or escalate it to the Nx Support Team.

With kind regards.

0

Today

July 07, 2026 07:32

Hello, NX Development Team

I requested https://192.168.17.136:7001/rest/v3/system/resourceData and the version I see is "version":"6.1.0.677".

0

Norman

Network Optix team

July 07, 2026 08:21

Hi Today,

Please share this information with your authorized reseller, so they can figure out why it doesn't work. The default version for Nx Witness 6.1.2.42921, should be 6.0.0.669, so the version you mention, 6.1.0.677, should work. However, I have doubts a file with this version was provided by the Nx Support team, so there might be errors in the file.

With kind regards.

0

Today

July 07, 2026 09:45

Hello, NX Development Team

I opened C:\Program Files\Network Optix\Nx Witness\MediaServer\resource_data.json and found that the version is "version": "6.0.0.670". However, the request to https://192.168.17.136:7001/rest/v3/system/resourceData returned "version": "6.1.0.677". Is this correct? Where does this HTTP request value come from?

0

Norman

Network Optix team

July 07, 2026 12:23 Edited

Hi Today

This value comes from a previous resource_data.json file, and also explains why the fix wasn't applied. The VMS always uses the resource_data.json file with the highest number, and ignored all others.

Because this issue requires a deeper dive into your specific setup, we highly recommend reaching out to your Authorized Reseller as soon as possible. They need to remove the 6.1.0.677 version from your Site database, so the 6.0.0.670 file will be applied.

Best regards.

0

Today

July 08, 2026 01:59

Hello, NX Development Team

I opened C:\Program Files\Network Optix\Nx Witness\MediaServer\resource_data.json and couldn't find the value "version": "6.1.0.677". How can I find this file?

I've provided a problem report for the resource_data.json file: https://support.networkoptix.com/hc/en-us/requests/50427 Could you please check if there's a problem with the provided file?

0

Norman

Network Optix team

July 08, 2026 08:02

Hi Today,

The file is fine. As said, you previously had a file with version 6.1.0.677, so the new file won't be applied, since the version number is lower.

As said, we highly recommend reaching out to your Authorized Reseller as soon as possible. They need to remove the 6.1.0.677 version from your Site database, so the 6.0.0.670 file will be applied.

Alternatively, you can change the version in the resource_data.json file that was provide to 6.1.0.678, and restart the Media Server, and you'll notice the file will be used.

That said, we do not recommend to use files with such high version numbers, since it will prevent you from receiving numerous future updates to the resource file.

Best regards.

0

Today

July 08, 2026 08:55

Hello, NX development team.
I'd like to know how to specifically locate version 6.1.0.677. I checked the installation directory and the file is 6.0.0.670. Regarding your mention of deleting it from the website database, how do I do that?

0

Norman

Network Optix team

July 08, 2026 12:43 Edited

Hi Today,

The files was in the exact same file path as the resource_data.json file used for version 6.0.0.670. However, when you saved the 6.0.0.670 resource_data.json file to that location, it overwrote and replaced the existing 6.1.0.677 resource_data.json file.

For guidance on deleting it from the database, please contact your reseller.

Best regards.

0

Today

July 09, 2026 01:15

Hello, NX development team. I am a device manufacturer without distributors, and we would like to integrate this feature. What should I do, and what do I need to provide?

0

Norman

Network Optix team

July 09, 2026 07:26

Hi Today,

In that case, assuming it isn't a production system, just (re)move the ecs.sqlite Site database file and restart the Media Server application. Then the system will be defaulted, and the resource_data.json file you added to the specific directory will be applied.

Best regards.

0

Today

July 10, 2026 00:55

Hello, NX Development Team

I deleted several `.sqlite` files in the `C:\Windows\System32\config\systemprofile\AppData\Local\Network Optix\Network Optix Media Server` directory, but the HTTP request still returns "version":"6.1.0.677". This problem persists. How can I calibrate the pan-tilt position myself to use advanced pan-tilt features?

0

Norman

Network Optix team

July 10, 2026 07:06

Hi Today,

Please tell me, if you removed the ecs.sqlite, and restarted the Media Server, were you prompted to setup a new System?

You can't calibrate the Advanced PTZ option yourself.

If the issue remains, you can, since you mentioned you're a device manufacturer, sign up for direct support via THIS link, and we can remote in to you Server and assist. Or if you want a quick fix; add version number 6.1.0.678 to the resource_data.json file and restart the Media Server.

With kind regards.

0

Today

July 10, 2026 07:32

Hello, NX Development Team

I tried manually changing the version in my resource_data.json to "version": "6.1.0.680"

Then I modified the following:

{
            "keys": [
                "IPCamera|SN-IPS*"
            ],
            "ptzMapper": {
                "fromCamera": {
                    "x": {
                        "extrapolationMode": "PeriodicExtrapolation",
                        "device":  [ -1, -0.5,  0, 0.5,  1],
                        "logical": [ 0, 90, 180, 270, 360]
                    },
                    "y": {
                        "extrapolationMode": "ConstantExtrapolation",
                        "device":  [  -1, 0,   1],
                        "logical": [ -15, 37.5, 90]
                    },
                    "z": {
                        "extrapolationMode": "ConstantExtrapolation",
                        "device":  [-1, -0.9, -0.8, -0.7, -0.6, -0.5, -0.4, -0.3, -0.2, -0.1, 0, 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1],
                        "logical": [1, 1.526315789, 2.131578947, 2.789473684, 3.289473684, 3.921052632, 4.526315789, 5.078947368, 5.631578947, 6.184210526, 6.789473684, 7.368421053, 7.947368421, 8.631578947, 9.289473684, 9.894736842, 10.47368421, 11.02631579, 11.57894737, 12.02631579, 12.71052632],
                        "logicalMultiplier": 90.1,
                        "space": "35MmEquiv"
                    }
                }
            }
        }

After restarting the server, the advanced features are available. I have a few questions:

After sending the device to the customer, do I have to have them manually replace this file? Can I have them only replace the plugin?
Is the right side the manufacturer's name?
Are there any specifications for the parameters of this JSON object? Some of my clients require customization and may need to modify certain parameters.

0

Norman

Network Optix team

July 10, 2026 08:17

Hi Today

Allow me to respond per number:

The fix, as provided in ticket #50427, will be part of the 6.1.3 release. If the customer uses the current release, they need to use the file with version 6.0.0.670. Please, do not share files with different numbers, since they might cause issues in the future.
In "IPCamera|SN-IPS*", IPCamera is the Vendor name, and SN-IPS* the Model name. Typically, we do not accept generic names, like IPCamera, since other manufacturers use the same generic name as well, and could cause conflicts.
The fix that was provided, and that will be part of the release was for model SN-IPS8655YDR-Z18*. For any other model, mapping needs to be redone to adhere minimal standards.

The modification you made is too generic, and possibly will affect the accuracy of the mapping, and won't make it into production.

0

PTZ 3D Positioning

Comments

Didn't find what you were looking for?