Search results

I dont understand where your issue could be. I setup a new project and added the script/variables and it works fine? Attached is a copy of my test project (V6.2 SP8)

sorry forgot to make the change to the script after cut/paste. You are not specifying the index in the data write your for loop should be IP.IPaddr.write( data );

You appear to be trying to write the entire data array into IPaddr and don't appear to be using the index i anywhere Variable IPaddr need to be defined as an array of 4 integers Then correct syntax would be int [ ] data = ModbusEquipment01.getProperty( "Con_IPAddress" ); for( int i = 0; i <...

David, You no longer setup IO Scanning in Unity in the "Ethernet" folder for a M580, you need to use DTM browser. The following youtube video shows the basics Configuring IO Scanning on M580 in Unity Pro

Have you checked that none of the .ndx files have been marked "read only" and/or the logged in user has permissions on the project directory?

David, the 170ENT11001 Ethernet adapter should communicate with the M580 (or any other Modbus/TCP master). Are you able to login to the embedded web server? if so does the diagnostic page show the modules is running (this will also show the valid I/O registers)

Clint KV, I know this is a bit late (but only just joined forums) but may help someone else. I have had a similar issue with Citect, turned out SQL had filled the hard drive, hence Citect can't open the dbfs to generate the compiled files. Freeing up some space then re-compile and everything...

Callistro, Yes it is possibly firmware issue When you configured hardware, which OS version did you choose? If it is an older CPU it may have out of date firmware. If you right click on "Momentum Bus" in the configuration and select "Replace Processor", select the "show all versions" option...

I haven't used Intouch HMI specifically but I have used the UnityPro Simulator successfully with physical HMIs (Magelis) and CitectSCADA on another PC or seperate VM - I cant see how Intouch HMI would be any different. I assume you are using Modbus/TCP or Ethernet/IP. I've even had one...

Callisto, I think there is a little confusion in your addressing of the zone status addressing. If you look at the CPU Configuration page, by default the state ram is allocated 1536 memory bits (%M), you are trying to use locations 10032 and above. Unless you are thinking of Modbus addressing...