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: 219717" data-attributes="member: 51680"><p>You know.... I completely missed it... Neither of your posts was there when I started writing the info... When I finally posted it, I saw your second post ( #77) and didn't bother scrolling up to notic #76...</p><p></p><p>My appologies!!!</p><p></p><p></p><p></p><p></p><p>Yes... it is strange... but the reason is simple... 0x00 is used as an End-Of-Line character... (could it be that the extra 0x00's that are being sent to the display are actually a bug in the MHC data collection routine... It determines what commands it wants to send to the display and adds a 0x00 terminator?? no data = terminator only???).</p><p></p><p>Because the 0x00 is used as a termination, it can't be used as a character...</p><p></p><p>I didn't have enough data from your logs to determine for sure that the 0x00 was the termination or that 0x08 was used in a display string... so I arbitrarily picked 0x00... bad choice 8-{... you are absolutely correct!</p><p></p><p>At least we both managed to determine the character encoding correctly 8-}</p><p></p><p></p><p></p><p>That's the way things go sometimes.... The timezone difference (8 hours) doesn't help any either... Something we'll have to deal with (unless you are planning on moving to a reasonable timezone 8-} )</p><p></p><p>Besides... I'd rather get a little out of sync, and get good information (and confirmation of said information) than be in sync with very little info or feedback...</p><p></p><p></p><p></p><p>No... your english is very good.... I just couldn't resist the retort!! 8-}</p><p></p><p></p><p></p><p>Here is another test version...</p><p></p><p>I rewrote the serial data handling rotine (again)... This time I added filtering of invalid data (why are we geting 0x3F all of a sudden???) and two rudimentary state machines ( the first to make sure we don't send a request for temperature data before we receive the data from the previous request and the second to try and properly detect a remote button that is being held down).</p><p></p><p>I also changed the initialization routine to send the same data (all those 0xAA's) as the MHC program....</p><p></p><p>And, I also discovered that I was not correctly closing the serial port on shutdown... hopefully this fix will let the display restart the machine from shutdown/hibernate/sleep (fingers crossed)!! 8-}</p><p></p><p>I also changed the shutdown routine to set the fan speed for both fans to 40%... Better to have a little noise from the fan than the expense of replacing a machine that has overheated.!!!..</p><p></p><p>Please make sure you have the options "Use fan control" turned on, and at least one of the fans set to "automatic" when you test this one (The temperature requests are only sent to the display if automatic fan control is needed).</p><p></p><p>Regards,</p><p>CybrMage</p></blockquote><p></p>
[QUOTE="cybrmage, post: 219717, member: 51680"] You know.... I completely missed it... Neither of your posts was there when I started writing the info... When I finally posted it, I saw your second post ( #77) and didn't bother scrolling up to notic #76... My appologies!!! Yes... it is strange... but the reason is simple... 0x00 is used as an End-Of-Line character... (could it be that the extra 0x00's that are being sent to the display are actually a bug in the MHC data collection routine... It determines what commands it wants to send to the display and adds a 0x00 terminator?? no data = terminator only???). Because the 0x00 is used as a termination, it can't be used as a character... I didn't have enough data from your logs to determine for sure that the 0x00 was the termination or that 0x08 was used in a display string... so I arbitrarily picked 0x00... bad choice 8-{... you are absolutely correct! At least we both managed to determine the character encoding correctly 8-} That's the way things go sometimes.... The timezone difference (8 hours) doesn't help any either... Something we'll have to deal with (unless you are planning on moving to a reasonable timezone 8-} ) Besides... I'd rather get a little out of sync, and get good information (and confirmation of said information) than be in sync with very little info or feedback... No... your english is very good.... I just couldn't resist the retort!! 8-} Here is another test version... I rewrote the serial data handling rotine (again)... This time I added filtering of invalid data (why are we geting 0x3F all of a sudden???) and two rudimentary state machines ( the first to make sure we don't send a request for temperature data before we receive the data from the previous request and the second to try and properly detect a remote button that is being held down). I also changed the initialization routine to send the same data (all those 0xAA's) as the MHC program.... And, I also discovered that I was not correctly closing the serial port on shutdown... hopefully this fix will let the display restart the machine from shutdown/hibernate/sleep (fingers crossed)!! 8-} I also changed the shutdown routine to set the fan speed for both fans to 40%... Better to have a little noise from the fan than the expense of replacing a machine that has overheated.!!!.. Please make sure you have the options "Use fan control" turned on, and at least one of the fans set to "automatic" when you test this one (The temperature requests are only sent to the display if automatic fan control is needed). 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