GarnerLights Posted February 4, 2022 Posted February 4, 2022 After connecting all my lights to my Microsoft Surface Pro X, the Hardware Utility will see it just fine, and I can control the lights just fine (I'm currently testing two props, a pixel snowflake from HolidayCoro and a "Magicolour High Grade 230w Beam" from Magical Light Shows). But, when going into Sequencer (and I made sure Light-O-Rama Control Panel was open and that "Control Lights" was selected in Sequencer) and pressing play, the music will play and the timeline progresses, but the lights won't do anything. This had worked before on the MacBook Pro I was using before switching over, but it's no longer working on the Surface. I'm running Windows 10 Pro 20H2 with the LOR S5 software suite, if that helps at all.
PhilMassey Posted February 4, 2022 Posted February 4, 2022 Have you checked the settings in Network Preferences reflect your new setup.
GarnerLights Posted February 4, 2022 Author Posted February 4, 2022 1 hour ago, PhilMassey said: Have you checked the settings in Network Preferences reflect your new setup. Yes.
GarnerLights Posted February 4, 2022 Author Posted February 4, 2022 I decided to take a look at the LOR Control Panel and I got these errors: 2022-02-04 13:20:33 10:LCM [WARN ] Error loading FTDI DLL; FTDI-based adapters will not be usable 2022-02-04 13:20:33 1:LORManager [WARN ] No FTDI interface available; LOR networks will not control lights Did I do something wrong / miss something when I installed my FTDI Drivers (I installed the ARM-specific ones because the Surface Pro is an ARM device)?
Jimehc Posted February 4, 2022 Posted February 4, 2022 Could you please show where you found a driver for an ARM Device... As they a not available here > https://ftdichip.com/drivers/
GarnerLights Posted February 4, 2022 Author Posted February 4, 2022 10 minutes ago, Jimehc said: Could you please show where you found a driver for an ARM Device... As they a not available here > https://ftdichip.com/drivers/ Should show up on this page: https://ftdichip.com/drivers/vcp-drivers/ I had to install it manually because the setup exe wouldn't go further than the Extract wizard.
Jimehc Posted February 5, 2022 Posted February 5, 2022 (edited) 7 hours ago, GarnerLights said: Should show up on this page: https://ftdichip.com/drivers/vcp-drivers/ I had to install it manually because the setup exe wouldn't go further than the Extract wizard. That does not contain ARM Drivers - Only AMD64 & I386 Drivers... Edited February 5, 2022 by Jimehc
GarnerLights Posted February 5, 2022 Author Posted February 5, 2022 11 hours ago, Jimehc said: That does not contain ARM Drivers - Only AMD64 & I386 Drivers... Where are you looking? Correct me if I'm wrong, but on the VCP drivers page it does show ARM. The Surface Pro X is ARM64-compatible so the drivers theoretically should work. https://ftdichip.com/drivers/vcp-drivers/#:~:text=–-,2.12.36.4A****,-–
GarnerLights Posted February 6, 2022 Author Posted February 6, 2022 On 2/5/2022 at 11:30 AM, Jimehc said: Yet is does not and the Setup stops... I'm not sure what you mean? If I use the setup executable, then it will stop installation, but manually getting the drivers from FTDI and installing them via Device Manager works just fine. It's when I try controlling them via Sequencer, which doesn't work. Like I said, it will work if I use Hardware Utility, but Sequencer won't talk to them, and that's what I'm trying to figure out.
Jimehc Posted February 7, 2022 Posted February 7, 2022 (edited) Hardware Utility=closed > Control Panel running - Controls Lights in Sequencer Enabled - Network Preferences point to Proper Adapter & COM Port Edited February 7, 2022 by Jimehc
GarnerLights Posted February 7, 2022 Author Posted February 7, 2022 6 hours ago, Jimehc said: Hardware Utility=closed > Control Panel running - Controls Lights in Sequencer Enabled - Network Preferences point to Proper Adapter & COM Port So I figured out the problem, but it wasn't this, though it was related: the spotlight that we have doesn't support the LOR Enhanced network, so we need to use 2 different USB485 adapters. Thanks for your help though!
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now