pturmel
MrPLC Admin-
Content count
759 -
Joined
-
Last visited
Posts posted by pturmel
-
-
11 hours ago, VFD Guy said:find an old hub or use a sniffer is the easiest
No question about that at all. But I am often not on-site, so a port mirror that can be configured remotely has great value. And, sometimes, simply moving connectors masks a problem.
-
10 hours ago, Joe E. said:downstream devices go away
Primarily.
10 hours ago, Joe E. said:another reason too?
Troubleshooting problems in cases like this. Most modern managed switches have features to help technical staff connect wireshark to specific ports, so that sources of bad behavior can be examined unfiltered, and without relying on an intermediate two-port switch.
Actual DLR, though, is awesome.
1 person likes this -
Wireshark can only capture packets that arrive at the PC's physical network interface. That often requires using a special mode on your switch to "mirror" everything to the PC's port, and ensuring that all devices are connected to the switch. You will not be able to capture traffic from daisy-chained devices. (The dual ports on AB devices should only be used for real rings.)
The mode problem suggests that the device in question is "owned" by something. What are these devices? Please also show your Studio 5000 I/O device tree where Device1 and Device2 are present.
-
6 hours ago, Yahya said:heartbeat function have to be created manually?
I would make it precisely to fit my needs. Maybe Mitsu has something built-in, but I'm not a Mitsu expert.
1 person likes this -
Since the master PLC is actually a modbus slave, and you want that slave to also respond to your monitoring, you will likely need to write a regularly changing value from each slave PLC to separate registers in the master PLC (heartbeat signals). Then have code in the master PLC that will time out if a given slave's heartbeat stops changing. Place the booleans for that status in other modbus addresses that the monitoring system can see. (Or, perhaps, have the monitoring system watch the same heartbeat values.)
1 person likes this -
Share more details. What is the network topology? Are both PLCs Allen-Bradley? Are you using message instructions in one to talk to the other? If so, show the three tabs of a message configuration.
Embedded service error indicates that a request used message router service 0x0A to embed multiple requests in a single packet, and one or more of those inner requests failed in the target device. You would have to inspect the nested responses to determine the true error or errors. (Wireshark will help you do that.)
-
I would get an IT person to help you collect a wireshark capture, to see how far the connection attempt packets get. And therefore let you focus on where they stop.
-
Sounds like a ground loop / isolation failure.
(I have no experience with either those PLCs nor those HMIs, but that is where I would look. With a scope, if necessary.)
-
I would expect you to need to use the SLC500 driver for that one.
-
Which model MicroLogix? One of the new ML8xx family? If so, you will need to use Control/CompactLogix(Tag) mode, for access to some global variables, or assign Modbus addresses within the ML8xx program.
-
Failure of the flyback protection on the contactor coil often proceeds to destroy the contact surfaces in the upstream relay. But there are many possible reasons for mechanical failures, too. You would need to dismantle the PLC output to determine anything for sure.
-
USB type A, type B, type B-mini, and type B-micro are not bidirectional. I would be shocked if you could use any adapter there to plug in a mouse.
-
On 4/6/2024 at 10:11 PM, BobLfoot said:bring back memories?
Nope. Never touched it.
On 4/6/2024 at 10:34 PM, BobLfoot said:Dataliner DL-40
I remember these (with horror).
1 person likes this -
2 hours ago, acpi said:replaced by brand new
SiemensRockwell hardwarecause it'sdespite Siemens being more common in EuropeFixed that for you.
Siemens is as bad as Microsoft when it comes to vendor lock-in and other monopolistic behaviors. Not to mention being extremely unfriendly to 3rd party use of their protocols.
Going to modern Rockwell would also let you use their conversion tool for PLC5 => Logix. Not the cleanest conversion, but saves a ton of engineering work.
1 person likes this -
I'm going to guess the time setting isn't a way to force the connection to close. It may not be possible.
-
You can only use the switches for addresses like 192.168.1.x. For anything else, you need to access the Module Configuration page of the device (via RSLinx) through a temporary connection (like putting your PC on 192.168.1.y long enough to do this).
-
Have you contacted Rockwell support?
-
3 hours ago, acpi said:I don't have the source code of the plc.
Oy! That will make it extra difficult.
I'd toss the PLC out, too. (Or sell it on EBay for mega bucks.)
-
Wow! I thought I was old enough to know about all the old AB stuff. But not that one, sorry. You might need to take pics of every screen and start from scratch.
1 person likes this -
Have you examined the load resistance downstream? Is it within the specs for the output card? If any receiving component is not isolated, have you checked for DC offset?
-
EtherNet/IP Tag sets. Set them up on each PLC, one to transmit, two to receive. Ideally, create structure types with the content to transfer. (This is similar to Rockwell's producer/consumer tags, and uses the same class 1 I/O buffer technology.)
2 people like this -
12 hours ago, Ken Roach said:always the time since boot ?
CST is Rockwell's precision time from before PTP. When synchronizing, it is the master clock's time since boot (ish).
12 hours ago, Ken Roach said:Windows 2012 Server instance that has NTP Server enabled
Rockwell has wisely chosen PTP (IEEE 1588) for its time synchronization. Much more precise, and auto-configurable in LAN environments. Put a Time Machines TM2000B on your network, set it to PTP Multicast, and turn on time synchronization in all of the Rockwell products. (Make sure the ControlLogix processors have time sync connections to their chassis ethernet cards instead of default connections.)
Every controller will quickly be within single digit microseconds of the atomic clock that drives the GPS cloud. The TM2000B also is an NTP server, so your less modern IT devices can synchronize, too.
(I have no connection to Time Machines, other than as a very happy customer.)
-
4 hours ago, Ken Roach said:You would have to change the WallClockTime object by 60,000,000 microseconds in your program at the appropriate early Sunday morning.
No, don't ever do this. Logix underlying clock (and all clock sync operations) run on Zulu time. The checkbox in the controller properties just tweaks the local time offset. Since not all timezones obey DST, with many crazy rules, the controller simply doesn't handle it. Use an SSV to set/clear that checkbox programmatically if you need it. The WallClock currentValue is always zulu, and should always be used for timestamping.
-
1 hour ago, d4rkm4n said:best way
I don't have any specific recommendation for Mitsubishis. In general, I would use a couple extra registers to hold valid conversions and look for repeat valid values before passing to a "final" value register. That might be enough to not need a timer.
1 person likes this
Tracking,
in Allen Bradley / Rockwell Automation
Posted
If you have to track in arrays of larger data structures, using ring buffer techniques can greatly reduce CPU utilization. Using the shift instructions, or COP for shifting, is quite expensive. Instead of shifting, you add to an integer subscript for the load point to manage where you are in the array. And wrap around the end. For physical items on the conveyor a known distance downstream from your load sensor, you simply add to the load point subscript the constant for the distance (in array elements), wrapping it around, too.