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: 219671" data-attributes="member: 51680"><p>What stuff??? The character definitions?? I posted that I had figured it out.... One of your logs showed MHC displaying the clock.... once you posted a picture showing the clock, I was able to deduce that the 64 bytes of data in the 0xAD command was custom character data.... I then manually decoded the data into character maps, and correlated that into the data being sent by MHC for the clock display... and managed to get results that match the picture.</p><p></p><p></p><p></p><p></p><p>What logo?</p><p></p><p></p><p></p><p>I could be wrong... but I don't think so... Please explain why you think I'm wrong.</p><p></p><p></p><p></p><p>hmm... should work... but, things don't always work the way you (me in this case) want them to.</p><p>At least I got you pointed in the right direction... 8-}</p><p></p><p></p><p>Yes... I noticed this too... but the remote mapping dialog in the the remote control plugin (external to the ExternalDisplay plugin) and I haven't had a chance to look into that problem yet.</p><p></p><p></p><p></p><p>Could you provide the mediaportal.log that I requested... I'm waiting on more data... Thanks.</p><p></p><p></p><p>Regards,</p><p>CybrMage</p><p></p><p></p><p></p><p>It was because I had assumed (from indications in the previous logs) that the data would come in bursts of 1, 2 or 3 bytes... and coded specific routines to take care the these cases on log the data... but I forgot to clear the data buffer after handling a 3 byte burst... so the next time the WhenDataReceived() routine was called, there was 4 bytes of data... then 6 bytes, etc... and the data handling routines were never executed with more than 3 bytes in the buffer... (Yes, I know... STUPID mistake... I'm only human...) </p><p></p><p></p><p></p><p></p><p>I'm looking at the log now... Thanks again... hopefully, I'll get this received data processing routine figured out this time.</p><p></p><p>Regards,</p><p>CybrMage</p></blockquote><p></p>
[QUOTE="cybrmage, post: 219671, member: 51680"] What stuff??? The character definitions?? I posted that I had figured it out.... One of your logs showed MHC displaying the clock.... once you posted a picture showing the clock, I was able to deduce that the 64 bytes of data in the 0xAD command was custom character data.... I then manually decoded the data into character maps, and correlated that into the data being sent by MHC for the clock display... and managed to get results that match the picture. What logo? I could be wrong... but I don't think so... Please explain why you think I'm wrong. hmm... should work... but, things don't always work the way you (me in this case) want them to. At least I got you pointed in the right direction... 8-} Yes... I noticed this too... but the remote mapping dialog in the the remote control plugin (external to the ExternalDisplay plugin) and I haven't had a chance to look into that problem yet. Could you provide the mediaportal.log that I requested... I'm waiting on more data... Thanks. Regards, CybrMage It was because I had assumed (from indications in the previous logs) that the data would come in bursts of 1, 2 or 3 bytes... and coded specific routines to take care the these cases on log the data... but I forgot to clear the data buffer after handling a 3 byte burst... so the next time the WhenDataReceived() routine was called, there was 4 bytes of data... then 6 bytes, etc... and the data handling routines were never executed with more than 3 bytes in the buffer... (Yes, I know... STUPID mistake... I'm only human...) I'm looking at the log now... Thanks again... hopefully, I'll get this received data processing routine figured out this time. 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
