k6ccc Posted October 16, 2018 Share Posted October 16, 2018 (edited) I have found a situation where entering a Windows command on one sequence causes that same change to take place on multiple sequences. Let me explain in more detail. For my year round landscape lighting, the evening startup sequence includes a Windows command that executes a batch file. The batch file in turn writes two log entries, and sends me an E-Mail that tells me that the show has started and which computer is running the show (my server runs the lights from January through mid October and a dedicated show computer runs is for Halloween and Christmas). As far as LOR is concerned, it's just executing a batch file. A couple weeks ago I created new landscaping sequences and shows for Fallen Firefighters memorial week. For each sequence, I took the existing landscape sequence and edited it to become largely red lights and saved them with new file names. I also created new batch files, and set the new sequences that have Windows commands to point to the appropriate batch file. That worked perfectly. However when Fallen Firefighters memorial week ended and I went back to the "normal" landscape lighting show and sequences, I noticed that the startup log files and E-Mails were still showing that the Fire memorial shows were starting. So last night I finally had time to investigate and found that If I edited the Windows command for the Fire memorial startup sequence, it also affected the Year round landscape startup sequence and vise versa. Same thing with the two transition sequences from the evening show to the overnight shows that also have Windows commands. I assume it is somehow related to the fact that I edited the started sequence and saved it with a new name as opposed to creating new sequences from scratch. I assume that I could clear the problem by simply deleting the cmdmap.lcm file and starting over, but I would rather not do that if I don't have to as there are dozens of entries in that file. Any ideas? Edited October 16, 2018 by k6ccc Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now