Modules for Samsung displays?
jkranz286
Posts: 7
Hello everyone.
What is the recommended method when there are no modules available for your specific display?
The Samsung displays that I will be controlling are:
Samsung UN85HU8550 - RS232
Samsung UN85JU7100F - RS232
Samsung UN49KU7000F - IR
Thank you for your input.
What is the recommended method when there are no modules available for your specific display?
The Samsung displays that I will be controlling are:
Samsung UN85HU8550 - RS232
Samsung UN85JU7100F - RS232
Samsung UN49KU7000F - IR
Thank you for your input.
0
Comments
For the IR one just learn IR code from the remote or try a IR file for samsung screen on the amx website.
I feel it's very important for us as programmers to not get overly lazy in this regard. I feel like we should be able to everything AMX in house programmers can do if not more as we are out in the battle fields. If you discipline yourself early on to write your own modules you'll quickly build up a useful library that Yiu have full control over. I highly recommend Yiu follow the AMX standard SNAPI guidelines so that you or a future programmer can easily drop in a new module. In other words: don't make yiur modules so different that they cannot work with the current standards/best practices. Most my modules can plug right into any main code following the SNAPI standard.
just a thiught.
Coding: this is short rant triggered with what Eric said. Unlike other control platforms craptron notably. With amx you have to write damn near the entirety of the program on your own, as that should be the case. Craptron is so big that there are modules out there for every device, every function everything so it takes little skill to connect signals together and to get a program working. To me and this is especially true because I'm still trying to find a programmer to fill a vacant spot where I work, is that I hold much more value in an amx programmer than a craptron programmer. In order to program an amx system you need to have a greater skill set than the other. So because of that I tend to think really go to the extreme and make things custom and better than it would be with manufacturer modules.
Standards: Eric I am a little guilty of not fully complying to this..... oops. Most of my channels follow SNAPI, but all of my modules are built around my framework and are nonstandard. Although you could drop them in someone else's code and make it work it would just require a little preparation. Part of it is how I group them all together, initialize them, and have almost all the values in them be able to change dynamically. I guess in hindsight I could have done a better job in making it a little more standard but I am waaay to far in it now to do anything about. So to conclude basically I am sorry.
I wouldn't feel bad about not always following SNAPI. It doesn't work for everything. In fact all my medial server modules don't even come close as SNAPI (IMHO) is not built for it. There are obviously many things we deal with that don't fit that mold. But for yiur workaday things like source or end point devices it's a perfectly fine convention. I'm not a fn of the few cases where they combine feedback channels with action channels like int the case of audio mute - channel 199. But for the most part it's okay.
to Vining's point - I tend to agree with some slight reservation. The whole notion of open source I tend to be more skeptical on the fairness of my fellow man. As proof of this I can site the Open-Source and free cost of LINUX, a platform I personally use and prefer. By almost any metric it is a better OS than Windows no Mac. But it has not caught on en masse'. Why? Tons of reasons. As most of us long-timers here on the forum may remember we had a bad spell of non-professional trolls allowed on basically asking us to write code for them for free because it was beneath their dignity to actually get the training and experience we spent countless hours and blood, sweat and tears getting. AND if we dared bring this fact up, we were then branded backward-thinking f$ck's who didn't understand open-source.
i thin Vining hit the nail on the head with AMX modules. The biggest complaint with them was reliability. I think we programmers were not without understanding and empathy for the plight of the folks writing the modules. We all have written code that "mostly" worked but had the occasional bug. Or even more commonly the manufacturer just up and changed the protocol. If we had a space here in the forum limited to the group with NDO s or whatnot with Source for the modules, we could have reacted quickly to the changes. Or even better yet - a community of programmers with a GIT or SVN repo with AMX management of the trunks to track public vs. private versions of the modules and their revisions. One of us VIPs could have managed it without any AMX Employees spending time on it.
i dunno... Woulda - Ciulda - Shoulda...
Power On = "$08,$22,$00,$00,$00,$02,$D4"
Power Off = "$08,$22,$00,$00,$00,$01,$D5"
HDMI1 = "$08,$22,$0a,$00,$05,$00,$c7"
9600 baud. I have the rest in a document around here somewhere if you need them. I'd just put those commands in a button event or in your power on/off functions and be done with it. I don't think they provide polling feedback on the EXLink port, or at least I don't have any info on doing it.
I agree that it's more complicated. I'd suggest a better way to describe what happened was the market "Moved Away" from higher-end automation toward an environment of less customization. I think I tend to be a bit more forgiving of our industry than perhaps you do. I don't think we handled it well. but, I'm not sure there was a better way to handle it.
Also, I agree that our days are numbered in Commercial as well. I find myself wandering farther and farther afield in search of the dwindling waterholes of where folks like us tend to thrive: Highly customizeable systems. Things like board rooms, divisible a/v spaces and large scale a/v distribution are tending to settle into "known science" that is now possible to use a check-list style programming method. I myself have written a lot of code this way. It's just I'm still the person filling in the check boxes.
My main market is still those areas too big to be well serviced by the mindless machines generating code. I realize that one day I might not be able to make it to the next watering hole.