Toshiba 20vl66 LCD IR control
Darkside
Posts: 345
Hi all,
Hoping someone may have played around with this 20" lcd screen...
The hand control only has a toggle control for power, and it appears that no other button will turn it on (sometimes a channel button might bring a device on).
We have a sys with a shipload of these screens in it and sometimes the screen does not turn on - either because it missed it, or the data got bumped into on the way etc. It is random across the 40 screens and random as to when it might do it.
I wondered if anyone would know if any other Tosh device will operate this screen, and if so, does that remote have discrete on off. (Wondering if say a tosh cube remote might fire the lcd)
It's a long shot, but with the wealth of knowledge and help here, I hope I might find a solution!
Any help gratefully received
Hoping someone may have played around with this 20" lcd screen...
The hand control only has a toggle control for power, and it appears that no other button will turn it on (sometimes a channel button might bring a device on).
We have a sys with a shipload of these screens in it and sometimes the screen does not turn on - either because it missed it, or the data got bumped into on the way etc. It is random across the 40 screens and random as to when it might do it.
I wondered if anyone would know if any other Tosh device will operate this screen, and if so, does that remote have discrete on off. (Wondering if say a tosh cube remote might fire the lcd)
It's a long shot, but with the wealth of knowledge and help here, I hope I might find a solution!
Any help gratefully received
0
Comments
I suggest that you should doubt that the behaviour is random, and go find what factor makes a difference. In my (humble) experience the most likely reason for random behaviour of an IR controlled device is that the pulse length is too short - or possibly too long.
I am also puzzled about "the data got bumped into on the way" and would appreciate some details on that.
I strongly suspect the run lengths are an issue here - not the code - and that it may well be a sagging power supply issue coupled with, perhaps, some deforming of the burst shapes over these distances. This is why I would like to get a discrete ON so that the cmd can be issued again as a safety. I have already tested for min pulse time and it appears to not like a pulse time of 3 very much (over these distances), so have left it at 5. I haven't considered that 5 is too short.
The handler for the screens is very tightly controlled and what cmd any screen gets and when it gets it is extremely strict. There have been reports of totally random screens simply not doing as they are told. Sometimes it is days before it occurs. At this early stage it would appear that we haven't even had the same ones misbehaving twice.
Spikes, large RF emissions from plant rooms etc. Kitchen devices kicking in etc can all 'bump into transmissions' causing corruption of serial/ir data if large enough. Perhaps I should have just said splatter the data!
Cables shouldn't be close to these sorts of animals in a perfect world - of course - but, .....were not in a perfect world!
The cable type used for the ir tx will allow us to implement the screen to help reduce this risk. We'll probably do this as a matter of course in this case.
As for the current sensors, yes it would be a huge cost, and, IMHO they are not well suited to this type of device.
Thanks for the input!