Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.

Log in or register to post/reply in the forum.

Time Slicing Conflict

Otemohu Dec 7, 2017 01:55 AM

Hi all,

I have an issue with my CRBasic program.
Here is the context: I have a condition statement to create two Tablefile name with the Outstat variables on the USR drive (fixed at ~1Mb). The tablefiles have two diffrent scan interval. The Table file renaming condition appears at the end of each slowsequence instruction.
I wanted first to create a sub routine and call the number of each table but I did not succeed. I was unable to add a number as a vraible in the table name.

So I copied twice the file renaming condition with Outstat1 and Outstat2, Filerenmae1 and Filerename 2 variables, .... but at the compilation, I have now this message:
line 324: Warning: Time Slicing Conflict in Slow Seq 2, Scan 1, with Main Sequence Scan 1.


Otemohu Dec 7, 2017 05:23 AM

It has been resolved. I don't know how but I came back to the latest working program and compared with the new one. A variable was never called in the program. I nevertheless don't understand how this 'time slice" message appeared.

ArtHeers Jan 4, 2018 12:47 PM

This "time slicing" warning occurs if there is not enough time to "slice" in a slow sequence scan of measurements along with the measurements for the scan in the main sequence.  In this example, both scans are meant to be once per second and there is simply not enough time to do all the measurements in both scans in one second.  If the scan in the slow sequence was 2 instead of 1 second, then perhaps they could be sliced into the main scan, some in the first main scan  and the remaining in the second main second.

Log in or register to post/reply in the forum.