https://magos.freshdesk.com/a/tickets/11716

Firmware: 25.01.00_20250923_R442

 

Issue Description:
When sending the camera to any AbsoluteMove position—pan, tilt, or zoom—the returned position in the GetStatus response is incorrect and does not match the commanded value.
As shown in the screenshot below, I sent the camera to a pan value of 0. The camera physically moved to the correct position, but the reported value in the GetStatus response was 0.017999, which is significantly different from the expected value.

Notes:
  • The mismatch between the AbsoluteMove command values and the GetStatus response occurs across the entire pan/tilt/zoom range.
  • We are able to work with such discrepancies only when the response curve is linear—meaning we can expect the min/max values per angle. However, in this case the deviation is non-linear and inconsistent, making such impossible.
  • Based on my experience, I have encountered similar behavior in a small number of other cameras, and it has been a firmware-related issue—typically resolved by the manufacturer with an update once their R&D team is involved. The root cause is usually incorrect internal mapping of the position values. 
Below are several screenshots from my tests. In each case I sent the camera to various pan, tilt, and zoom positions using AbsoluteMove, then retrieved the reported position using GetStatus.
  • Green: AbsoluteMove target value
  • Red: GetStatus reported value
Pan
Tilt
Zoom