home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Input / Output interfaces
Mini Display
Zalman HD135 VFD (VlSys Mplay)
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="cybrmage" data-source="post: 219622" data-attributes="member: 51680"><p>ANY case fan running at full speed will make some noise... That's the reason that most of the HTPC cases have either a manual (eg: Antec fusion case) or automatic (eg: HD135 case) fan controls.</p><p></p><p></p><p>Well... OK.... who am I to argue 8-}</p><p></p><p></p><p></p><p>I do hope that you are kidding!!!</p><p></p><p></p><p>I don't know... I didn't program the ExternalDisplay plugin... I just write drivers...</p><p></p><p></p><p>I believe that would be "MediaPortal II"... It's in early alpha, and I haven't had a chance to look at it yet.</p><p></p><p></p><p></p><p></p><p></p><p>Custom characters are simple...</p><p></p><p>The display expects ALL custom character to be defined when sent the "define characters" command.</p><p>Each character is a 5x8 matrix defined by 8 bytes of character data...</p><p>Each byte defines a horizontal row of pixels... The three high order bits are ignored...</p><p></p><p>IE:</p><p></p><p>the data { 0x00, 0x00, 0x0E, 0x11, 0x11, 0x11, 0x11, 0x11 }</p><p>defines a character</p><p></p><p><span style="font-family: 'Courier New'"></span></p><p><span style="font-family: 'Courier New'">........ 0x00</span></p><p><span style="font-family: 'Courier New'">........ 0x00</span></p><p><span style="font-family: 'Courier New'">....***. 0x0E</span></p><p><span style="font-family: 'Courier New'">...*...* 0x11</span></p><p><span style="font-family: 'Courier New'">...*...* 0x11</span></p><p><span style="font-family: 'Courier New'">...*...* 0x11</span></p><p><span style="font-family: 'Courier New'">...*...* 0x11</span></p><p><span style="font-family: 'Courier New'">...*...* 0x11</span></p><p><span style="font-family: 'Courier New'"></span></p><p></p><p></p><p>So, the "define custom characters" command breaks down like this</p><p></p><p><span style="font-family: 'Courier New'"></span></p><p><span style="font-family: 'Courier New'">AD ; the "define custom characters" command</span></p><p><span style="font-family: 'Courier New'">00 00 0E 11 11 11 11 11 ; The definition data for custom character 0</span></p><p><span style="font-family: 'Courier New'">01 01 01 01 01 01 01 00 ; The definition data for custom character 1</span></p><p><span style="font-family: 'Courier New'">00 00 0E 01 01 01 01 01 ; The definition data for custom character 2</span></p><p><span style="font-family: 'Courier New'">00 00 01 11 11 11 11 0F ; The definition data for custom character 3</span></p><p><span style="font-family: 'Courier New'">00 00 0E 10 10 10 10 10 ; The definition data for custom character 4</span></p><p><span style="font-family: 'Courier New'">00 00 01 01 01 01 01 01 ; The definition data for custom character 5</span></p><p><span style="font-family: 'Courier New'">0E 10 10 10 10 10 0E 00 ; The definition data for custom character 6</span></p><p><span style="font-family: 'Courier New'">0E 01 01 01 01 01 0E 00 ; The definition data for custom character 7</span></p><p><span style="font-family: 'Courier New'"></span></p><p></p><p>To display a custom chatacter, you send the index of the custom character { 0 - 7 } to the display with the 0xA& command.</p><p></p><p>IE:</p><p>sending {0x05, 0x03, 0x20, 0x41, 0x42, 0x43 } to the display will show "{custom character 5}{custom character 3} ABC".</p><p></p><p>The MHC program displays the large clock by redefining the custom characters before sending the two lines that make up the display.</p><p></p><p></p><p></p><p>Still working on it... 8-}</p><p></p><p></p><p></p><p></p><p>That's the beauty of having a configurable remote!!!... Some people want a button to do one thing... others want something else... With it being configurable, you can "please all of the people all of the time". Would having "STANDBY" as the default be better??</p><p></p><p></p><p>The ExteralDisplay plugin controls the driver... When it receives a standby/hibernate/shutdown message, it stops the driver... (calls the Cleanup() function)... When it gets a "resume from hibernate/standby" message, it starts the driver again... (calls the Setup() and Initialize() functions)...</p><p></p><p>In the drivers Cleanup() function, we (try to) send the display all the commands it needs to display a shutdown message, dim the display, set it's internal clock (I do not know if it actually has one), configure it to wake the machine, etc... Then we close the port completely. The logs do dhow that the port is being closed.</p><p></p><p></p><p>We just need to determine the correct commands to send to it to enable it to wake the machine...</p><p></p><p></p><p></p><p></p><p>I assume you are referring to the "1x26".... Don't blame me!!! That's the interpretation that the CLR is making of the data... which is extremely strange.... It means that it received a value of 0x126... but the data is only a single byte...</p><p></p><p></p><p></p><p>maybe... I'm not sure if the { 0x00, 0x00, 0x00 } is an actual command, an idle delay, or an end of command marker...</p><p></p><p>It's use seems to be ambiguous... The 0xA1, 0xA2 and 0xA7 commands seem to be followed by a 0x00 end of command marker... but the other commands do not seem to be....</p><p></p><p>The other question is about the 0xAE command... what does it do?? I see in the logs that is is sent as 0xAE, { 0xAE, 0xAE } or { 0xAE, 0xAE, 0xAE }... Are these the same command being sent multiple times, or does the number of bytes signify a different command??? (I would suspect it is the same command multiple times... but why is it sent in multiples?)</p><p></p><p></p><p></p><p></p><p>That should be rather easy... pick the button you want to use, then in the remote configuration editor, add a new action to that key (click on "new")... the click on the "no condition" entry and change it to "Window" and select the "Fullscreen Video" dropdown. The change the Action dropdown to "Key Pressed", and change the "key" (first box) to 83. Then save your changes.</p><p></p><p></p><p></p><p></p><p>Sorry... I can't help you with that... hopefully someone else on the forum can help you with that.</p><p></p><p></p><p>Regards,</p><p>CybrMage</p></blockquote><p></p>
[QUOTE="cybrmage, post: 219622, member: 51680"] ANY case fan running at full speed will make some noise... That's the reason that most of the HTPC cases have either a manual (eg: Antec fusion case) or automatic (eg: HD135 case) fan controls. Well... OK.... who am I to argue 8-} I do hope that you are kidding!!! I don't know... I didn't program the ExternalDisplay plugin... I just write drivers... I believe that would be "MediaPortal II"... It's in early alpha, and I haven't had a chance to look at it yet. Custom characters are simple... The display expects ALL custom character to be defined when sent the "define characters" command. Each character is a 5x8 matrix defined by 8 bytes of character data... Each byte defines a horizontal row of pixels... The three high order bits are ignored... IE: the data { 0x00, 0x00, 0x0E, 0x11, 0x11, 0x11, 0x11, 0x11 } defines a character [FONT="Courier New"] ........ 0x00 ........ 0x00 ....***. 0x0E ...*...* 0x11 ...*...* 0x11 ...*...* 0x11 ...*...* 0x11 ...*...* 0x11 [/FONT] So, the "define custom characters" command breaks down like this [FONT="Courier New"] AD ; the "define custom characters" command 00 00 0E 11 11 11 11 11 ; The definition data for custom character 0 01 01 01 01 01 01 01 00 ; The definition data for custom character 1 00 00 0E 01 01 01 01 01 ; The definition data for custom character 2 00 00 01 11 11 11 11 0F ; The definition data for custom character 3 00 00 0E 10 10 10 10 10 ; The definition data for custom character 4 00 00 01 01 01 01 01 01 ; The definition data for custom character 5 0E 10 10 10 10 10 0E 00 ; The definition data for custom character 6 0E 01 01 01 01 01 0E 00 ; The definition data for custom character 7 [/FONT] To display a custom chatacter, you send the index of the custom character { 0 - 7 } to the display with the 0xA& command. IE: sending {0x05, 0x03, 0x20, 0x41, 0x42, 0x43 } to the display will show "{custom character 5}{custom character 3} ABC". The MHC program displays the large clock by redefining the custom characters before sending the two lines that make up the display. Still working on it... 8-} That's the beauty of having a configurable remote!!!... Some people want a button to do one thing... others want something else... With it being configurable, you can "please all of the people all of the time". Would having "STANDBY" as the default be better?? The ExteralDisplay plugin controls the driver... When it receives a standby/hibernate/shutdown message, it stops the driver... (calls the Cleanup() function)... When it gets a "resume from hibernate/standby" message, it starts the driver again... (calls the Setup() and Initialize() functions)... In the drivers Cleanup() function, we (try to) send the display all the commands it needs to display a shutdown message, dim the display, set it's internal clock (I do not know if it actually has one), configure it to wake the machine, etc... Then we close the port completely. The logs do dhow that the port is being closed. We just need to determine the correct commands to send to it to enable it to wake the machine... I assume you are referring to the "1x26".... Don't blame me!!! That's the interpretation that the CLR is making of the data... which is extremely strange.... It means that it received a value of 0x126... but the data is only a single byte... maybe... I'm not sure if the { 0x00, 0x00, 0x00 } is an actual command, an idle delay, or an end of command marker... It's use seems to be ambiguous... The 0xA1, 0xA2 and 0xA7 commands seem to be followed by a 0x00 end of command marker... but the other commands do not seem to be.... The other question is about the 0xAE command... what does it do?? I see in the logs that is is sent as 0xAE, { 0xAE, 0xAE } or { 0xAE, 0xAE, 0xAE }... Are these the same command being sent multiple times, or does the number of bytes signify a different command??? (I would suspect it is the same command multiple times... but why is it sent in multiples?) That should be rather easy... pick the button you want to use, then in the remote configuration editor, add a new action to that key (click on "new")... the click on the "no condition" entry and change it to "Window" and select the "Fullscreen Video" dropdown. The change the Action dropdown to "Key Pressed", and change the "key" (first box) to 83. Then save your changes. Sorry... I can't help you with that... hopefully someone else on the forum can help you with that. Regards, CybrMage [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Input / Output interfaces
Mini Display
Zalman HD135 VFD (VlSys Mplay)
Contact us
RSS
Top
Bottom