Orion5150 Posted October 7, 2012 Share Posted October 7, 2012 Received my 6 CCP's(doubles) last week along with USB485 adapters(software dated 8-31-2011). I have S-3(ver 3.7) advanced with SuperStar on Vista. The Hardware Utility does not recognize the CCP controllers. I get, "01 unknown device" after hitting the refresh button. Tried 3 different USB485 adapters. Comm ports work fine. Tried different Cat5E cables. I then downloaded "latest drivers" for 485 adapters. I still get "01 unknown device" after hitting refresh. I do get a steady led light on each controller though. All my 1602w's are identified just fine, just not any of the CCP controllers. I can't proceed to Configuration because the CCR/CCB button is greyed out. Any ideas on what the problem/fix is? Thanks in advance! Link to comment Share on other sites More sharing options...
Ron Boyd Posted October 7, 2012 Share Posted October 7, 2012 (edited) You did hook them up 1 at a time right, with nothing else hooked up but the USB 485? If not, you have to add them 1 at a time and set the ID # on each one seperately. Edited October 7, 2012 by Ron Boyd Link to comment Share on other sites More sharing options...
Don Posted October 7, 2012 Share Posted October 7, 2012 The Hardware Utility does not recognize the CCP controllers. I get, "01 unknown device" after hitting the refresh button.When the newer Generation 3 controllers came out, those running the S2 versions of the software would experience these same issues. The light on the controller would go solid, meaning communication was there, but the Hardware utility didn't know exactly what was connected, just that *something* was connected.It sounds like something, somewhere, didn't go quite right with your installation. I would suggest a quick uninstall/reinstall following these steps.Make a backup copy of your sequences/audio/clipboards/visualization, just to be on the safe side.Uninstall using the normal Windows uninstall process.Run the Registry Wipe program for 3.7.0.Re-Install the software.At this point I would suspect that things will be resolved for you.A more technical answer below. Use at own risk. Do not attempt changes without backup copies.Look in your LOR Program directory. On a 64 bit machine this is usually "C:\Program Files (x86)\Light-O-Rama"Now look for a file called LOR_Device.txt, with great care, open it in a text editor. Do you see any lines starting with:185,CCB100D Ver 1.?123,CCB100 Ver 1.?If not, then I would suspect this is the file that didn't get installed correctly. You could try the steps above, skipping #3 to see if that quickly resolves the issue. Link to comment Share on other sites More sharing options...
Orion5150 Posted October 7, 2012 Author Share Posted October 7, 2012 I did have just one controller hooked up at a time. I think Don is probably right. I will try to reinstall S-3. Will have to wait until tomorrow when someone with better computer skills can assist so I don't lose everything! Thanks guys! Link to comment Share on other sites More sharing options...
Orion5150 Posted October 7, 2012 Author Share Posted October 7, 2012 Don, I looked in the LOR Program directory. Both lines you mentioned (185,CCB100D Ver1.? & 123,CCB100 Ver1.?) were in the LOR Device text file. Does this change your thinking that a reinstall is still called for? Link to comment Share on other sites More sharing options...
Orion5150 Posted October 7, 2012 Author Share Posted October 7, 2012 When the newer Generation 3 controllers came out, those running the S2 versions of the software would experience these same issues. The light on the controller would go solid, meaning communication was there, but the Hardware utility didn't know exactly what was connected, just that *something* was connected.It sounds like something, somewhere, didn't go quite right with your installation. I would suggest a quick uninstall/reinstall following these steps.Make a backup copy of your sequences/audio/clipboards/visualization, just to be on the safe side.Uninstall using the normal Windows uninstall process.Run the Registry Wipe program for 3.7.0.Re-Install the software.At this point I would suspect that things will be resolved for you.A more technical answer below. Use at own risk. Do not attempt changes without backup copies.Look in your LOR Program directory. On a 64 bit machine this is usually "C:\Program Files (x86)\Light-O-Rama"Now look for a file called LOR_Device.txt, with great care, open it in a text editor. Do you see any lines starting with:185,CCB100D Ver 1.?123,CCB100 Ver 1.?If not, then I would suspect this is the file that didn't get installed correctly. You could try the steps above, skipping #3 to see if that quickly resolves the issue.Don, both lines were in the LOR device text file. Does this change your opinion that a reinstall is necessary? Link to comment Share on other sites More sharing options...
Don Posted October 7, 2012 Share Posted October 7, 2012 There is a part of me that says a re-install is worth a try.The other part of me says that we're missing something incredibly simple here. If no one else pops up with an answer, I'd give the re-install a try. Link to comment Share on other sites More sharing options...
LOR Staff Posted October 9, 2012 Share Posted October 9, 2012 I spoke with Orion today by phone and we did a complete (and clean) re-installation of S3 - including the registry wipe. We verified the devices file is correct. Unfortunately he still has the same issue. I sent his ticket up to the big man (Dan), who I know will be able to figure it out - unfortunately he's swamped at the moment, and I feel really bad that I couldn't get his hardware working. If anyone has a suggestion about what is going wrong, please let me (and Orion) know! Link to comment Share on other sites More sharing options...
bisquit476 Posted October 9, 2012 Share Posted October 9, 2012 Is the adapter the 485 or the 485B? I doubt it makes a difference, but want to make sure we're all on the same page. Link to comment Share on other sites More sharing options...
Ron Boyd Posted October 9, 2012 Share Posted October 9, 2012 If you have all of your USB 485s configured to the network you're using for each, try plugging all of the 485s in like you're going to run your show.Now, Say one of them has 3 CCPs (6 strings), on network Aux A: hook up the first CCP and set the ID #. Unplug it and connect your next controller and assign it a different ID #, and so on until all of them have unit IDs assigned. (make sure you mark each one somehow)Once you have all of the IDs configured, then, keep all USB 485s hooked up, then attach the controller/s and then see if the HU will recognize them.I had the same problem but using a DMX device. I didn't chime in with it, because I figured yours was a different problem. The above instructions worked for the DMX device. Don't know if this is the solution to your problem, but it's worth a try. Link to comment Share on other sites More sharing options...
Orion5150 Posted October 11, 2012 Author Share Posted October 11, 2012 Is the adapter the 485 or the 485B? I doubt it makes a difference, but want to make sure we're all on the same page.I have 2 USB485 adapters and on USB485B adapterI have 2 USB485 adapters and 1 USB485B adapter Link to comment Share on other sites More sharing options...
Orion5150 Posted October 11, 2012 Author Share Posted October 11, 2012 If you have all of your USB 485s configured to the network you're using for each, try plugging all of the 485s in like you're going to run your show.Now, Say one of them has 3 CCPs (6 strings), on network Aux A: hook up the first CCP and set the ID #. Unplug it and connect your next controller and assign it a different ID #, and so on until all of them have unit IDs assigned. (make sure you mark each one somehow)Once you have all of the IDs configured, then, keep all USB 485s hooked up, then attach the controller/s and then see if the HU will recognize them.I had the same problem but using a DMX device. I didn't chime in with it, because I figured yours was a different problem. The above instructions worked for the DMX device. Don't know if this is the solution to your problem, but it's worth a try.No luck with your suggestion. I can assign a unit ID to each controller but the HU does not recognize the device type. When i hit the refresh button, I get, "1 unit found" and "11 unknown device". 11 being the unit ID I changed it to. I am unable to configure the CCP controller because that option is greyed out. Link to comment Share on other sites More sharing options...
LOR Staff Posted November 6, 2012 Share Posted November 6, 2012 Oh Microsoft User Access Control. How do I hate thee? Let me count the ways..... 998,902Dan bounced this around a couple of times with the user, and we even had him send some of his controllers back incase of something hardware related. Instead, it was UAC AGAIN that did us in....This particular customer had originally installed 1.6.2 (S1) on this machine. The Device file was installed way back then too, but it didn't know about CCDs. With a normal operating system, uninstalling and re installing should have overwritten this file. Every time we looked at the file directly, it was the new one. Ah, but Windows thinks it knows better than we do.In an effort to keep viruses out of the Program Files directory, early versions of Vista removed permissions for files in these directories and then monitored for changes. If a change DID occur, it would write the file and you would believe it was replaced. HOWEVER it was keeping a secret copy . When the Hardware Utility asked for the Devices file, instead of it giving us the new one (the only one that should have existed), it would send us the SECRET copy.The solution is to turn OFF UAC, uninstall LOR, Re Install LOR, and then turn UAC back on. Windows will then kill it's secret copy. Link to comment Share on other sites More sharing options...
Recommended Posts