Other than some initial issues on the 196 when they took over from Arriva, I'm yet to actually have issue with HTL's level of service with the Sprinters being the only real exception for the reason St Helens Rider gives above.
Is Merseytravel's stance with LED's standard practice across the industry , I'm not sure why TfL seems to favour Roller Blinds .
Until the industry falls one way or another you'll always have this argument .
(27/06/2013 09:18)wirralbus Wrote: [ -> ]Is Merseytravel's stance with LED's standard practice across the industry , I'm not sure why TfL seems to favour Roller Blinds .
Until the industry falls one way or another you'll always have this argument .
Merseytravel don't have a policy about LED's that makes all of it's operators use them unlike TFL, It's purely down to operator choice.
In the long run they don't cost anything to add or remove destinations, you can program them to say whatever you want, they do not fade, they can be seen easily day and night, and you can program scrolling text saying whatever you want, even images, and thus have become industry standard.
The only real downside to them is that they require power, and someone trained in computer software to program them and the initial cost.
Regarding their visibility, in bright sunlight, I've struggled to see them before and although I don't usually have an issue with reading the LEDs, roll blinds do still seem clearer to me.
(27/06/2013 20:58)CX54 DKD Wrote: [ -> ]Regarding their visibility, in bright sunlight, I've struggled to see them before and although I don't usually have an issue with reading the LEDs, roll blinds do still seem clearer to me.
It depends on the light intensity of the blind most of the time (2229 is a good example where half the blind is lower then the rest and harder to see), The brighter the LED's, the clearer the blind (but more power consuming), Halton's are very unclear to see with the likes of the mylleniums, as are some of cumfybus's older solos, but that's what happens when you buy cheap equipment, it tends to break faster and give poorer results!
We are in an age where technology is becoming more advanced, The powerblind is like the Windows 95 of computers, and if it wasn't for the likes of TFL and Lothian, it is highly likely to be a thing of the past, just like it would be
near impossible to buy a brand new bus with bench seats or roller blinds.
(27/06/2013 21:54)Raawwwrrr! Wrote: [ -> ]It depends on the light intensity of the blind most of the time (2229 is a good example where half the blind is lower then the rest and harder to see), The brighter the LED's, the clearer the blind (but more power consuming), Halton's are very unclear to see with the likes of the mylleniums, as are some of cumfybus's older solos, but that's what happens when you buy cheap equipment, it tends to break faster and give poorer results!
Yes, that explains it. I find the LEDs on most of the Darts particularly easy to pick out in St Helens whereas those on the B10s and Pulsars can be particularly difficult to read in bright sunlight. There was a Marshall running around here with the same style issue that you describe for 2229 some time ago too.
In regards to LED screens, Dart MPD SN06 BMO was out today on route 173/4 with a green front LED destination screen!
This one has had a replacement engine too (SN51 TDU being the donor) and it also had a proper Dennis badge (pre 1999 style with the triangles top and botton) on its rear bumper too!
Thank goodness BMO has finally had a new screen. There's one of the Solos which had been operating the 147/196 quite regularly (MOF perhaps?) which needs a replacement screen too. I assume the green LED is one that has been spare at HTL? I'm sure I've seen it in one of their vehicles before...
At a guess the green screen has come from one of the older S reg Darts as they had them - not absolutely sure however!
There is a Solo with a faulty front LED screen (it isn't MOF though!) but I think this is getting it sorted ASAP as well!
Ive seen a few "173 Sefton Par" around over the last few weeks i thought this had been fixed!