Hi,
Not AFAIK; most of the description about Interrupts (e.g. in the Programming Manual Appendices) applies primarily to X2s.
The SERVO command and the time variable use the
same (20 ms) timer (T1), so if the Servo pulses are "good" then so should be the time variable.
Basically, the "time" variable is obtained by a system interrupt routine dividing the Servo timer by 50 (sadly this prescaler value is not accessible to the program-writer). The 20ms preload is also interrupt-driven, so when interrupts are disabled then both the 20ms period and subsequently the "time" prescaler may be corrupted (i.e. delayed). Note that the 20 ms timer continues to run whether "time" is ENABLEd or DISABLEd. You can read the T1 value by using PEEKSFR commands (it normally increments at 1 MHz from 45536 to 65535 and then overflows to generate the system interrupt).
I believe the main commands which disable interrupts are the serial communications, i.e. SERIN , SEROUT , SERTXD and DEBUG , because they use bit-banging to time the data. Apparently PULSIN , PULSOUT and COUNT do NOT disable these system interrupts, so it is their values which become corrupted if there is a conflict.
There may be other commands which disable interrupts, but you may find the text and Logic Analyser waveforms (including corruption of the Servo Pulses) of relevance
HERE.
Cheers, Alan.