manjey73

Forum Replies Created

Viewing 15 posts - 481 through 495 (of 888 total)
  • Author
    Posts
  • in reply to: Device channels not reconized in v6 #10600
    manjey73
    Participant

    You must have a communication line set up in the Communicator to be able to use the Channel Creation wizard. In the window, you select a line, a device, and you should be shown how many channels will be created. After that, you transfer the configuration to the server and restart it.

    in reply to: Plug in charge #10574
    manjey73
    Participant

    License keys are linked to a PC, so there is no need to purchase them on the PC where you are developing the project, and to purchase them only on the desktop PC where the project will work. Test keys are created until the end of the next day and you can use it if you need to test on different PCs.

    in reply to: GetBit Error #10573
    manjey73
    Participant

    Val(106) – Channel value number 106
    106 is just a channel number, you will always receive a bit from the number 106, and converted to double by the system beforehand

    If you need only one bit from the incoming signal, and you are not interested in the number itself and other bits, then you can simply use the GetBit(Cnl, 0) formula in the input channel without resorting to calculation channels

    in reply to: Administrator Chiannels #10572
    manjey73
    Participant

    The command number is the number that is obtained as a result of configuring the Modbus template command, for example, you specified a register entry command and a number 1 or 2 was created for it, this is the number you specify in the control channel (output channel) The output channel number can be arbitrary and you refer to it in the input channel thus creating a link. Switch to version 6, it now has one channel, just specify its type Input, Input/Output, Output

    in reply to: Send command button – change register bit #10570
    manjey73
    Participant

    If the setBit formula has already been added to the database, it allows you to change the bit to both 0 and 1

    SetBit(Val(101), 2, Cmd)

    When transmitting 0, bit number 2 will be reset, when transmitting 1, bit number 2 will be set. The remaining bits of the channel will not be changed

    in reply to: Send command button – change register bit #10568
    manjey73
    Participant

    @victorlam In this case, in the existing channel 101, you change the 2nd bit to 1 if it was zero, or it remains 1 if it was in 1 and you write 0

    | – or
    << 2 – Shift the zero bit by 2 positions

    That is, this formula is only for setting the 2nd bit to 1

    • This reply was modified 3 years, 5 months ago by manjey73.
    in reply to: Rapid SCADA 6 Beta #10567
    manjey73
    Participant

    There are a lot of changes in the kernel. Especially when working with archives. The ability to use PostgreSQL as the main database instead of the internal one. Accessing variables by tag code. Removal of restrictions on 65 thousand channels. And apparently much more… If it is possible to upgrade to version 6 or start, then it is better to do so.

    in reply to: Plug in #10566
    manjey73
    Participant

    The long computer code may be related to the number of network interfaces, if you use Virtualbox or similar programs and run virtual machines, the composition of network interfaces will change. This may be related to the problem of the key operation. Ask the developer to make you a key to the real network card of the computer in this case.

    in reply to: Device channels not reconized in v6 #10557
    manjey73
    Participant

    “Code” is needed

    in reply to: Modbus RTU Device with RS485 to IP converter #10535
    manjey73
    Participant

    The mode should be Modbus RTU, but the communication line setup should be TCP/IP with the port specified from the converter settings. At the same time, the device Address = 1 must be specified in the device settings

    in reply to: AllenBradley PLC Polling Driver (Ethernet) #10412
    manjey73
    Participant

    @manyan2028 127.0.0.1 this is the local IP of the machine, not the IP of the PLC
    502 the port is a Modbus port and not a port for the Ethernet/IP protocol, by default the port should be 44818

    This is according to your screenshot from the mail. Read carefully how the Allen Bradley PLC is polled and exactly how you want to poll it, via Modbus, if it has such an opportunity, or still via Ethernet/IP

    in reply to: Gateway #10331
    manjey73
    Participant

    Does your gateway work over Modbus TCP ? Has a port for access, for example 502 ? Perhaps you are requesting an address that is not in the gateway variables

    in reply to: Entering number from browser #10254
    manjey73
    Participant

    use Formula SetVal

    Look in the documentation how to use it correctly

    in reply to: Monitoring Panel #10071
    manjey73
    Participant

    Use Autologin for version 5

    in reply to: Sending Command Skipped #10064
    manjey73
    Participant

    I may be wrong, but in this case, the trigger should be set to the channel status and apply formulas that change the status.

Viewing 15 posts - 481 through 495 (of 888 total)