MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About IanM8040

  • Rank

Profile Information

  • Country United States
  1. L18ERM 16#0203

    you probably want to make sure that you have the right number of IO in the configuration as well... considering its the embedded IO that can't be detected properly.
  2. Changing a PowerFlex 753

    If you do change them out, don't run Firmware 14.XX if you plan to use P163 [DI RUN] and P162 [DI FWD/REV]. There's a bug with firmware 14 that causes a conflict of parameters even though there is no conflict when using those input settings to determine forward or reverse direction on the drive.
  3. Upload from ABB PM5630 PLC to Computer

    I ran into this same issue with a pm564eth. Customer needed help on an abandoned project. There was nothing on the SD card and each time i tried to upload i would get an error.   It seems unless they specifically store the project to the SD then you can't simply upload to your PC like Allen bradley (which i normally deal with)... And i thought just not getting comments was annoying! Youll need the original project, if you get it, everything should be set up including communications they used to get online with it. Once i had my original project in hand, i was able to go online with the controller like normal.
  4. ACD file to PDF

    Not sure what reports you chose, I did a simple print routine to try it first and it printed fine. then generated a report and made sure to unselect everything... then only chose ladder and tags. The AOI in it are just doing small conversions.
  5. ACD file to PDF

    Here you go, let me know if thats all you need or not. ladder.pdf
  6. update the revision of your drive to the latest and match it in the studio project. 6.001 or 7.001, there is no 6.1 on the site for download so it may not be supported anymore and logix is detecting that?
  7. This is what happens for sure. 3 and 6 aren't landed in the c13 cable. I probably didn't outline that enough in an earlier reply when I mentioned not to use a crossover cable!   Reminds me of when I was a floor technician and got called to a machine where an engineer attempted to connect to a 5/03 directly to the ethernet port on his laptop, the entire line was down until we found out what happened. I was a little wary of touching anything with the 'fakernet' ports until I read up on it and realized what happened.
  8. https://twcontrols.com/lessons/rslogix-500-allen-bradley-rslinx-harmony-files-deleting-to-fix-browsing-issues
  9. The black UIC device in the link is just a third-party device.    have you tried deleting the harmony files for rslinx?   
  10. I take it you don't have a second UIC device to test against?    maybe try these steps also.   https://twcontrols.com/lessons/how-to-configure-the-1747-uic
  11. This driver used for dh485 uic device    
  12. Here's a list. basically it just needs the 1747-uic device (Make sure the switch on it is clicked to the right position, otherwise it will be trying to use the DB9 instead of the rj45). then go to a standard rj45 (ethernet) cable. use the 1747 uic device driver which only asks for the comm port needed, it shouldn't have an auto-configure button on the driver needed.   Whatever you do, just don't use a crossover cable with the RJ45.... things may burn up at that point.
  13.     It's the likely guess. not sure if there is even a way around this... I may just end up using bridged and working around the difference in connection if ethernet/ip driver is needed to discover devices.   I could always just use that handy SIM IPE tool to discover them when no IP is listed too!!
  14. Thanks, yeah the basics are good. Ping is good, can communicate just fine, this one driver just does not like this adapter setting.    Just tried the harmony files delete and it didn't seem to change anything. although it was still set to trying to browse a remote subnet to test.     So, still odd... ping is good, harmony files delete didn't work. I think rockwell just has a thing for me.
  15. Thanks Tim, I'll give it a try.   So a little more information would help also.  I'm using a VM through Vmware, the connection is NAT. If I use bridged, then it works fine. but switching back to NAT where I had it previously it doesn't work automatically. in either bridged or NAT the ethernet driver maintains connections no problem, so definitely seems like some sort of internal issue with linx.