FF OPC read & write Mode Status

How do I read & write to a block Mode Status using the OPC server.  For example I thought that each (such as Actual, or Target, etc) would be a bit mapped byte with each bit representing a mode, but it does not seem to work this way.

You can get a block status by reading MODE_BLK.ACTUAL (type = uint8)
You can set a block status by writing MODE_BLK.TARGET (type = uint8)
For example, you can set a block to OOS by setting MODE_BLK.TARGET = 0x80.
If you find MODE_BLK.ACTUAL is 0x08, then it is in Auto.
The followings are the mode value description.
0) Value 1
Desc |en|ROut
Help |en|Remote Ouput Mode
1) Value 2
Desc |en|RCas
Help |en|Remote Cascade Mode
2) Value 4
Desc |en|Cas
Help |en|Cascade Mode
3) Value 8
Desc |en|Auto
Help |en|Automatic Mode
4) Value 16
Desc |en|Man
Help |en|Man
5) Value 32
Desc |en|LO
Help |en|Local Override Mode
6) Value 64
Desc |en|IMan
Help |en|Initialization Manual Mode
7) Value 128
Desc |en|OOS
Help |en|Out Of Service Mode

Similar Messages

  • To export query from Access to Excel in Read/Write mode in VBA

    Below is the code which exports the query named 'LatestSNR' from Access to Excel;
    Public Sub Expdata()
    Dim rst As DAO.Recordset
    Dim Apxl As Object
    Dim xlWBk, xlWSh As Object
    Dim PathEx As String
    Dim fld As DAO.Field
    PathEx = Forms("Export").Text14 'path comes from the directory given in form
    Set Apxl = CreateObject("Excel.Application")
    Set rst = CurrentDb.OpenRecordset("LatestSNR")
    Set xlWBk = Apxl.Workbooks.Open(PathEx)
    'xlWBk.ChangeFileAccess xlReadWrite
    Set xlWBk = Workbook("PathEx")
    Apxl.Visible = True
    Set xlWSh = xlWBk.Worksheets("Metadatasheet")
    xlWSh.Activate
    xlWSh.Range("A2").Select
    For Each fld In rst.Fields
    Apxl.ActiveCell = fld.Name
    Apxl.ActiveCell.Offset(0, 1).Select
    Next
    rst.MoveFirst
    xlWSh.Range("A2").CopyFromRecordset rst
    xlWSh.Range("1:1").Select
    ' selects all of the cells
    Apxl.ActiveSheet.Cells.Select
    ' selects the first cell to unselect all cells
    xlWSh.Range("A2").Select
    rst.Close
    Set rst = Nothing
    ' Quit excel
    Apxl.Quit
    End Sub
    After the execution of code, the query is transferred to excel sheet and is viewed in 'Read only' mode. If I try to save it, a copy of the excel file is produced. Can the Excel be opened in Read/Write mode ? so as to save the workbook and also to transfer
    the query to same workbook repeatedly.
    If in case the change of mode is not possible, then is there any alternative  method?

    Try this version:
    Public Sub Expdata()
    Dim rst As DAO.Recordset
    Dim Apxl As Object
    Dim xlWBk As Object, xlWSh As Object
    Dim PathEx As String
    Dim i As Long
    PathEx = Forms("Export").Text14 'path comes from the directory given in form
    Set Apxl = CreateObject("Excel.Application")
    Set xlWBk = Apxl.Workbooks.Open(PathEx)
    Set xlWSh = xlWBk.Worksheets("Metadatasheet")
    Set rst = CurrentDb.OpenRecordset("LatestSNR")
    For i = 1 To rst.Fields.Count
    xlWSh.Cells(1, i).Value = rst.Fields(i - 1).Name
    Next i
    rst.MoveFirst
    xlWSh.Range("A2").CopyFromRecordset rst
    xlWBk.Close SaveChanges:=True
    Apxl.Quit
    rst.Close
    Set rst = Nothing
    End Sub
    or else
    Public Sub Expdata()
    Dim PathEx As String
    PathEx = Forms("Export").Text14 'path comes from the directory given in form
    DoCmd.TransferSpreadsheet TransferType:=acExport, _
    SpreadsheetType:=acSpreadsheetTypeExcel12Xml, _
    TableName:="LatestSNR", _
    Filename:=PathEx, _
    HasFieldNames:=True, _
    Range:="Metadatasheet!"
    End Sub
    Regards, Hans Vogelaar (http://www.eileenslounge.com)

  • How to open a "manual" Physical standby database in read/write mode

    Hi,
    I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
    I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
    The standby database is started this way :
    startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
    alter database mount standby database;
    Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
    The thing is, if I shutdown immediate the database, then do just startup :
    shutdown immediate;
    startup;
    The database opens with no error messages, but is still in read-only mode...
    I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
    Thanks,
    Mat

    Hello,
    There're features which allows you to open a Standby database in Read/Write mode but for all I know
    it needs Entreprise Edition.
    In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
    a way by using flashback database so as to rolling backward the database and avoiding to recreate
    the Standby.
    In Standard Edition I'm afraid that you'll have to recreate your Standby database.
    Best regards,
    Jean-Valentin

  • ORA-22292: Cannot open a LOB in read-write mode without a transaction

    Hi ,
    somebody can help me, what is that problem.
    I run the script by using the Oracle SQL developer to update the clob column.
    error message is :
    ORA-22292: Cannot open a LOB in read-write mode without a transaction.
    Regards,
    Message was edited by:
    user533045

    Without posting the code its difficult for anyone to figure out whats wrong with this
    error.Please paste the code.
    Khurram

  • Clone Production Database and Convert into Read Write Mode

    Hi,
    Please help me for below question...
    How to Create Test Database from Production Database without transporting backup of Production Database to Test Database and the Test Database should be in different directory structure and converting into read write mode?
    Please find me a solution as early as possible...
    Thanks & Regards
    Akhil

    if you don't need to move backup from prod to dev you need to create rman catalog and have access on it from dev server , after that you will be able to duplicate your prod to dev without moving backup and database will be in Read write by default .

  • Mounting UDF formatted DVD+RW in read-write mode

    Hi folks,
    I'm having trouble getting Leopard to mount a freshly formatted UDF DVD+RW in read-write mode. It always seems to come up mounted read-only regardless of the options I give mount or mount_udf. I've tried default and 2.5 versions of UDF, specifying fix-packet when creating the volume, specifying -w on mount_udf, specifying -o w on mount, etc.
    The disc seems to be created okay, and shows free space..Just can't figure out how to use it. Any thoughts/working recipes? Example transcript follows..
    Thanks in advance,
    - Zanthrox
    scutter:~ doucej$ newfs_udf -v "Backup" /dev/disk1
    write to block device: /dev/disk1 last written block address: 2295103
    scutter:~ doucej$ mkdir /Volumes/Backup
    scutter:~ doucej$ sudo mount_udf -w /dev/disk1 /Volumes/Backup
    scutter:~ doucej$ df
    Filesystem 512-blocks Used Available Capacity Mounted on
    /dev/disk0s2 454819840 320448088 133859752 71% /
    devfs 213 213 0 100% /dev
    fdesc 2 2 0 100% /dev
    map -hosts 0 0 0 100% /net
    map auto_home 0 0 0 100% /home
    /dev/disk0s3 32905496 32284360 621136 99% /Volumes/Untitled
    /dev/disk1 9178360 572 9177788 1% /Volumes/Backup
    Looks good so far -- the volume was created fine, is readable, mountable, and shows free space..
    scutter:~ doucej$ mount
    /dev/disk0s2 on / (hfs, local, journaled)
    devfs on /dev (devfs, local)
    fdesc on /dev (fdesc, union)
    map -hosts on /net (autofs, automounted)
    map auto_home on /home (autofs, automounted)
    /dev/disk0s3 on /Volumes/Untitled (ntfs, local, read-only, noowners)
    /dev/disk1 on /Volumes/Backup (udf, local, read-only)
    scutter:~ doucej$
    ....but it still won't come up read-write, so I can't actually use it.

    If LVM has dropped write permissions on a volume or group then its probably for a good reason. You might want to look at the root cause for the failure and check /var/log/messages for any information.
    If you don't care about the data, you might be able to to bring back write access using
    <pre>
    lvchange --ignorelockingfailure -p w VolGroup00-LogVol14
    </pre>
    But like I said, there is probably a good reason why the volume is write protected in order to prevent further damage, or because of a underlying hardware issue.

  • Clone production db, & convert it to read write mode

    Hi Guys.,
    I'm having dba1 & dba2 server's , At dba1 there is my production database , Using this production database I want to create a new 'test' database
    "WITHOUT taking the BACKUP of MY production database."
    Note: I want to convert 'test' database to read write mode Too.
    please help me out with neat steps ,, Thanks in advance:-)

    If your database version is 11g R2 then you can use active database duplication as Hermant says.
    http://taliphakanozturken.wordpress.com/2011/06/26/creating-standby-database-with-rman-active-database-duplication-in-11gr2/
    Otherwise you need data pump export/import, transportable tablespace, etc to transfer your data.
    Talip Hakan Ozturk
    http://taliphakanozturken.wordpress.com/

  • Which table shows the tablespace in read-only mode or read-write mode.

    HI All,
    Can someonoe help me out to find which table shows whether the a tablespace is in Read-only mode or Read-write.
    Thanks,
    naveen

    Try this:
    select tbl.table_name, tb.tablespace_name, TB.STATUS from dba_tablespaces tb, dba_tables tbl
    where TB.TABLESPACE_NAME = tbl.TABLESPACE_NAME and TB.TABLESPACE_NAME = 'YOUR_TABLESPACE_NAME' and tbl.table_name = 'TABLE_NAME'

  • Read/Write mode in FileIO doesn't work?

    It seems it's not possible to both read from and write to a
    file in the same
    openFile session? I had the following code:
    fObj=xtra("FileIO").new()
    fObj.openFile(the moviePath & fName,0)
    fObj.writeString(fileString)
    fObj.closeFile()
    fObj=0
    fName and fileString are preset before this starts, but are
    not relevant to
    the issue. This code was working for saving existing files,
    but wouldn't
    create files if they didn't exist already. So I added the
    following:
    fObj=xtra("FileIO").new()
    fObj.openFile(the moviePath & fName,0)
    if fObj.readFile() = VOID then
    fObj.createFile(the moviePath & fName)
    fObj.openFile(the moviePath & fName,0)
    end if
    fObj.writeString(fileString)
    fObj.closeFile()
    fObj=0
    Basically, I'm checking and see if the file exists already or
    not. It opens
    it and reads it to see if there's anything there already. If
    not, it
    creates the file and opens it. This did the opposite, working
    fine on new
    files but wouldn't save data to existing files. So I had to
    add yet another
    chunk of code to make it work all around:
    fObj=xtra("FileIO").new()
    fObj.openFile(the moviePath & fName,0)
    if fObj.readFile() = VOID then
    fObj.createFile(the moviePath & fName)
    fObj.openFile(the moviePath & fName,0)
    else
    fObj.closeFile()
    fObj.openFile(the moviePath & fName,0)
    end if
    fObj.writeString(fileString)
    fObj.closeFile()
    fObj=0
    So if the file does exist, it has to close it and then open
    it again in
    order to write to it? I thought that mode 0 was supposed to
    be
    "Read/Write". So I should be able to both, but apparently not
    in the same
    session? Is there a better way to check if the file exists
    first? Seems
    like I'm using twice as much code as should be necessary to
    do this...

    > No, but strange as it seems, it does have to open it
    before it can delete
    > it.
    Not deleting anything just yet, only creating new or altering
    old.
    > Buddy API*, of course. :)
    > baFileExists(), baDeleteFile().
    Was afraid of that, I generally try to avoid adding Xtras to
    a project
    unless there's really no other way. I'm sure at some point
    Buddy API may be
    added to this project's Xtra list, but until I need to, I'm
    holding back a
    bit.
    > Is there any chance that you still have the file open?
    This can happen
    > during
    > authoring if the script stops for any reason before
    issuing closeFile().
    I'm almost certain that's not the case. I make a pretty
    strict habit of
    closing files as soon as possible after opening them -
    open-read-close or
    open-write-close. Since the program hasn't actually errored
    at all during
    this process, I can safely assume that the closeFile() is
    happening as it
    should.
    > But the real trick with fileIO is using both status()
    and error() (if
    > status
    > returns other than 0) after nearly every operation.
    I was trying to see what those did, but status() returned 0
    every time, even
    when it didn't do what it was supposed to. Error() I didn't
    check, but
    without a code to put into it, it doesn't seem like it'd do
    anything. The
    other one I was looking at was getLength() - presumably
    that'd return 0 for
    a non-existent file?
    > IIRC, the process for deleting a file without a 3rd
    party Xtra goes
    > something
    > like:
    Well, as I said I'm not deleting anything, so I don't think I
    need that yet.
    I think Stephen hit the nail though - it actually was
    writing, just in the
    wrong place.

  • How to share out web Documents folder in read/write mode

    I have a MacPro at work with Mac OS X 10.5.1 sitting on a network with a static IP address which is accessible via the Internet with few restrictions. This Mac does not use the built-in firewall; it is off. I regularly use my Mac at home to update a web site which I host on this Mac for a non-profit community group.
    What I am trying to do is set up the /Library/WebServer/Documents folder with this organization's president so he can update the web site himself. He has a Mac running Tiger. I created an account and set up file sharing and he can mount this folder on his desktop and see its contents; however, the Documents folder and every item in it are locked so no updates or changes can be made. When I check with Get Info, the Documents folder shows a lock symbol, but when I unlock it and use the option to apply the change to the folder's contents, then close the Get Info window and open it again, the lock is activated again. He and I are the only ones with permissions to alter these files, and I don't have a lock on them. How can I remove the lock so my co-webmaster can update the files?

    Unfortunately, his Mac is not local to me. I would have to drive about 30 miles each way, which is not too bad, but I won't have time to do it for a couple of weeks and I am hoping an easier solution can be found without me having to drive, especially since if the problem is on my end, that trip would be a waste of time for both of us.

  • Error message - this project cannot be opened in read-write mode because a previous checkin for this project is not complete.

    Hi,
    I have read the previous posts about this error message and I have tried all resolutions suggested but to no avail.
    This week 4 Project Managers have reported this error message to me. Each time I have checked the Force Check-In Enterprise Objects, the queue and also the cache. None of the projects can be found anywhere. This is obviously frustrating for them and for
    myself.
    If anyone has any advice on where to find these project and check them in properly, and also how to avoid this happening going forward, I would be greatful.
    Thanks,
    Clair.

    Clair --
    Did you look at the local project Cache on the PC of each of the affected users?  Did you ask the affected users to clean out their Cache and try to open each project directly from the Project Server database, instead of opening it from the Cache?
    There is a possibility that the Cache has gotten corrupted on the PC of each of your affected users.  To resolve possible Cache corruption, ask each of the affected users to do the following:
    1.  Close Microsoft Project 2010.
    2.  Click the Start > All Programs > Accessories > Run.
    3.  In the Run dialog, enter the following command:
         %appdata%\Microsoft\MS Project\14\Cache
    4.  Click the OK button.
    Please let us know if this helps.
    Dale A. Howard [MVP]

  • ORA-22292: Cannot open a LOB in read-write mode without a transaction ORA-06512

    I'm trying to do an update of a clob, and have come up against this error. all similar posts i can find on this site mention the not locking the record before the update...
    cheers in advance :-)

    Set it to Required. The bean will join a transaction if one is started or start a new one if not.
    /Mattias

  • Whats the power consumption in standby and read/write mode on the Hitachi HTS545032B9A302 ?

    Hello, im about to but an ssd and dont want to pick a drive with more energy consumption to reduce the battery time so i wonder if someone knows the conumption for the Hitachi HTS545032B9A302 drive on the new macbook pro or in worst case if someone dares to approximately guess the consumption in W(Watt)

    Does the hard drive label say 5V 700ma?
    You might look at the Hitachi spec sheet for the A300/A301's, which have the same power specs: http://www.hitachigst.com/tech/techlib.nsf/techdocs/FFA370A7BF845F87862574FE0003 054C/$file/TS5K500B_DS_final.pdf

  • Select in read only transaction mode / insert in write mode

    hello,
    i have a following question: i have 2 db, one is rdb and one oracle
    im extracting data out of table out of rdb and inserting them into oracle via OWB;
    however this is run in read-write mode and causes locks in rdb; the only way to prevent locks is to run a select statement that accesses rdb in 'read only' transaction mode;
    my question is: is this possible to split up the select and insert statements of oracle into 2 different transaction modes, so that select statement is run in 'read-only' mode and insert in 'write' mode?
    i appreicate tips on how this could be achieved
    thx
    rgds

    Hello,
    is this something like:
    insert into oracle_table (select * from rdb_table@rdb_link);
    Then it is easy, you just need to use an sql init file for your OCI Service. Create a file, e.g. sql_init.ini that contains this line:
    declare transaction read only;
    Then alter your service so that it sees the sql init file, e.g.:
    SQLSRV> alter service <your OCI service> sql_init_file sql_init.ini
    The service owner must have the privileges to read the file. You need to restart the OCI service.
    Then a statement of the above kind results in a read only transaction on Rdb side, and the insert on Oracle side is done.
    I hope your SQL/Services version is a recent one (actual version is 7.3.1), because of this (from the SQL/Services Release Notes 7.2.0.1):
    5.4.25 Declare Transaction in SQL Init File Being Overridden
    In releases of OCI Services for Oracle Rdb prior to 7.2.0.1, if a DECLARE
    TRANSACTION statement was executed in the SQL initialization file of a service, it would
    be overridden by a DECLARE TRANSACTION statement executed later by OCI Services
    for Oracle Rdb. Toward the end of the connection setup, OCI Services for Oracle Rdb would
    execute a DECLARE TRANSACTION statement to set the default transaction
    characteristics to be close to Oracle default transaction characteristics. This would supersede
    any DECLARE TRANSACTION statement in the SQL initialization file. Starting with
    release 7.2.0.1, OCI Services for Oracle Rdb recognizes that a DECLARE TRANSACTION
    statement has been executed and will not execute another one.
    Regards
    Wolfgang
    P.S.: It is always better to place Rdb related questions in our communities at https://communities.oracle.com/portal/server.pt/community/rdb_product_family_on_openvms . Those are watched by Rdb Engineering and Support. It was by pure chance that I saw this forum thread.

  • Unable to open database in READ ONLY mode

    When trying to open database in READ ONLY MODE it says needs recovery. How ever database opens succesfully in READ WRITE MODE.
    1) Startup mount
    2) SQL> ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ ONLY
    ERROR at line 1:
    ORA-16005: database requires recovery
    But database opens succesfully when opened in READ WRITE mode.

    user12038051 wrote:
    When trying to open database in READ ONLY MODE it says needs recovery. How ever database opens succesfully in READ WRITE MODE.
    1) Startup mount
    2) SQL> ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ ONLY
    ERROR at line 1:
    ORA-16005: database requires recovery
    But database opens succesfully when opened in READ WRITE mode.
    sqlplus '/as sysdba'
    shutdown imediate;
    startup;
    shutdown imediate;
    startup mount;
    recover database;
    alter database open read only;

Maybe you are looking for