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="Herr R aus B" data-source="post: 220368" data-attributes="member: 62807"><p>Great! Once again I have been taken over by historical events regarding the VL System MR300 driver landscape... Fortunately I managed to eliminate MHC from the auto start registry entries - so it's not running, but I certainly will have a look at the new driver tho <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p><strong><span style="color: Blue">===================================</span></strong></p><p></p><p>Seems to work as in kicks off MHC, but doesn't restart it after MP shutdown. Should it?</p><p></p><p></p><p></p><p><strong><span style="color: Blue">===================================</span></strong></p><p></p><p>Me again - I just have been looking at the first of the URLs, Manfred posted. And I find these little functions interesting, as there are some, we obviously never took into account - these are the gotoXY function, that also sends a 0xA7 that we couldn't determine its meaning so far and the initFans function. The other functions match pretty good our results... Unfortunately we still can't be sure whther this 0xA4 0x7E we<a href="https://forum.team-mediaportal.com/showpost.php?p=220011&postcount=92" target="_blank"> discussed here</a> really is setting the display to internal standby mode or to display the internal time. If 0xA4 0x7D really means "init fans" than 0xA4 0x7E might be "init display" meaning setting the display to its internal standby screen... Maybe these delays they are using in there functions might be of any interest... Finally this cler function explains the 0xA0...</p><p></p><p>[CODE][FONT="Courier New"][SIZE="2"]def write(fd, v):</p><p> os.write(fd, chr(v))</p><p></p><p>def writeChr(fd, c):</p><p> os.write(fd, c)</p><p></p><p>def writeLn(fd, ln):</p><p> for i in range(0, min(len(ln), 20)):</p><p> writeChr(fd, ln[i])</p><p> time.sleep(0.000040)</p><p></p><p>[COLOR="LightBlue"]def clear(fd):</p><p> write(fd, 0xA0)</p><p> time.sleep(0.000040)</p><p>[/COLOR]</p><p>[COLOR="Blue"]def gotoXY(fd, x, y):</p><p> write(fd, 0)</p><p> write(fd, 0xA1+y)</p><p> write(fd, x)</p><p> write(fd, 0xA7)</p><p> time.sleep(0.000040)</p><p></p><p>def initFans(fd):</p><p> write(fd, 0)</p><p> write(fd, 0xA4)</p><p> write(fd, 0x7D)[/COLOR]</p><p></p><p>def setFans(fd, fan1, fan2):</p><p> write(fd, 0)</p><p> write(fd, 0xAC)</p><p> write(fd, fan1)</p><p> write(fd, fan2)</p><p> time.sleep(0.000040)</p><p></p><p>def setChars(fd, chars):</p><p> write(fd, 0)</p><p> write(fd, 0xAD)</p><p> for char in chars:</p><p> for row in char:</p><p> write(fd, row)</p><p> time.sleep(0.000040)[/SIZE][/FONT]</p><p>[/CODE]</p><p>I scanned one of the old logs and found this right after the COM port was initialized:</p><p>[CODE][FONT="Courier New"][SIZE="2"][COLOR="Blue"]00 .</p><p>A1 ¡</p><p>00 A7 .§[/COLOR]</p><p>20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 </p><p>20 20 20 20 </p><p>[COLOR="Blue"]00 .</p><p>AF ¯[/COLOR]</p><p>00 .</p><p>A2 ¢</p><p>00 A7 .§</p><p>[COLOR="Blue"]20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 </p><p>20 20 20 20 [/COLOR] </p><p>[/SIZE][/FONT]</p><p>[/CODE]</p><p>According to these functions that would be </p><ol> <li data-xf-list-type="ol">gotoXY(0,0) as in place the cursor in the upper left corner (at least I assume that the upper left corner is at 0,0),</li> <li data-xf-list-type="ol">write 20 spaces at the current cursor position and thus, clear the first line of the display</li> <li data-xf-list-type="ol">call temp values (0x00 0xAF as can be read in the function Manfred posted)</li> <li data-xf-list-type="ol">gotoXY(0,1) as in put the cursor to the first character of the second line</li> <li data-xf-list-type="ol">write 20 spaces at the current cursor position and thus, clear the second line of the display</li> </ol></blockquote><p></p>
[QUOTE="Herr R aus B, post: 220368, member: 62807"] Great! Once again I have been taken over by historical events regarding the VL System MR300 driver landscape... Fortunately I managed to eliminate MHC from the auto start registry entries - so it's not running, but I certainly will have a look at the new driver tho :) [B][COLOR="Blue"]===================================[/COLOR][/B] Seems to work as in kicks off MHC, but doesn't restart it after MP shutdown. Should it? [B][COLOR="Blue"]===================================[/COLOR][/B] Me again - I just have been looking at the first of the URLs, Manfred posted. And I find these little functions interesting, as there are some, we obviously never took into account - these are the gotoXY function, that also sends a 0xA7 that we couldn't determine its meaning so far and the initFans function. The other functions match pretty good our results... Unfortunately we still can't be sure whther this 0xA4 0x7E we[URL="https://forum.team-mediaportal.com/showpost.php?p=220011&postcount=92"] discussed here[/URL] really is setting the display to internal standby mode or to display the internal time. If 0xA4 0x7D really means "init fans" than 0xA4 0x7E might be "init display" meaning setting the display to its internal standby screen... Maybe these delays they are using in there functions might be of any interest... Finally this cler function explains the 0xA0... [CODE][FONT="Courier New"][SIZE="2"]def write(fd, v): os.write(fd, chr(v)) def writeChr(fd, c): os.write(fd, c) def writeLn(fd, ln): for i in range(0, min(len(ln), 20)): writeChr(fd, ln[i]) time.sleep(0.000040) [COLOR="LightBlue"]def clear(fd): write(fd, 0xA0) time.sleep(0.000040) [/COLOR] [COLOR="Blue"]def gotoXY(fd, x, y): write(fd, 0) write(fd, 0xA1+y) write(fd, x) write(fd, 0xA7) time.sleep(0.000040) def initFans(fd): write(fd, 0) write(fd, 0xA4) write(fd, 0x7D)[/COLOR] def setFans(fd, fan1, fan2): write(fd, 0) write(fd, 0xAC) write(fd, fan1) write(fd, fan2) time.sleep(0.000040) def setChars(fd, chars): write(fd, 0) write(fd, 0xAD) for char in chars: for row in char: write(fd, row) time.sleep(0.000040)[/SIZE][/FONT] [/CODE] I scanned one of the old logs and found this right after the COM port was initialized: [CODE][FONT="Courier New"][SIZE="2"][COLOR="Blue"]00 . A1 ¡ 00 A7 .§[/COLOR] 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 [COLOR="Blue"]00 . AF ¯[/COLOR] 00 . A2 ¢ 00 A7 .§ [COLOR="Blue"]20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 [/COLOR] [/SIZE][/FONT] [/CODE] According to these functions that would be [LIST=1] [*]gotoXY(0,0) as in place the cursor in the upper left corner (at least I assume that the upper left corner is at 0,0), [*]write 20 spaces at the current cursor position and thus, clear the first line of the display [*]call temp values (0x00 0xAF as can be read in the function Manfred posted) [*]gotoXY(0,1) as in put the cursor to the first character of the second line [*]write 20 spaces at the current cursor position and thus, clear the second line of the display [/LIST] [/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