How to manage string data in Version 6

Forum Home › Forums › Communicating with Devices › How to manage string data in Version 6

Tagged: 

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • December 2, 2022 at 11:04 am #11709
    AFP
    Participant

    Hello,

    Is it possible to manage string data coming directly from the devices in version 6 ?
    If yes, how can I use them in channel in order to have them showed as device data.

    Thank you

    December 2, 2022 at 2:12 pm #11710
    Mikhail
    Moderator

    Hello,

    It is possible in case a driver supports strings. Currently, the following drivers can provide string data: OPC UA and OPC Classic.
    What communication protocol and driver do you plan to use?

    December 2, 2022 at 2:28 pm #11712
    AFP
    Participant

    Hello Mikhail,

    Thank you for your reply.
    I’m using “MQTT Client” driver

    December 2, 2022 at 5:01 pm #11713
    AFP
    Participant

    Is it possible to do that with this driver ? Is a customization needed ? If yes, what would be the conditions ?
    This is very important and urgent for me…

    December 3, 2022 at 7:51 am #11714
    Mikhail
    Moderator

    Could you provide examples of the strings?
    Are they predefined constants? For example, “Status A”, “Status B”…

    December 3, 2022 at 8:25 am #11715
    AFP
    Participant

    No. They are not predefined.

    Following are examples of strings :

    Examples 1:
    F. F. F./ F. F. F.

    Examples 2:
    In Sw cl. Out Sw cl. M-By Sw op. By Sw op.

    Examples 3 ( the longest possible one ):
    Rectifier fault. Inverter fault. Auxiliary power fault. Fan fault. Input Thyristor failed. Invert Thyristor failed. bypass Thyristor failed. Fuse broken. DC BUS volt. abnormal. Initializtion fault. Battery Thyristor failed. Charger fault. Parallel fault. Parallel on invalid. DC component over limit. Mains Site Wiring Fault. Input Neutral line missing. Bypass Site Wiring Fault. Battery Reverse. No Battery. Feedback protection. Battery Fault. Battery temperature over. Overload. Parallel Overload. Battery under voltage. Battery over voltage. Battery low pre-warning. Mains freq. abnormal. Mains volt. abnormal. Bypass unable to trace. Bypass Not Available. Bypass over current. LBS Not SYNC. System Not Synchronized. Ext. Fire Alarm. Ext. Smog Alarm. Mains Abnormal. Battery under voltage. Bypass Output. UPS fault. Invert Output. UPS Power Integration Fault alarm. Over temperature. Transfer Times-out. ShutDown/Batt Low. UPS in Bypass/Overload. UPS in shutdown/Overload. Inv invalid/Overload. Inv Off/Overload. Inv Off/PowerOff. Bypass Supply Power. Rectifier Over Current. ByPass Switch Opened. Manu-Bypass Switch Opened.

    December 5, 2022 at 8:50 am #11720
    Mikhail
    Moderator

    For the example 3 you should create separate tags like
    – Rectifier fault
    – Inverter fault
    …
    They should not be strings.

    The feature of working with string tags may be added in the future version of the driver. I’ve added it to the wish list.

    December 15, 2022 at 11:02 am #11765
    Anonymous
    Inactive

    But unfortunately , I don’t see such details in the indicated topic.

    December 15, 2022 at 11:25 am #11766
    Mikhail
    Moderator

    You can read strings from OPC UA and OPC Classic. If you need to read a string, configure OPC driver and create channels using the Administrator tools. Channels for strings would be created by the wizard.

    December 15, 2022 at 11:27 am #11767
    Mikhail
    Moderator

    @palennt, send links to your screenshots to get more detailed recommendations.

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.