AdvancedHMI Software

General Category => Support Questions => Topic started by: garone on January 05, 2016, 09:52:17 PM

Title: Not working on CompactLogix 1769-L33ERM
Post by: garone on January 05, 2016, 09:52:17 PM
I am trying to get this to work on CompactLogix 1769-L33ERM and it is not working. It is not read the tag and I am not sure what went wrong. Any advise?
Title: Re: Not working on CompactLogix 1769-L33ERM
Post by: Bob on January 06, 2016, 05:47:16 AM
Last week I tested AdvancedHMI with CompactLogix 1769-L18ERM, and there were problems. It started reading the values correctly but on every 20 seconds it was trowing exception - No Response from PLC(22). As far as I know this is the latest version of CompactLogix so probably there some changes. I hope that Archie will take a look at that because it is critical.
Title: Re: Not working on CompactLogix 1769-L33ERM
Post by: Archie on January 06, 2016, 07:09:14 AM
What firmware version and what version of AdvancedHMI?
Title: Re: Not working on CompactLogix 1769-L33ERM
Post by: Bob on January 07, 2016, 11:03:02 AM
I tested with AdvancedHMI V399a. The controller was 1769-L18ERM-BB1B, B Series, firmware 20.012
Title: Re: Not working on CompactLogix 1769-L33ERM
Post by: bachphi on January 07, 2016, 03:49:54 PM
it sounded like L1 & L3 are not working for you guys? I have a working system with AHMI399a, and an L2 with firmware 20.01
Title: Re: Not working on CompactLogix 1769-L33ERM
Post by: Bob on March 18, 2016, 03:15:32 PM
I made some new tests with CompactLogix 1769-L18ERM. It turned out that the problem was in my computer. I just test AdvancedHMI  on another computer it was working very well.
I still don't know what exactly is the problem on my pc. It works very well with older version of CompactLogix. I can ping the controller and also can see it in Linx but in my opinion the Ethernet/ip doesn't work correctly with the new CompactLogix. Anyway, I just wanted to say that there is no problem.
Title: Re: Not working on CompactLogix 1769-L33ERM
Post by: Archie on March 18, 2016, 05:07:26 PM
I appreciate the update on this.