These were the usual things as recommended by the programming manual. This message instruction was enabled by the dn bit of a self resetting timer every 500milliseconds Through the setup screen, I made a data file MSG_9, and set up the received data to land in another data file N10:0 onwards for 10 integers. I used the Message read instruction (MSG with Modbus function for reading registers). VSD_comms_via_modbus.RSSĪttaboy Bob Coincidentally, today I was struggling to rig up 3 energy meters with Modbus ports configured to talk with ML 1100 with its Channel0 set as Modbus master with matching baud-rate and parity etc. I have to state here that my experience with message instruction programming is limited, so i ask that if anyone has time to look at my logic and make comment ( good or bad ) as to whether it will work, i would be grateful for any feed back. I have modified the existing logic to what i believe will eliminate the message instruction being able to become stuck in an error state. From what i have read I believe that this is what is required to reset an error state. I have spent some time watching the logic to see if i could work out why the logic was not resetting the error, I found that in some situations the logic was not able to trigger the message instruction FALSE to TRUE to reset the error.
If the MSG destination is an INTERCHANGE client on a host computer, the destination is specified as “client” and stored as a NULL terminated string.Hi Guy's I have an existing system that controls X number of VSD via modbus comms, the logic is event driven message instructions, the logic works fine 90% of the time but on occasions one or two of the message intructions become stuck in an error state and will not reset.This requires the power to be cycled on the processor to clear fault. For example: If the IP Address is 423.156.78.012, the first byte is the ASCII character “4”. The first byte in the array is the left-most character in the string as written. The IP Address string format is up to 42 ASCII characters including a terminating NULL character. Reserved (Ethernet Message Type) must be 0 MSG Control Block without Logical ASCII Addressingįile Type (based on local source or destination address) With logical ASCII addressing, the length of the control block is 93 words. The length of the control block without logical ASCII addressing is 51 words.
The following are MSG control blocks, without and with logical ASCII addressing.
0 kommentar(er)
