[TCUG] Re: Lamp Monitoring of LED Heads on Siemens RMS

  • From: "Morar Jag \(ST\)" <Jag.Morar@xxxxxxxxxx>
  • To: <tcug@xxxxxxxxxxxxx>
  • Date: Fri, 18 Jul 2008 13:48:20 +0100

Robert,

The Siemens RMS lamp monitoring is designed for conventional lamp
monitoring through the torroids at  the phase outputs. Conventional
current monitoring of 240v LED optics at the controller is difficult, if
not impossible, due to the very low and irregular current profile and
harmonics from the switched mode supply. This is probably why TSEU
provide sense wiring from the monitoring that is done directly on the
optic. However, I also  suspect the OMU does not have software that is
designed to report lamp faults using such inputs.

However, I believe lamp current monitoring of LED aspects should become
easier when we move to ELV operation - as see on the Siemens ST900 ELV
controller.

Jag Morar=20
Transport for London
Directorate of Traffic Operations
25 Eccleston Place=20
London=20
SW1W 9NF=20
0207126 2754=20
Please note my new email address: jag.morar@xxxxxxxxxx=20






-----Original Message-----
From: tcug-bounce@xxxxxxxxxxxxx [mailto:tcug-bounce@xxxxxxxxxxxxx] On
Behalf Of Robert Mansell
Sent: 17 July 2008 15:41
To: tcug@xxxxxxxxxxxxx
Subject: [TCUG] Lamp Monitoring of LED Heads on Siemens RMS


When installing a Siemens RMS OMU into a non-Siemens controller, you
would normally fit torroids to perform lamp monitoring. Our new sites
are now installed with LED signals, has anyone any experience of how RMS
copes with monitoring LEDs? Specifically, we have Microsense LED Signal
Heads, the type that use a sense wire for monitoring the reds, the newer
3G TSEU signal heads and also Peek Elite LED.

Thanks

Robert Mansell

The City of Edinburgh Council


************************************************************************
This email and files transmitted with it are confidential and are
intended for the sole use of the individual or organisation to whom they
are addressed. If you have received this eMail in error please notify
the sender immediately and delete it without using, copying, storing,
forwarding or disclosing its contents to any other person. The Council
has endeavoured to scan this eMail message and attachments for computer
viruses and will not be liable for any losses incurred by the recipient.
************************************************************************


-- Binary/unsupported file stripped by Ecartis --
-- Type: application/ms-tnef
-- File: winmail.dat


-----------------------------------------------------------
A message from the TCUG mailing list. For information about
the list visit //www.freelists.org/webpage/tcug

***************************************************************************=
********
The contents of the e-mail and any transmitted files are confidential and i=
ntended solely for the use of the individual or entity to whom they are add=
ressed. Transport for London hereby exclude any warranty and any liability =
as to the quality or accuracy of the contents of this email and any attache=
d transmitted files. If you are not the intended recipient be advised that =
you have received this email in error and that any use, dissemination, forw=
arding, printing or copying of this email is strictly prohibited., If you h=
ave received this email in error please notify postmaster@xxxxxxxxxxx, This=
 email has been sent from Transport for London, or from one of the companie=
s within its control within the meaning of Part V of the Local Government a=
nd Housing Act 1989. Further details about TfL and its subsidiary companies=
 can be found at http://www.tfl.gov.uk/ourcompany, This footnote also confi=
rms that this email message has been swept for the presence of computer vir=
uses.
***************************************************************************=
********

-----------------------------------------------------------
A message from the TCUG mailing list. For information about
the list visit //www.freelists.org/webpage/tcug

Other related posts: