how can you use time/clock in pac machine edition/rx3i?

[Andor]

Rung 5, the source at IN1 of the AND instruction should be Time_reader(4), not Time_reader(3). Also you need to multiply the result of the AND by 256 to move it to the upper 8 bits.

Oke thank you. I will try tomorrow.

I cannot edit old posts in this forum. see no edit button

 

[Steve Bailey]

There is a time limit on the ability to edit.

And here's an one-rung method to reverse the upper and lower words. This works in this case because the hour and minute are in the same word when you select BCD - 4-digit year for the returned data from the SVC_REQ.

 

[Andor]

Rung 5, the source at IN1 of the AND instruction should be Time_reader(4), not Time_reader(3). Also you need to multiply the result of the AND by 256 to move it to the upper 8 bits.

I tried it but that doesn't work either. the minutes are not correct now either.

 

[Andor]

There is a time limit on the ability to edit.

And here's an one-rung method to reverse the upper and lower words. This works in this case because the hour and minute are in the same word when you select BCD - 4-digit year for the returned data from the SVC_REQ.

Yes! Thnx. this works immediately.

 

[Steve Bailey]

The screen captures are confusing. The result of 8192 in %R0707 equates to 2000 in BCD, but that value is not the result of ANDing 4096 with 16#FF. The result of 19 in %R0707 equates to 13 in BCD, but that isn't the result of ANDing 4096 with 16#FF00. Also rung 7 doesn't appear to be active at the time of the screen grab. Is this logic in a subroutine?

 

[Andor]

The screen captures are confusing. The result of 8192 in %R0707 equates to 2000 in BCD, but that value is not the result of ANDing 4096 with 16#FF. The result of 19 in %R0707 equates to 13 in BCD, but that isn't the result of ANDing 4096 with 16#FF00. Also rung 7 doesn't appear to be active at the time of the screen grab. Is this logic in a subroutine?

I did the ror_word and the bcd to int. that works perfectly the way I want it. regarding your question above. no idea. could it possibly be done by the length of OR word? the outcome with the rx3i from OR_word was always a maximum of two digits. With the 90-30 there was no bite length in the or word function. With the RX3i I see that the length can be specified.