Tags not updating in the designer

[Ebrahim_Karam]

I have a programmable device simulator and the tags are not updating fast enough in the designer.
I have one boolean that is set to have a value of
square(1.0, 0.0, 1.0, true)

If the cycle is 1 second or less the data doesn't get updated in the designer or in the HMI tags that rely on it

What may I do to fix this or what am I missing

[Transistor]

You are polling the tag at the rate defined in the Default tag group. The default rate for this is 1000 ms.

Create a new tag group with a faster scan rate.

Then edit the tag to use the new group.

[Ebrahim_Karam]

So this what I have set the tag group to be

But when I set the rate to speed less than 0.7
square(1.0, 0.0, 0.5, true)

I only get a steady signal
Am I still missing something

[PGriffith]

What's the base rate set to in the simulator?

Programmable Device Simulator | Ignition User Manual

Regardless, this is probably the wrong hammer for this job.
I wouldn't recommend driving any "production" logic off a simulator tag.

From the tag name, it sounds like you're looking for a "flasher". In Perspective, you really shouldn't use a tag-based flashing approach. Instead, use a style class:

Internal flash bit

It’s a tiny bit convoluted, but you can just use a style class for this, too: [image] Set the duration appropriately, then add a stop at 49% with the same color as your 0% state. Then add a stop at 50% (and 100%) with the alternate color. The animation will take 1s to transition through all your steps - so half the time, it will be trying to transition from step 0 to step 49 - but since they’re the same, nothing will happen. Then, after 50% of 1s has elapsed, it switches to the 50% style (a…

Or if you insist on using a tag, so that flashing is globally synchronized, just use an expression tag with something like:
getSeconds(now(__someRateIntegerInMilliseconds__)) % 2 = 0
If the expression tag is set to 'Event Driven' mode, it'll run as fast as the refresh rate you set on now().

[pturmel]

I think you have misunderstood how the simulator works. Your square wave period is expected to be an integer, indicating how many cycles of the base rate it lasts. The base rate is an overall setting for the simulator.

[Ebrahim_Karam]

So editing the base rate would do it!!

Thank you

So square signal is multiple of the base rate
square(1.0, 0.0, 0.5, true)
square(min, max, period, repeat)
Where period
Represents a period of time as a number of Time Intervals. The default value of 10 represents "10 Time Intervals.". So it needs to be a multiple of the base. 1000 ms is the default