Search the Community
Showing results for tags 'momentum'.
Found 4 results
Morning Guys, For my latest project I need to read a gas sensor via 485 from a Momentum PLC. I've been through the help files, but they seem to only raise more questions than they answer, they only seem to reference PLC -> PLC comms. I've had a play with the 'MBP_MSTR' & 'OUT_IN_MBUS' function blocks, but i can't seem to get anywhere, Has anyone got any examples of reading in data via 485, or can anyone lead me in the right direction?
Hello, We have Modicon Momentum PLC and there is about 80 millions of Collision Errors (and growing cca 1.4 error per second) logged in Ethernet Statistics. In the manual they write only "This field should allways be 0". It is working for us though. We only have one problem that two machines on ADO 740 50 with ENT 110-01 stop simultaneously and irregularrly without any appearent reason. It is happening now for about 6 months, but I have calcluated that this collision errors accumulated over cca 2 years. My question is, what "Collision Errors" mean and could that by any chance make two particular machines on one ADO 740 50 module go off simultaneously?
I am struggling with the following problem: We have a Momentum PLC running with a project downloaded from Concept 2.6. When I make a small change into the project and I download the change to PLC there seems to be no problem. But when I try to run a visualisation project in Vijeo Look then after any click in visualisation the yellow triangles with red crosses appear over every object on the screen. We run OFS to enable communication between PLC and Vijeo Look. We use non-allocated variables in the project and probably the Visualisation does not work well with those unallocated variables after project changes. Can someone please describe steps which need to be taken to compile or upload a Concept project so that it works well in Vijeo Look with unallocated variables?
On Momentum PLC we have setup remote network modules as follows: On output modules with ADO 740 50 we have setup Last Value to Set to 0. Does it actually mean that the output value will be set to 0 in PLC memory immediately when PLC loses ethernet connection with the output module? We have setup hold up timeout on 170 ENT 110 01 on the remote side, but I am not sure how exactly the Concept parameters work with output remote modules. In the Concept documentation the process how Health Timeout and Last Value works is poorly documented. So the question is basically: How does Health timeout and Last Value parameters work in Concept Ethernet I/O Scanner with Momentum and remote output module ADO 740 50 with ENT 110 01? When timeout occurs in communication with output module ENT 110 01+ADO 740 50 and Last Value is configured to "Set to 0", does it mean that the output variable assigned to this remote module is set to 0 in PLC memory? If there are Timed out transactions on PLC with Health timeout expired, would that appear in Ethernet statistics on Momentum web page?