Re: [foxboro] FBM204 failed to be recognized by system
- From: "Jason.LJZ" <jason.ljz@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Sun, 22 Jan 2012 08:40:21 +0300
You are right. It display BAD I/O. When I source it with Altek. the
Altek just indicates that the loop is open.
When I set AOUT=50% and measure the AOUT channel, multimeter read zero.
I suspect that it could be a hardware error. I mean probably the FBM204
is bad.
I have tried it with another empty slot, another new type I cable. But
nothing changed.
But I don't have another FBM204 in hand, so I can't confirm if it's
FBM204 problem.
Later, I will try it, and if found the answer I will send a mail to list.
Thank you all. It's so good to have you all.
PS: My mail system marked the subject with a SPAM, so I send the mail again.
于 2012-1-19 16:41, Dan Butler 写道:
> Jason - What are the raw counts in the AIN detail display? If you are
> bringing in the 4-20 with a SCI of 3 and your OSV (over scale) is less than
> 25% you will see an out of range, or Bad I/O with 0mA coming in. Can you
> source in a 4-20 with an Altek or similar device?
>
> Dan Butler
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Jason.LJZ
> Sent: Wednesday, January 18, 2012 10:37 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [SPAM] Re: [foxboro] FBM204 failed to be recognized by system
> Importance: Low
>
> I will try another cable. Actually, the cable we used is really in mess after
> transportation.
> I also doubted it but didn't suppose it could be damaged easily.
>
> Thanks.
>
> 于 2012-1-18 20:01, Landry, Scott 写道:
>> Sounds like the t/a and/or t/a cable is bad or the wrong type
>>
>> ________________________________________
>> From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On
>> Behalf Of Dirk Pauwels [dirk.pauwels@xxxxxxxxxx]
>> Sent: Wednesday, January 18, 2012 10:59 AM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: Re: [foxboro] FBM204 failed to be recognized by system
>>
>> Did you try delete and undelete?
>> Did you try to delete the FBM in the CP60_ECB and create it again?
>>
>> If you created the FBM ECB's long time before you physically entered
>> the fbms it might be necessary to re-create them
>>
>> Rgds,
>>
>> Dirk
>> -----Original Message-----
>> From: foxboro-bounce@xxxxxxxxxxxxx
>> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Jason.LJZ
>> Sent: Wednesday, January 18, 2012 2:49 PM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: Re: [foxboro] FBM204 failed to be recognized by system
>>
>> I am sure we have set the
>>
>> IOMOPT = 1
>> IOM_ID
>> SCI=3/SCO=3
>>
>> etc. correctly.
>>
>> Thanks for your precious time and reply.
>>
>> 于 2012-1-18 16:29, Dirk Pauwels 写道:
>>> Q1: If your FBM is online and on scan it should be ok I guess
>>> Q2: not that I know off, we have plenty of them and can't remember we
>>> had problems during install
>>> Q3: Did you enter the IOM_ID and point nr?
>>> IOMOPT = 1?
>>> Did you enter the SCI=3/SCO=3?
>>>
>>> Rgds,
>>> Dirk
>>>
>>> -----Original Message-----
>>> From: foxboro-bounce@xxxxxxxxxxxxx
>>> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Jason.LJZ
>>> Sent: Wednesday, January 18, 2012 11:28 AM
>>> To: foxboro@xxxxxxxxxxxxx
>>> Subject: [foxboro] FBM204 failed to be recognized by system
>>>
>>> Dear all,
>>>
>>> I just ran into a problem: we need to add a FBM204 to our system, which is
>>> I/A 7.0 with 4 pairs CP60 and six AW51/WP51(Sun Blade 150) stations.
>>>
>>> Before we added the FBM204, the system has no other FBM204 installed. We
>>> added a ECB2 and configured it as HWTYPE=204, SWTYPE=2. AIN and AOUT were
>>> added and configured.
>>>
>>> The status of ECB2 was ONLINE and ON_SCAN.
>>>
>>> The problem is when we checked the AIN and AOUT block, the AIN block was
>>> indicated as BAD I/O even the transmitter outside worked normally. When we
>>> set output of AOUT as 50%, no milliampere can be measured.
>>>
>>> We also added a FBM241C to our system, and it works fine once it was added.
>>> The difference is there are FBM241C already used in system.
>>>
>>> My question is:
>>>
>>> 1. Does it matter that there are same type FBM already installed in system?
>>> So the newly added modules can be recognized by system?
>>>
>>> 2. Is there any thing special about adding FBM204 to system?
>>>
>>> 3. What can I do to probably solve the problem?
>>>
>>> Thanks in advance for your precious time for reading this and any help is
>>> appreciated.
>>>
>>>
>>> _____________________________________________________________________
>>> _ _ This mailing list is neither sponsored nor endorsed by Invensys
>>> Process Systems (formerly The Foxboro Company). Use the info you
>>> obtain here at your own risks. Read
>>> http://www.thecassandraproject.org/disclaimer.html
>>>
>>> foxboro mailing list: //www.freelists.org/list/foxboro
>>> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>>> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>>>
>>>
>>>
>>> _____________________________________________________________________
>>> _ _ This mailing list is neither sponsored nor endorsed by Invensys
>>> Process Systems (formerly The Foxboro Company). Use the info you
>>> obtain here at your own risks. Read
>>> http://www.thecassandraproject.org/disclaimer.html
>>>
>>> foxboro mailing list: //www.freelists.org/list/foxboro
>>> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>>> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>>>
>> ______________________________________________________________________
>> _ This mailing list is neither sponsored nor endorsed by Invensys
>> Process Systems (formerly The Foxboro Company). Use the info you
>> obtain here at your own risks. Read
>> http://www.thecassandraproject.org/disclaimer.html
>>
>> foxboro mailing list: //www.freelists.org/list/foxboro
>> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>>
>>
>>
>> ______________________________________________________________________
>> _ This mailing list is neither sponsored nor endorsed by Invensys
>> Process Systems (formerly The Foxboro Company). Use the info you
>> obtain here at your own risks. Read
>> http://www.thecassandraproject.org/disclaimer.html
>>
>> foxboro mailing list: //www.freelists.org/list/foxboro
>> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>> *** Confidentiality Notice: This e-mail, including any associated or
>> attached files, is intended solely for the individual or entity to which it
>> is addressed. This e-mail is confidential and may well also be legally
>> privileged. If you have received it in error, you are on notice of its
>> status. Please notify the sender immediately by reply e-mail and then delete
>> this message from your system. Please do not copy it or use it for any
>> purposes, or disclose its contents to any other person. This email comes
>> from a division of the Invensys Group, owned by Invensys plc, which is a
>> company registered in England and Wales with its registered office at 3rd
>> Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For
>> a list of European legal entities within the Invensys Group, please go to
>> http://www.invensys.com/en/legal/default.aspx.
>>
>> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
>> reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be
>> subject to the terms of any agreements between Invensys (and/or its
>> subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
>> affiliates).
>>
>>
>>
>>
>> ______________________________________________________________________
>> _ This mailing list is neither sponsored nor endorsed by Invensys
>> Process Systems (formerly The Foxboro Company). Use the info you
>> obtain here at your own risks. Read
>> http://www.thecassandraproject.org/disclaimer.html
>>
>> foxboro mailing list: //www.freelists.org/list/foxboro
>> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at your
> own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
