Hanwha-Techwin
On this page
Introduction
GCXONE integrates with Hanwha Vision cameras using SUNAPI for device discovery and event/device integration. Once the device is added, the camera stream is used by the GCXONE Video Viewer for live monitoring. Events generated by the Hanwha device are received by GCXONE and displayed in Video Search.
Prerequisites
- The Hanwha Vision camera is powered on and reachable from the GCXONE environment.
- The camera IP address is known and stable/reserved.
- Valid camera administrator credentials are available.
- Required HTTP/HTTPS, RTSP and SUNAPI discovery/integration traffic is permitted by the network/firewall.
- The camera firmware supports the SUNAPI features required by the GCXONE integration.
- The camera time/date is correct and synchronized where possible; correct timestamps are important for event search and correlation.
- For motion/analytics events, the camera is mounted so that the desired people/object movement area is visible.
Hanwha-Techwin Configuration
Event configuration is performed on the Hanwha Vision camera. The exact menu names vary by camera model and firmware. Some P Series and X-Core/Plus models use Event rule setup, while other models can still use Event setup.
Enable the Event/Analytics Source
Step 1: Log in to the Hanwha Vision camera using its web interface.
Step 2: Open Setup.
Step 3: Go to Event / Analytics according to the camera model (for example, Event > Event setup), and select the channel (for example, CH 1).
Step 4: For motion events, enable Motion detection and configure the required detection area.
Step 5: For AI/IVA events, enable the required analytic and configure the virtual line/area/object type as supported by the camera.
Step 6: Apply/save the settings.
The motion-detection workflow is: enable motion detection, select a detection area, draw the required area on the camera view, and apply the configuration.
Configure the Event Rule
For cameras that have Event rule setup, create an event rule that has the required trigger and event action. A typical validation rule is a Motion detection rule enabled for the required schedule.
Step 1: Navigate to Setup > Event > Event rule setup.
Step 2: Select Add to create a rule.
Step 3: Enter a clear Rule name, for example NXGEN_Motion_Test.
Step 4: Select the channel.
Step 5: Under Event trigger, select Motion detection, IVA, Object Detection, Virtual Line, Virtual Area, or the required event trigger supported by the camera.
Step 6: Enable the rule and select the required Schedule.
Step 7: Under Event action, configure the event action required by the device/recording workflow.
Step 8: Save/apply the rule.
Step 9: Generate a real test event in front of the camera.



This is a reference illustration; Hanwha UI fields vary by model and firmware.
The Event rule setup page shows the enabled Motion rule with its event trigger and event action columns.
Make Events Available in Hanwha Search
The following sequence is recommended when camera events must be visible in the Hanwha Vision Search interface.
Step 1: Enable the analytic/event source: enable Motion detection, IVA, object detection, virtual line/area, or the required analytic on the camera.
Step 2: Define the detection area: draw the detection zone over the actual people/object movement area. Avoid pointing the camera at an empty wall or irrelevant background.
Step 3: Create/enable the event rule: under Event rule setup, enable the corresponding trigger and save the rule.
Step 4: Configure the recording/event schedule: where the model requires it for event recording/search, configure the recording schedule to include Event or Event/Continuous.
Step 5: Generate a test event: walk/move through the configured detection zone and wait for the camera to register the event.
Step 6: Confirm the camera-side event: use the camera's Live/Event indicators or logs, where available, to verify that the event was generated.
Step 7: Verify Search: open the Hanwha Vision Search interface, select the appropriate channel/time range/event filter, and confirm the generated event is returned.

Step 8: Validate in GCXONE: after the same event is generated, confirm the corresponding event is received and displayed in Video Search (see Validate Events in GCXONE).
The complete sequence is: enable the required motion detection, define the detection area, configure the recording/event behavior, and then enable the Motion rule in Event rule setup.

Hanwha-Techwin Config Guide with GCXONE
Add the Device
Step 1: In GCXONE, go to Configuration and open the customer and site where the camera will be added.
Step 2: Open the Devices tab and click Add New. The Add Device dialog opens.
Step 3: In the Device dropdown, select Hanwha-Techwin.
Step 4: Enter a Name for the device and, if required, select an entity group in Select Entity Group.
Step 5: Under Connection Settings, enter the IP Address Or Host Name, Serial Number, User Name, Password, Control Port, RTSP Port, Server Port and HTTPS Port. The port values must match the camera configuration.
Step 6: Select the Timezone (required). Adjust Enable Audio, Device Configuration, Advanced Settings and Location if needed, and confirm the mandatory fields are populated.
Step 7: Select Discover. GCXONE validates the device and retrieves the supported device/channel information.
Step 8: After successful discovery, click Save to save the device.
Step 9: Confirm the device is listed under the customer site in the Devices tab.
Validate the Live Stream
After the device is saved, the camera is available in the GCXONE device tree.
Step 1: Open the Video Viewer.
Step 2: In Device Explorer, on the Devices tab, locate the newly added Hanwha Vision device.
Step 3: Drag and drop the device/channel onto the video viewing grid, or double-click it in the device tree.
Step 4: Wait for the live stream to initialize.
Step 5: Verify that live video is visible and the stream remains stable for several minutes.
Validate Events in GCXONE
Once the camera is configured and producing events, validate the complete event path.
Step 1: Trigger the configured event at the camera.
Step 2: Confirm the event is generated by the Hanwha device.
Step 3: Confirm GCXONE receives the event through the Hanwha-Techwin (SUNAPI) integration.
Step 4: Confirm the event is mapped to the correct device/channel in GCXONE.
Step 5: Open Video Search and verify the event appears.
Step 6: Compare the event timestamp with the camera timestamp and the Video Search timestamp.
Step 7: Repeat with at least two or three events to verify consistency rather than a single successful trigger.
Troubleshooting
Symptom | Likely checks | Action |
|---|---|---|
Discover fails | IP reachability; credentials; SUNAPI discovery traffic; HTTP/HTTPS port | Verify the network path and the camera web login; verify the configured ports and firewall rules. |
Device saves but the stream is blank | RTSP port; stream profile; codec; credentials; network | Validate RTSP reachability and the camera stream settings; try a supported H.264 profile if the player has codec limitations. |
Stream works but no events in Video Search | Event source disabled or wrong channel/event mapping | Verify camera event generation first; then validate GCXONE event reception/mapping. |
Event is not in Hanwha Search | Event rule; detection area; schedule; recording configuration | Verify the event is actually generated; verify the correct channel/time range is selected; verify event/recording configuration is enabled where required. |
Events have wrong timestamps | Camera/GCXONE time mismatch | Synchronize the camera and server time/NTP and repeat the test. |
Frequent false events | Detection zone/sensitivity too broad | Reduce the detection area; adjust sensitivity/minimum duration; retest. |
Network and Protocol Notes
Hanwha Vision lists SUNAPI Discovery as UDP 7701 and documents HTTP/HTTPS web communication. Exact ports can vary by device role/model and configuration, so the values shown in GCXONE must match the camera configuration rather than relying on a universal default.
Important: The RTSP port must be the value configured/supported by the specific camera. Do not assume the port from a different Hanwha device or recorder model.
Thank you — your feedback goes to the team that owns this page.