Another short update on the cluster LCD repair
02-11-2006, 12:49 PM
#1
Another short update on the cluster LCD repair
Hi everybody. Just wanted to let you know how things are going with the cluster lcd replacement.
The good:
I have found a screen that is almost the same as size as the original and has a white el backlight. It has double the resolution of the original screen across both axes which makes it suitable for integrating other gimmics in the control module.
The bad:
The dashboard microprosessor doesn't do any busy checks on the lcd screen and there is only 1 micro second delay between bytes of data. This makes it really hard to capture the data and convert it. I have tried processors as fast as 48 Mhz (which is pretty big for a small embedded controller) and they were not able to keep up capturing the data, by the time the interrupt routine that reads the byte returns, it's too late, one data cycle from the dashboard was missed.
This is the only problem that's left to be fixed and this will work. My big problem is time: i am taking 16 credit hours and i am close to graduation so i will have to postpone this a bit. I might work on it during the spring break if i can get an appropriate board (one with DMA) by then... if not i will only resume work on this project at the end of April when the semester ends.
This is my last post from the "update" series and the only next post will be one that says "Problem fixed".
Thanks everybody for the support!
The good:
I have found a screen that is almost the same as size as the original and has a white el backlight. It has double the resolution of the original screen across both axes which makes it suitable for integrating other gimmics in the control module.
The bad:
The dashboard microprosessor doesn't do any busy checks on the lcd screen and there is only 1 micro second delay between bytes of data. This makes it really hard to capture the data and convert it. I have tried processors as fast as 48 Mhz (which is pretty big for a small embedded controller) and they were not able to keep up capturing the data, by the time the interrupt routine that reads the byte returns, it's too late, one data cycle from the dashboard was missed.
This is the only problem that's left to be fixed and this will work. My big problem is time: i am taking 16 credit hours and i am close to graduation so i will have to postpone this a bit. I might work on it during the spring break if i can get an appropriate board (one with DMA) by then... if not i will only resume work on this project at the end of April when the semester ends.
This is my last post from the "update" series and the only next post will be one that says "Problem fixed".
Thanks everybody for the support!
repares to bow to you:: I feel your pain with the credit hours, 18 here at Pitt, senior next yr.
02-11-2006, 04:01 PM
#5
AudiWorld Super User
Join Date: Dec 2005
Posts: 2,616
Likes: 0
Received 0 Likes
on
0 Posts
Ahhh. Quite your crying... I worked a full time+ job with a family and got an MBA in one year. :-P
Quit drinking and start studying! Oh yea... I didn't have the S4 then either. had a 540 but it wasn't quite the addictive bitch that this thing is.
Good luck with school-
Good luck with school-
)
