I've got an old mx4 that starting to die on me so I was thinking about possibly replacing it with another MO product. From what I can tell the GLK19264-7T-1U-USB-YG seems to be the closest in functionality to the MX4 for graphical LCD's.
My primary use for the screen is to control fans, lights and the water pump in my machine.
My questions are:
The specs list it as having 6 GPO's but no advanced GPO's. Does this mean it doesn't have the PWM control capabilities of the MX4? In LCDC the advanced GPO settings are the ones that let you tweak PWM and RPM reporting.
What software is used to control the GPO's? I've played with LCD studio (which seems to be what yall are useing for the graphical displays, correct me if I'm wrong) for a number of years but to my knowledge it doesn't have the ability to control the GPO's.
Finally, if this display doesn't have the ability to contol it's GPO's with PWM, do any of the new displays have that ability? I'd rather not get another MX display since I've had so many problems with it but I'm willing to give all new hardware a try.
Questions about GLK
Hello,
Thanks for your post. Thank you also for your continued interest in our products.
With the MX series obsoleted, we have introduced the LK204-25-USBs. Unfortunately, we have cut down some features, including the one you are interested in - fan control. Please see this document
What we intend to replace the MX series is our GX Typhoon Series. The GX series will have digital baybus add on that will contain features like fan controls; this is coming in the future.
Thanks,
Thanks for your post. Thank you also for your continued interest in our products.
With the MX series obsoleted, we have introduced the LK204-25-USBs. Unfortunately, we have cut down some features, including the one you are interested in - fan control. Please see this document
What we intend to replace the MX series is our GX Typhoon Series. The GX series will have digital baybus add on that will contain features like fan controls; this is coming in the future.
Thanks,
Raquel Malinis
Design and Development
Matrix Orbital
Design and Development
Matrix Orbital
Any estimate as to how far in the future? I would be willing to throw my old rheostat baybus in and wait if it's not going to be too long.
I also wouldn't mind fixing my MX4 if yall have any ideas why lcdc has gradually begun to halt with com errors. Once it halts, lcdc is unable to connect to it again until the display is power cycled and windows is restarted. In this state it also causes all USB devices on my machine to run slow (but doesn't take up CPU) so I have to unplug it.
I also wouldn't mind fixing my MX4 if yall have any ideas why lcdc has gradually begun to halt with com errors. Once it halts, lcdc is unable to connect to it again until the display is power cycled and windows is restarted. In this state it also causes all USB devices on my machine to run slow (but doesn't take up CPU) so I have to unplug it.
Hi,
Sorry but the baybus might take some more. We have planned for them, and definitely have some things started, but have just taken a step back because of more urgent things.
As per the communication problems with the MX4, this sounds like more of a software problem. Please check out LCDC as they also have a forum that might help you.
Thanks and Best Regards,
Sorry but the baybus might take some more. We have planned for them, and definitely have some things started, but have just taken a step back because of more urgent things.
As per the communication problems with the MX4, this sounds like more of a software problem. Please check out LCDC as they also have a forum that might help you.
Thanks and Best Regards,
Raquel Malinis
Design and Development
Matrix Orbital
Design and Development
Matrix Orbital
Well it's no longer recognized in windows when it does that, if I just unplug and plug the usb cable back in it shows up and "unrecognized device".
It stays in that state until I take the measures mentioned before.
It's done this across several motherboards over the years intermittently, but now it's in variably within a few hours of bootup.
It stays in that state until I take the measures mentioned before.
It's done this across several motherboards over the years intermittently, but now it's in variably within a few hours of bootup.