What address are you using that will not write to the PLC for you?Problem is with writing holding registers . Controls for user input & writing to PLC do not write data . Write function returns 0 but physically value is not written to Modbus slave from ADVhmi application (V 366).
I applaud your efforts and the graphic work is outstanding. I watched your tutorial and tried to pay close attention to the available toolbars. I didn't see any reference or means for:
Alarming w/ Summary and Historical
Graphing/Trending
Scripting
Window navigation
As I'm sure you know, HMI implementation is much more than the graphical interface. Are the above components part of your project, or items yet to come or are you narrowing your focus on just the graphical interface portion? I understand the project is in its infancy, but I'm curious as to the level of functionality you envision obtaining.
The first important thing to know about the TwinCAT driver is that it will not work on a PC with TwinCAT installed. It can only communicate to a remote run time of TwinCAT. The only way to get it to work on the same PC is to run TwinCAT in a virtual machine. This will appear to the driver that TwinCAT is running on a different PC.My config:
Twincat PLC 2.11
VB2010 Expres Edition
I downloaded you Advance HMI,opened in VB,folow the steps from the pdf instruction,and put a "MomentaryButton" and a "TwinCatComm".
I set the button to the Main.Switch1 as it is declared in my PLC program.
In TwinCatcomm I set the AMSNetID to AMS router value which I found in Twincat properties.But in VB to the TwinCatComm is a target IP adress which default have a adress.The HMI not communicate with PLC,i receive a error like "no response from remote system"
My questions is:I use the right driver(TwincatComm) in VB or not?
Without a hardware connected to the PLC,should be work the HMI local?