EpicInfo Timing issue

[Daniel Boulay]

Good day Peter,

hope you're doing well.

I have read in your documentation that some PHs are scanned more often than others and I understand why and it makes sens.

But if (for a special projetc) I don't use any Sets and only use PH via the FSUIPC_Read feature, will it affect the scanning rate which PHs i choose to use ?

My epicinfo.cfg file looks like this:

[fanda]

Log=0

FSUIPC_WRITE_1=Y15,2,50C0

FSUIPC_READ_1=129,2,50C2

FSUIPC_READ_2=130,4,50C4

FSUIPC_READ_3=131,2,50C8

FSUIPC_READ_4=132,2,50CA

FSUIPC_READ_5=133,2,50CC

FSUIPC_READ_6=134,2,50CE

FSUIPC_READ_7=135,2,50D0

FSUIPC_READ_8=136,2,50D2

FSUIPC_READ_9=137,2,50D4

FSUIPC_READ_10=138,2,50D6

FSUIPC_READ_11=139,2,50D8

FSUIPC_READ_12=149,2,50DA

FSUIPC_READ_13=141,2,50DC

FSUIPC_READ_14=142,2,50DE

So, basically, my question is that if I use PH 118 instead of PH 129,

will it make a difference in the updating rate ?

Thanks and best regards,

Daniel

[Pete Dowson]

But if (for a special projetc) I don't use any Sets and only use PH via the FSUIPC_Read feature, will it affect the scanning rate which PHs i choose to use ? ...

So, basically, my question is that if I use PH 118 instead of PH 129,

will it make a difference in the updating rate ?

No. The update rate is limitied for the regular PHs and QPs because they operate procedurally, reading Gauge Token values by calls to PANELS.DLL which in turn calls SIM1. DLL, etc. Very slow. Direct FSUIPC reads are very fast and not a performance problem.

Pete

[Daniel Boulay]

Thank you.

Daniel