adccommunitymod (AutomationDirect) asked a question.
Created Date: May 23,2010
Created By: amcbrearty
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Hi All, I was trying to help a colleague setup his 250-(1), Ecomm 100, and C-more communications. Thought I had it all worked out - knew static IP addresses to use, - programmed C-more to have one IP, - setup Panel Manager with ECOM protocol and other IP. Then, ran Netedit3 and realized that he had Windows 7 and could not use IPX and did not see the ECOM module with UDP. Read forum and decided to use the ECOM100 and ECIPSUP IBOX to store the static IP using code. Now I am getting the error flag set on the ECIPSUP and the error code 3E9. I looked on the docs and this forum, but found no error codes. Before I send him a laptop with Windows XP (AND IPX), are there any suggestions out there to get this to work with Windows 7? And also, WHY can I NEVER get UDP/IP to find an ethernet module on the PLC? I always have to use IPX? Thanks, -andrew
Created Date: May 24,2010
Created by: franji1
Sorry about the missing documentation. Those errors are in decimal and 3E9 equals 1001 decimal, which is returned when dip switch #7 is OFF on the ECOM100 module. In order to enable most EC* IBoxes in an ECOM100 module, you have to turn on dip switch #7 on its circuit board.
Please review the IBox manual, specifically the ECOM100 instruction and the ECIPSUP instruction.
http://www.automationdirect.com/static/manuals/d4user/dl405_ibox_s.pdf
IBoxes are basically the same between 205 and 405, so don't worry about the fact that this is a "405 " manual.
Created Date: May 24,2010
Created by: amcbrearty
Invalid Ecom?
Hi franji1,
Thank you for the reply!
I actually _had_ set the dip switch #7 to ON, but after pulling the module to double-check, I realized that it was an H2-ECOM, ...NOT... and ECOM100.
I assume that since the Ibox routines call out "ECOM100 " this does not work on an ECOM?!
Sorry for any confusion here. Did not see anything in the documentation calling out that this does not work on H2-ECOM modules.
-andrew
Created Date: May 24,2010
Created by: franji1
Yes, it must be an ECOM100 module. If you just bought the ECOM module, you can exchange it for an ECOM100 module (plus a little $ for the cost difference). Check the return policy.
Created Date: May 23,2010
Created by: amcbrearty
Hi All,
I was trying to help a colleague setup his 250-(1), Ecomm 100, and C-more communications.
Thought I had it all worked out - knew static IP addresses to use,
- programmed C-more to have one IP,
- setup Panel Manager with ECOM protocol and other IP.
Then, ran Netedit3 and realized that he had Windows 7 and could not use IPX and did not see the ECOM module with UDP.
Read forum and decided to use the ECOM100 and ECIPSUP IBOX to store the static IP using code.
Now I am getting the error flag set on the ECIPSUP and the error code 3E9. I looked on the docs and this forum, but found no error codes.
Before I send him a laptop with Windows XP (AND IPX), are there any suggestions out there to get this to work with Windows 7? And also, WHY can I NEVER get UDP/IP to find an ethernet module on the PLC? I always have to use IPX?
Thanks,
-andrew