Gary.Johnson

MrPLC Member
  • Content count

    39
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Gary.Johnson

  • Rank
    Senior mechatronics engineer

Profile Information

  • Gender Male
  • Location Michigan
  • Country United States

Recent Profile Visitors

2023 profile views
  1. kepserver with cx programmer

    I have several machines communicating with Kepserver using CIO6000 to 6143 and haven't had any problems.
  2. Rung wrap read only?

    Tried to activate rung wrap view and saw the attached dialog. I don't recall seeing it in older versions. Is this a bug?
  3. fresher need help for change screen

    Assuming you have a NS series display there are controls for displaying numbers and strings. Omron manual V073 explains how to use them.
  4. question @ and !

    Those symbols can mean different things depending on where they are used. If you have a CJ or CS series PLC, Omron manual W394 explains how to use them.
  5. Industrial router recommendations

    Thanks, took a look and Red Lion devices can't route by IP address/port. The search continues.
  6. CX-Programmer improvement requests

    OK, found something else to cry about. Consider the following: Project includes EIP network so addressing is through network tags (arrays). Each device on the network gets its own array/tag. I add unique comments for each address associated with a given device. When I use any of the addresses in the PLC, whether entering as array[index] or typing the literal address directly, CX-P displays the tag name/comment instead of the unique comment associated with the individual address. If I want to see address specific comments I have to use a XFER block to copy the tag/array into a parallel set of addresses and attach the comments to the parallel addresses. Very wasteful in terms of memory, program size, and time. It would be swell if CX-P gave priority to individual comments and only showed the array comment where there is no comment attached to a particular address. Example attached. EXAMPLE.cxp
  7. Industrial router recommendations

    Thanks kaare_t, One of the things slowing my search is filtering the verbiage. Some folks think of a 'port' as the physical hole you plug a patch cable into, others think it is an attribute of a logical address. Some suppliers offer 'Layer 3 switches' where others call them routers and some offer 'routers' with no (TCP/IP) layer 3 capability at all. I end up having to download the manual or tech spec to identify the specific capabilities and protocols the device supports. Very time consuming.
  8. Greetings all, Looking for a DIN rail mounted router ('layer 3') for an Ethernet/IP application that requires port forwarding/translation/redirection. Finding lots of devices that can do 1:1 NAT but PAT seems to be much less common. Prefer something easy to get in the USA. TIA
  9. Got it sorted out. "Implicit messaging" is ODVA's term for mapping memory areas of a given device to Devicenet master allocations. In the case of the Watlow devices it's a list of parameters like presets and temperature readings that are mapped to DRM21 addresses in order of appearance. The first parameter in the list is mapped to the first allocated address and so forth. Watlow provides a piece of software called ASSEMBLY PROGRAMMER for configuring their devices and you have to have it to use their temp controllers. The units as delivered can't be controlled over Devicenet. I suspected this but the manufacturer of the machine I'm working on mucked things up so badly that it was impossible to tell from his code. The fellow I spoke with at Watlow was an expert on their devices and how to configure them but wasn't much help trying to translate that into Devicenet. I had to configure a device, add it to the network and sift through PLC addresses until I stumbled onto the numbers I was looking for. Time consuming but it got the job done. Thanks again. Hope this helps the next guy who runs into these devices.
  10. Thanks PdL, I did that when I was initially handed the system. The device(s) in question are Watlow EZ-Zone temperature controllers. The configuration in the DRM21 allocates four 8 bit registers as polled inputs and four 8 bit registers as polled outputs to each of the Watlow nodes. The EDS file supplied by Watlow shows 80 bytes one way and 84 the other. Some of the controllers are dual channel and require a minimum of 16 bytes in each direction to exchange the minimum information required to operate them. This leads me to believe that the configuration in the DRM21 has no bearing on CIP implicit messaging. I guess the next question I have is does this CIP implicit messaging operate independant of the I/O configuration in the DRM21 and if so, is it possible to (re)configure the devices to operate like normal Devicenet nodes or do I have to figure out how to exchange CIP implicit messages?
  11. Got a real head scratcher and I'm hoping for some guidance. I've been handed a system that communicates with field devices over Devicenet but instead of reading/writing CIO addresses the PLC and devices are exchanging hex codes via something called "CIP implicit messaging". I've pretty much figured out what CIP messaging is but the OEM didn't bother to provide a map of the specific addresses in use. I'm looking at an overcomplicated chunk of programming that employs multiple levels of indirection (for loops, index registers, pointers, arrays...) and no documentation to explain how everything works. Before I spend days/weeks trying to pry information out of the OEM or reverse engineer the entire system I'm hoping there is some sort of correlation between these CIP message addresses and the CIO addresses allocated to the nodes in CX-Integrator. Any insights?
  12. Replace button/label text

    Why didn't I think of that?
  13. Replace button/label text

    Got a project with 100+ screens and the supplier wasn't a very good speller. I need to correct a spelling error on 1200+ buttons and labels. I've read thorugh the CX-Designer help file and manual and can't find a search/replace for text, only addresses and tags. Am I looking in the wrong place or did Omron actually forget to include this?
  14. W coil not working

    Any chance your W bit is mapped to an input somewhere (Devicenet, Profibus...)? Happened to me once. Contractor fat fingered something and moved half the I/O table. First symptom was work bits that weren't working.
  15. Got into a discussion the other day regarding my company's practice of storing documentation (ring binders) and spare tooling inside the main (high voltage) enclosure. It's my understanding that anything that won't fit in a print pocket on the door has to go somewhere else not only for house keeping but also for fire safety. I would like to base my argument on a regulation or documented 'best practice' but I've yet to find one. Anyone aware of a reg/rule covering this?