Data expected behavior on SAVE_DATA and RESTORE_DATA depending the Unity Pro version.
>>Official expected behavior:
Unlocated and located data have the same behavior and It is possible to do a SAVE_DATA even if there are data forced.
Will be implemented on Unity Pro V13.1
NOTA: No Red Forced Bit status in status Bar
>> Behavior with Unity Pro V12.0 and V13.0
To solve an issue reported on Up V11.1 it was decided do not save data with forced bit.
(*) Red Forced Bit status in status Bar (not expected, value being not forced)
>>Behavior with Unity Pro V11.1 and previous version.
(1) Red Forced Bit status in status Bar (not expected, value being not forced), can be change on INIT
(2) No Red Forced Bit status in status Bar (not expected, value being forced), can be changing the item from unforced to Forced.
NOTA: Possibility to force unlocated data is possible since Unity Pro V8.0 and M580 offer.
NOTA: Working with Unity Pro in simulation mode doesn’t allow to force unlocated data.
Unlocated and located data have the same behavior and It is possible to do a SAVE_DATA even if there are data forced.
Will be implemented on Unity Pro V13.1
| Variable | Value when “Save Data” | Values just before “Restore Data” | Expected Value after “Restore Data” | Comments |
| MyM100 | 0 | 1 | 0 | Value SAVE |
| MyM101 | 0 | F1 | F1 | Forced status before RESTORE |
| MyUnloc1 | 0 | 1 | 0 | Value SAVE |
| MyUnloc2 | 0 | F1 | F1 | Forced status before RESTORE |
| MyM100 | F1 | 0 | 1 | Value SAVE but unforced |
| MyM101 | F1 | F0 | F0 | Forced status before RESTORE |
| MyUnloc1 | F1 | 0 | 1 | Value SAVE but unforced |
| MyUnloc2 | F1 | F0 | F0 | Forced status before RESTORE |
>> Behavior with Unity Pro V12.0 and V13.0
To solve an issue reported on Up V11.1 it was decided do not save data with forced bit.
| Variable | Value when “Save Data” | Values just before “Restore Data” | Values just after “Restore Data” | Comments |
| MyM100 | 0 | 1 | 0 | Value SAVE |
| MyM101 | 0 | F1 | F1 | Value before RESTORE |
| MyUnloc1 | 0 | 1 | 0 | Value SAVE |
| MyUnloc2 | 0 | F1 | 0 | Value SAVE (*) |
| MyM100 | 1 | |||
| MyM101 | F1 | |||
| MyUnloc1 | 1 | |||
| MyUnloc2 | F1 |
>>Behavior with Unity Pro V11.1 and previous version.
| Variable | Value when “Save Data” | Values just before “Restore Data” | Values just after “Restore Data” | Comments |
| MyM100 | 0 | 1 | 0 | Value SAVE |
| MyM101 | 0 | F1 | F1 | Value before RESTORE |
| MyUnloc1 | 0 | 1 | 0 | Value SAVE |
| MyUnloc2 | 0 | F1 | 0 | Value SAVE (1) |
| MyM100 | F1 | 0 | 1 | Value SAVE |
| MyM101 | F1 | F0 | F0 | Value before RESTORE |
| MyUnloc1 | F1 | 0 | F1 | Value SAVE (2) |
| MyUnloc2 | F1 | F0 | F1 | Value SAVE |
(2) No Red Forced Bit status in status Bar (not expected, value being forced), can be changing the item from unforced to Forced.
NOTA: Possibility to force unlocated data is possible since Unity Pro V8.0 and M580 offer.
NOTA: Working with Unity Pro in simulation mode doesn’t allow to force unlocated data.
게시 대상: 슈나이더 일렉트릭 Korea
도움이 필요하신가요?
제품 선택기
애플리케이션에 적합한 제품과 액세서리를 빠르고 쉽게 찾을 수 있습니다.
견적 받기
영업 관련하여 온라인으로 문의하시면 전문가가 연락드립니다.
구매처
해당 지역의 가장 가까운 슈나이더 일렉트릭 대리점을 쉽게 찾을 수 있습니다.
지원 센터
한 곳에서 모든 요구 사항에 대한 지원 리소스를 찾아보십시오.