chelton

Target variable is the Assembly Instance you are going to use ie 100 for input 150 for output. The originator variables are the network variables that you will need to create. It is best to create a structure then create a variable from the structure and assign it as an input/output network variable.

Strange. It won't allow me to do that.

I don't have 2 x NA's to test, but why cant you have a single global DINT in the PLC that both _HMI_CurrentPageIndex are mapped too? I can't see why the ladder code is needed at all?

Is it possible you have accidentally mapped both screens _HMI_CurrentPageIndex to the same global variable? or left the global event in?

I don't think there is a way. The only way to see the value is to hover the mouse over the value or in the watch window.

Yes it appears the security certificate has expired

There are functions called "Get1sClk" etc that are what you use now.

What device are you using to convert from profinet - modbus/tcp . A protocol converter usually has to have the mapping setup. You should have set your profinet variables to correspond with modbus registers in the protocol converter.  

I can't see where you are using the variable ARRAY_RECEITAS ? is that ladder screenshot in a function block? It looks like you may have declared 2 variable arrays 1 called RECEITAS and another called ARRAY_RECEITAS  

If you want every cycle you can change the code to this: Timer_SP:= 200; (* Timer setpoint *) TIMHX(TRUE,timer1,Timer_SP); pulse:= input AND NOT oneshot; (*generate pulse on rising edge of input*) oneshot:=input; IF pulse THEN IF NOT timer1.CF THEN (*Calculate cycle time only if timer has not timed out*) inst_cycle_time_sec:= UINT_TO_REAL(Timer_SP-timer1.PV)/100.0; (*instantaneous cycle time in seconds*) ELSE inst_cycle_time_sec:=0.0; END_IF; timer1.PV:= Timer_SP; END_IF;  

Cycle time between pulses in seconds. Timer_SP:= 2000; (* Timer setpoint *) pulse:= input AND NOT oneshot; (*generate pulse on rising edge of input*) oneshot:=input; IF pulse THEN IF Timer_Start AND NOT timer1.CF THEN (*Calculate cycle time only if timer has not timed out*) inst_cycle_time_sec:= UINT_TO_REAL(Timer_SP-timer1.PV)/100.0; (*instantaneous cycle time in seconds*) END_IF; Timer_Start:= NOT Timer_Start; (* toggle timer every pulse*) END_IF; TIMHX(Timer_Start,timer1,Timer_SP);  

Do you want the cycle time between every input pulse or every second input pulse? Starting and stopping the timer using a flip flop will only be able to capture every second pulse.

What happens when the timer times out?  A simple flip flop to toggle a bit in ST  pulse:=input AND NOT temp temp:=input IF pulse THEN output:= NOT output; END_IF  

Can't you just divide the DINT by 100.0 and have the Destination as a REAL ? 

In the manual for CJ2's under offset addressing it states you can offset address a symbol value. Attached is the snippet from the manual. It doesn't work for me? Can anyone tell me if it does actually work or its in the manual and isn't actually implemented.

Yes that's what i mean, The only reason I found out was because I added a variable to the symbol table which I was using elsewhere with an address offset. Then when i tried to compile I had errors. D0[2] works  D0.00[2] works D0[D1] works D0[symbol_01] works Symbol_01[1] Fails Symbol_01[Symbol_02] Fails  

Apologies Michael, You are correct. 

You can reference the index of the structure with a variable IF you give the structure an address in the symbol table.      

Your need to assign a length to the string variable in the plc. eg STRING[10]

Correct. User manual W516 - Section 2-2-4

Built in Analogue inputs are 0-10V only. Addresses are A642 and A643 Range is Hex 0000 - 03E8   ( 0 - 1000)

This is the equivalent of your ST: Sec_PW_RST_Seq_Latch_1:=Sec_Invisible_Button AND NOT Sec_PW_RST_Seq_Latch_2; Password_RST_TTimer(IN:=(Sec_TextEntry_HMI_PB AND Sec_PW_RST_Seq_Latch_1),PT:=T#5s,Q=>Sec_PW_RST_Delay_Dn);  

Also line 3-6 can simply be: Sec_PW_RST_Seq_Latch_1:=Sec_Invisible_Button AND NOT Sec_PW_RST_Seq_Latch_2;  

Is there any noticeable difference between the 2 packages? Will my licence for a 32 bit version work on a 64 bit installer?  

I think you'll be safe for a while yet with the CJ/CS series, there's isn't a redundancy option available in the NJ/NX range yet.