Com error in schedu...
 
Notifications
Clear all

Com error in scheduler

22 Posts
5 Users
0 Reactions
4,254 Views
Posts: 290
Topic starter
(@jeeves55)
Reputable Member
Joined: 19 years ago
[#1702]

This has happened pretty much every night.
The scheduler is set to turn my program on at 4:30.
But every night, at 4:30 is says there is a conflict with the com port, and does not start. If I say OK to the error, which closes it, and then select restart timers. It starts right up no problem.

I am using this version of Vixen, with the renard modified dimmer.
There is nothing else being used with the computer or vixen. There is not another thing scheduled with the scheduler.
Anyone else have this problem?


21 Replies
Mudsculpter
Posts: 1220
Admin
(@mudsculpter)
Member
Joined: 19 years ago

Yes I have. But my experiences are more random. I have been in touch with KC about it and he is taking a look at some files that I have sent.

Are you running a background script? If so, when you compiled it did you select "hold port open..." in the port settings?


Reply
Posts: 290
Topic starter
(@jeeves55)
Reputable Member
Joined: 19 years ago

No, I am not running a background script.


Reply
Mudsculpter
Posts: 1220
Admin
(@mudsculpter)
Member
Joined: 19 years ago

Are you using a usb to serial converter device


Reply
Posts: 161
(@greenmeanie)
Estimable Member
Joined: 19 years ago

I have the same problem.


Reply
Posts: 290
Topic starter
(@jeeves55)
Reputable Member
Joined: 19 years ago

Actually I think it was because I wasn't running a background sequence. i came laste last night, after the show was off, and found my sign light was still on. That would cause a port com error, I am sure. I used my background sequence from last year, and hopefully it will work fine now.


Reply
Posts: 161
(@greenmeanie)
Estimable Member
Joined: 19 years ago

Mine goes off without one.
I had two good nights doing this.
I boot up the computer and then vixen. I then plug in the usb to serial. If I leave it plugged in on boot it gives me a COM error. I will let you know if I have another bad night doing this.


Reply
Mudsculpter
Posts: 1220
Admin
(@mudsculpter)
Member
Joined: 19 years ago

I have replaced my usb to serial converters to a dual port serial pci card. Results have been great so far. I have been error free for 21 hours. It's the first time that vixen has run all night without an error. Cant wait until 5:30pm when the show is supposed to start to see if an error happens.

<>

http://www.newegg.com/Product/Product.aspx?Item=N82E16815166004


Reply
Posts: 290
Topic starter
(@jeeves55)
Reputable Member
Joined: 19 years ago

Well I am unhappy to announce that the problem i was having, whatever it is, was not fixed.

Today, the show started on time. At approx 10 after 10, the wife and I were watching uit through the front window, then suddenly, everything went dark. Ran to the computer, and it was the com error again! WTF??

This is judging week for the Christmas light contest, and apparently I have to be here the whole time it's on to make sure it stay's on. Today was an office Christmas party, I had to have one of my friends drive by the house at the scheduled start time to make sure it was on. But if it's going to randomly shut off, then I need to be here all the time. I told the wife I've got to ditch her family Christmas Thursday to watch this, she is less than pleased.

So anyone else offer up any suggestions?


Reply
Macrosill
Posts: 9739
(@macrosill)
Member
Joined: 20 years ago

May be a silly question at this point but do you "Hold the port open"? I continually got Com errors in all intervals from 3 minutes to 4 hours on the 1st night. Once I did a fresh Vixen install, switched to the modified Renard plugin, Hold to port open and created each sequence over in the fresh install I have not had an issue since, and it has been about 3 weeks now. I think I only restarted the pc once.

To re-create the sequences I just made a new sequence and then copied and pasted the grid into the new sequence. I am really not sure which one of these fixed the error but I would assume it was holding the port open since that is the only one directly related to the com port. I kept getting the error with the modified plugin and not holding the port open.

Good luck,


Reply
Page 1 / 3
Share: