Two text screens used for debugging my E2 which is seen on the plate.
The left screen is a number that represents the current interval ms delay. It is adjusted based upon the op usage of the e2.
The right screen displays a piece of code that generates a unique random ID and adds it to one of the main arrays. The "365" is the location within the array and the "1.7.2.75" is the random ID. On occasions a duplicate ID is created and needs to be check with all current IDs. To do this I used a while loop that scans through each array location and checks if it matches. This is quite consuming on resources so I implemented a limit of 200 locations for the array. The dynamic interval delay obviously helps in dealing with the op usage of the e2 but so far there seems to be a limit where the while statement consume all of the available quota so I'm trying to find ways I can deal with this (such as using incremented IDs instead of random ones).
Oh and the purpose of all this is for a E2 network of cool machines that can be controlled.
If the screenshot doesn't display:
http://cloud-2.steampowered.com/ugc/576716022863070425/FD44E79DF8F0B6CA472130938F39E1556B824DB7/
