Sean Meighan
Welcome => Do You Need Help? Post it here => Topic started by: feeleyfam on November 29, 2019, 02:57:56 PM
-
I am trying to find out why xschedule does not want to output to my LOR Comm Port. Can't find a setting or anything specific in xSchedule that might prevent this. My Alphapix is running fine. Attached is the log file which shows the warning. If anyone can help me with this, I'd appreciate it.
Jim
-
Could it be you have lor running somewhere on the machine or xlights running with it open. Windows only allows one process access to the comm port at a time.
-
I have verified that neither is running it. I have double checked that xlights still outputs to my LOR comm port and we are good there. I even shut down xlights afterwards. I see the lights solid on the controllers so something is getting to them.
-
Reboot.
-
No Luck. Still othing to my LOR Comm Port. Still getting that same warning on my attachment.
-
Problem solved. I updated to .67 and it corrected the comm port problem. I was on .64. I appreciate your help Keith. I’m still working out a few bugs because of my Pixie controllers but at least I can run a show with xLights.
-
Pixie controllers will give you grief until you offload them onto some other poor sap.
-
Funny you say that because I have a falcon F16 arriving Wednesday and am about to place an order for lights to move my lor stuff to it. Gonna have a busy week converting all that over. I definitely wished I would’ve started off with xlights!