Show Posts
1
Open Discussion / Anyone have a micro 820 working? Looking for tips
« on: December 14, 2017, 10:21:54 AM »
Hello, Very new to programming. Spent 5 years wiring panels and my new employer loaned me an 820 to take home and learn.
Adv-HMI looks like exactly what I was looking for in an hmi solution.... only after a day of trying to make a button in adv-hmi toggle an actual output on the 820 I got no where. Saw that there was a driver for the 820 in Adv-HMI, thank you. Cycled through all ip based communication protocols but couldnt get one to work as expected. Many exceptions and errors dealing with plcaddress variable.
In CCW does one need to specify a panelview and associate the ip address that Adv-HMI would be using? Protocol? Or should we not include a panelview in to projects and set up the application without a panelview? What protocol to use with the 820? Looks like CIP or Modbus are the only ones not for a given series.
Do we need to designate program names anywhere?
In Adv-HMI I saw that I was limited to 11 chars for addresses. All of the internal addresses in a Micro820 are 12 characters in length. Tried using aliases but Adv-HMI did not pick up on them. How does one approach PLCAddressClick and PLCaddress Visible with a 820? I have read a number of posts looking for what these fields actually do but an not finding anything other than things that apply to different plc's like "N7:00" or "U41600". All I can find in the controller are values too long to put in to Adv-HMI like _IO_EM_DI_00. Since backplane routes are not needed in micro820 what is the magic recipe for getting Adv-HMI to handshake with the Micro820?
In cross reference browser variables in 820 I see that most tags are showing with read attributes. Do these need to be writable? After cycling through all protocols and not getting any desired results I am not sure where to start. Again, tips or pointers from another 820 user would be greatly appreciated.
Thank you
Daryl
Adv-HMI looks like exactly what I was looking for in an hmi solution.... only after a day of trying to make a button in adv-hmi toggle an actual output on the 820 I got no where. Saw that there was a driver for the 820 in Adv-HMI, thank you. Cycled through all ip based communication protocols but couldnt get one to work as expected. Many exceptions and errors dealing with plcaddress variable.
In CCW does one need to specify a panelview and associate the ip address that Adv-HMI would be using? Protocol? Or should we not include a panelview in to projects and set up the application without a panelview? What protocol to use with the 820? Looks like CIP or Modbus are the only ones not for a given series.
Do we need to designate program names anywhere?
In Adv-HMI I saw that I was limited to 11 chars for addresses. All of the internal addresses in a Micro820 are 12 characters in length. Tried using aliases but Adv-HMI did not pick up on them. How does one approach PLCAddressClick and PLCaddress Visible with a 820? I have read a number of posts looking for what these fields actually do but an not finding anything other than things that apply to different plc's like "N7:00" or "U41600". All I can find in the controller are values too long to put in to Adv-HMI like _IO_EM_DI_00. Since backplane routes are not needed in micro820 what is the magic recipe for getting Adv-HMI to handshake with the Micro820?
In cross reference browser variables in 820 I see that most tags are showing with read attributes. Do these need to be writable? After cycling through all protocols and not getting any desired results I am not sure where to start. Again, tips or pointers from another 820 user would be greatly appreciated.
Thank you
Daryl