Jump to content
Light-O-Rama Forums

Bug Report - CP refuses to disconnect COM when requested (Resolved)


dgrant

Recommended Posts

I saw this in 6.0.0 and now in 6.0.2, both have the same issue. When the HU requests the CP to disconnect from the Com port, it states the request was sent and to refresh. Fact, it does not disconnect.

Link to comment
Share on other sites

I've tried on several computers, but cannot duplicate. After I click "Yes" to have the Hardware Utility tell the Control Panel to stop using the port, the port gets a red status in the Control Panel. Then I am able to refresh in the Hardware Utility. When I exit the Hardware Utility, the port status goes back to green in the Control Panel. This is what I see in the Network Log:

7/6/2022 15:30:55   Listener INFO Listening on 127.0.0.1:8837
7/6/2022 15:30:55   LOR-Aux A INFO COM5 opened as Aux A with speed 500K
7/6/2022 15:30:55   LOR-Reg INFO COM8 opened as Regular with speed 57.6K
7/6/2022 15:31:06   Listener INFO Connection accepted (127.0.0.1:9487)
7/6/2022 15:31:08   ReqHandler INFO Client 127.0.0.1:9487 identified as Hardware Utility
7/6/2022 15:31:13   ReqHandler INFO Client 127.0.0.1:9487 (Hardware Utility) requests control of COM8
7/6/2022 15:31:13   LOR-Reg INFO Temporarily giving up control of comm port COM8
7/6/2022 15:32:07   ReqHandler INFO Client 127.0.0.1:9487 (Hardware Utility) relinquishes control of COM8
7/6/2022 15:32:07   LOR-Reg INFO COM8 opened as Regular with speed 57.6K
7/6/2022 15:32:08   Listener INFO Socket 127.0.0.1:9487 (Hardware Utility), exiting

What does your Network Log look like?

Matt

Link to comment
Share on other sites

Naturally.  Worked when I tested now...

2022-07-06 02:22:30    Listener    INFO    Connection accepted (127.0.0.1:5416)
2022-07-06 02:22:32    ReqHandler    INFO    Client 127.0.0.1:5416 identified as Hardware Utility
2022-07-06 02:22:34    ReqHandler    INFO    Client 127.0.0.1:5416 (Hardware Utility) requests control of COM3
2022-07-06 02:22:34    LOR-Reg    INFO    Temporarily giving up control of comm port COM3
2022-07-06 02:23:35    LOR-Reg    ERROR    Error opening comm port: COM3
2022-07-06 02:24:13    ReqHandler    INFO    Client 127.0.0.1:5416 (Hardware Utility) relinquishes control of COM3
2022-07-06 02:24:13    LOR-Reg    INFO    COM3 opened as Regular with speed 57.6K
2022-07-06 02:24:14    Listener    INFO    Socket 127.0.0.1:5416 (Hardware Utility), exiting
 

 

Link to comment
Share on other sites

On the Networks tab, to the right of where it says "Lighting Networks".  Buttons for "NETWORK LOG", "IMPORT", "EXPORT", "REMOVE", "EDIT", & "ADD".

 

Link to comment
Share on other sites

That explains it. Right now, due to the other issues, I can't even get there. Back to the CP won't load. 😬

Link to comment
Share on other sites

Fixed!!! Turns out, I kept seeing old address information in the ShowScheduleSettings.json file, that were no longer valid. Matt told me they were contained within the older S4/S5 yearsched.lsc and weeksched.lsc files. I deleted those files and sure enough, the Control Panel launched!

Wrong reply, sorry

Edited by dgrant
Link to comment
Share on other sites

  • 3 weeks later...

Rev 6.0.6 Still not working. Note the Com 3 in use. Also, nothing is reported in the Network log when the HU utility is launched from the CP

spacer.png

Link to comment
Share on other sites

Here is the log. At the bottom is the latest startup. Following it, I tried to launch the HU from the CP and capture it here in the log. Nothing appears. From the logs that both Jim and Matt showed, the "ReqHandler INFO" is not happening on this machine. I checked the FTDI driver's and found mine was more advanced than that specified by LOR so I rolled back to the LOR suggested but nothing changed. Now why both of yours show different port#'s than each other's, mine shows the same as Matt's, 8837 but Matt's changed itself to 9487. Where exactly might I identify this port # ? It appears I'm not getting the "Connection Accepted" either.

