...
[Minimum object compliancy test]
[Minimum object compliancy test]Starting Test : Minimum object compliancy test
[Minimum object compliancy test]
[Minimum object compliancy test] Testing mandatory manager(s) for test device
[Minimum object compliancy test] Testing 1 mandatory manager(s) for compliancy
[Minimum object compliancy test]Testing mandatory object(s) for test device
[Minimum object compliancy test]ERROR: Missing mandatory object OcaControlNetwork
[Minimum object compliancy test] Testing 8 mandatory object(s) for compliancy
[Minimum object compliancy test]ERROR: Failed to test objects
[Minimum object compliancy test]Test Minimum object compliancy test is now unsuccesfull
[Minimum object compliancy test]
[OCC Object Compliancy Tests]
[OCC Object Compliancy Tests]Starting Test : OCC Object Compliancy Tests
[OCC Object Compliancy Tests]
[OCC Object Compliancy Tests] Testing 4 manager(s) for test device
[OCC Object Compliancy Tests] Testing 203 object(s) for test device
[OCC Object Compliancy Tests]WARNING: Object OcaNetwork (ONo=9000) is deprecated! (ClassID 1.2.1. Class version 2)
[OCC Object Compliancy Tests]Test OCC Object Compliancy Tests is now successfull
[OCC Object Compliancy Tests]
...
My understanding from the previous issues' dicussion ist, that micro OCA uses an old way to handle control messages and therefore does not provide this object.
Another indicatino would be the Warning about deprecation.
So can we say that MicroOCA is still fully functional and just does it in an old-fashioned way?
Are there any issues to be expected when using the device with a recent Oca Controller? Or is alle funcitonality provided fully backward compatible?
Are there any plans to update MicroOCA to the new standard? Or any good reasons to do so?
Hello!
in issue #8 the compliance test for MicroOCA was addressed and most issues were resolved.
Testing against the latest SW now will only result in one error:
call: Aes70CompliancyTestTool.exe -d "name" -s tcp -v AES70-2018
... [Minimum object compliancy test] [Minimum object compliancy test]Starting Test : Minimum object compliancy test [Minimum object compliancy test] [Minimum object compliancy test] Testing mandatory manager(s) for test device [Minimum object compliancy test] Testing 1 mandatory manager(s) for compliancy [Minimum object compliancy test]Testing mandatory object(s) for test device [Minimum object compliancy test]ERROR: Missing mandatory object OcaControlNetwork [Minimum object compliancy test] Testing 8 mandatory object(s) for compliancy [Minimum object compliancy test]ERROR: Failed to test objects [Minimum object compliancy test]Test Minimum object compliancy test is now unsuccesfull [Minimum object compliancy test] [OCC Object Compliancy Tests] [OCC Object Compliancy Tests]Starting Test : OCC Object Compliancy Tests [OCC Object Compliancy Tests] [OCC Object Compliancy Tests] Testing 4 manager(s) for test device [OCC Object Compliancy Tests] Testing 203 object(s) for test device [OCC Object Compliancy Tests]WARNING: Object OcaNetwork (ONo=9000) is deprecated! (ClassID 1.2.1. Class version 2) [OCC Object Compliancy Tests]Test OCC Object Compliancy Tests is now successfull [OCC Object Compliancy Tests] ...
My understanding from the previous issues' dicussion ist, that micro OCA uses an old way to handle control messages and therefore does not provide this object. Another indicatino would be the Warning about deprecation.
So can we say that MicroOCA is still fully functional and just does it in an old-fashioned way? Are there any issues to be expected when using the device with a recent Oca Controller? Or is alle funcitonality provided fully backward compatible?
Are there any plans to update MicroOCA to the new standard? Or any good reasons to do so?
Best regards,
Sebastian