2022-07-27 4:03:18 PM    Listener    Information    Listening on 127.0.0.1:8837
2022-07-27 4:03:18 PM    DMX Univ 1    Information    E1.31 universe 1 opened on 10.10.10.11:5568
2022-07-27 4:03:18 PM    DMX Univ 2    Information    E1.31 universe 2 opened on 10.10.10.11:5568
2022-07-27 4:03:18 PM    DMX Univ 3    Information    E1.31 universe 3 opened on 10.10.10.11:5568
2022-07-27 4:03:18 PM    DMX Univ 4    Information    E1.31 universe 4 opened on 10.10.10.11:5568
2022-07-27 4:03:18 PM    DMX Univ 5    Information    E1.31 universe 5 opened on 10.10.10.11:5568
2022-07-27 4:03:18 PM    DMX Univ 7    Information    E1.31 universe 7 opened on 10.10.10.10:5568
2022-07-27 4:03:18 PM    DMX Univ 8    Information    E1.31 universe 8 opened on 10.10.10.10:5568
2022-07-27 4:03:18 PM    DMX Univ 9    Information    E1.31 universe 9 opened on 10.10.10.10:5568
2022-07-27 4:03:18 PM    DMX Univ 10    Information    E1.31 universe 10 opened on 10.10.10.10:5568
2022-07-27 4:03:18 PM    DMX Univ 11    Information    E1.31 universe 11 opened on 10.10.10.10:5568
2022-07-27 4:03:18 PM    DMX Univ 12    Information    E1.31 universe 12 opened on 10.10.10.10:5568
2022-07-27 4:03:18 PM    DMX Univ 13    Information    E1.31 universe 13 opened on 10.10.10.10:5568
2022-07-27 4:03:18 PM    DMX Univ 14    Information    E1.31 universe 14 opened on 10.10.10.10:5568
2022-07-27 4:03:18 PM    DMX Univ 15    Information    E1.31 universe 15 opened on 10.10.10.12:5568
2022-07-27 4:03:18 PM    DMX Univ 16    Information    E1.31 universe 16 opened on 10.10.10.12:5568
2022-07-27 4:03:18 PM    DMX Univ 19    Information    E1.31 universe 19 opened on 10.10.10.12:5568
2022-07-27 4:03:18 PM    DMX Univ 20    Information    E1.31 universe 20 opened on 10.10.10.12:5568
2022-07-27 4:03:18 PM    DMX Univ 40    Information    E1.31 universe 40 opened on 10.10.10.13:5568
2022-07-27 4:03:18 PM    DMX Univ 41    Information    E1.31 universe 41 opened on 10.10.10.13:5568
2022-07-27 4:03:18 PM    DMX Univ 42    Information    E1.31 universe 42 opened on 10.10.10.13:5568
2022-07-27 4:03:18 PM    DMX Univ 43    Information    E1.31 universe 43 opened on 10.10.10.13:5568
2022-07-27 4:03:18 PM    DMX Univ 44    Information    E1.31 universe 44 opened on 10.10.10.13:5568
2022-07-27 4:03:18 PM    DMX Univ 45    Information    E1.31 universe 45 opened on 10.10.10.13:5568
2022-07-27 4:03:18 PM    DMX Univ 46    Information    E1.31 universe 46 opened on 10.10.10.13:5568
2022-07-27 4:03:18 PM    DMX Univ 50    Information    E1.31 universe 50 opened on 10.10.10.14:5568
2022-07-27 4:03:18 PM    DMX Univ 51    Information    E1.31 universe 51 opened on 10.10.10.14:5568
2022-07-27 4:03:18 PM    DMX Univ 52    Information    E1.31 universe 52 opened on 10.10.10.14:5568
2022-07-27 4:03:18 PM    DMX Univ 53    Information    E1.31 universe 53 opened on 10.10.10.14:5568
2022-07-27 4:03:18 PM    DMX Univ 54    Information    E1.31 universe 54 opened on 10.10.10.14:5568
2022-07-27 4:03:18 PM    DMX Univ 55    Information    E1.31 universe 55 opened on 10.10.10.14:5568
2022-07-27 4:03:18 PM    DMX Univ 56    Information    E1.31 universe 56 opened on 10.10.10.14:5568
2022-07-27 4:03:18 PM    DMX Univ 57    Information    E1.31 universe 57 opened on 10.10.10.14:5568
2022-07-27 4:03:18 PM    DMX Univ 60    Information    E1.31 universe 60 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 61    Information    E1.31 universe 61 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 62    Information    E1.31 universe 62 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 63    Information    E1.31 universe 63 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 64    Information    E1.31 universe 64 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 65    Information    E1.31 universe 65 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 66    Information    E1.31 universe 66 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 67    Information    E1.31 universe 67 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 68    Information    E1.31 universe 68 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 69    Information    E1.31 universe 69 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 70    Information    E1.31 universe 70 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    DMX Univ 71    Information    E1.31 universe 71 opened on 10.10.10.15:5568
2022-07-27 4:03:18 PM    LOR-Reg    Information    COM3 opened as Regular with speed 57.6K
2022-07-27 4:03:18 PM    LOR-Aux A    Information    COM4 opened as Aux A with speed 115.4K

 

Edited by dgrant
Link to comment
Share on other sites

1 hour ago, dgrant said:

Now why both of yours show different port#'s than each other's, mine shows the same as Matt's, 8837 but Matt's changed itself to 9487. Where exactly might I identify this port # ? It appears I'm not getting the "Connection Accepted" either.

You can try a different port in the Control Panel settings. The default is 8837.

image.thumb.png.10ffbd872069054a2098a3735e92f3bb.png

Link to comment
Share on other sites

Thanks but didn't help. I tried both port numbers that Matt and Jim used, but neither gets this to work

Link to comment
Share on other sites

Can you control lights from the Sequencer? I am guessing not, because it uses the same mechanism. When Control Lights is enabled in the Sequencer, you should see a message in the Control Panel's network log about a connection from the Sequencer.

Which firewall software are you using on your computer? It may be blocking this communication between programs.

Matt

Link to comment
Share on other sites

I don't have anything connected quite yet to test with. I'm using Windows Defender since its free from MS.

Link to comment
Share on other sites

Try temporarily turning off Defender's firewall, and then see if going into the Hardware Utility releases the port.

Link to comment
Share on other sites

I turned off all three firewall settings, Domain, Public and Private. None allowed the HU to work via the CP

Link to comment
Share on other sites

I connected a single dumb strip to one DC controller and toggled it on via a sequence. It started to run then stopped even though the sequence was still playing and the commands going out should have continued. I shut off the CP but the sequencer won't command the lights without the CP running in the background. I am able to command the test lights function for that device and dumb strip via the CP

Link to comment
Share on other sites

I spoke too soon. It seems to still have an issue with the sequencer when it acquires the control lights capability. It plays about 1 second of the selected sequence to the lights, then the lights quit as the sequence still runs.

 

This issue is the same that Steven reported in the Sequencer Not Controlling the Lights. Hopefully fixed shortly

Edited by dgrant
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...