| Some details to make your comfort.
>- Are there any completed solutions with the asset VAX_SIMATC-S5 ?
Yes, there are at least 20 VAX SIMATIC's being used all over Europe
to date. Also there is a BASESTAR integration.
>- How do they look like ?
Difficult to say, but mainly interfacing the PLC into customer
applications, often done by the customer.
>- Who has experience in programming with the asset ?
You mean within Digital ? I can you tell anything about it.
Also my colleage who is integrating it in BASESTAR. Also some countries have
people who knows VAX SIMATIC, but I don't know them all!
>- Who can give me some hints if the following configuration will work:
> there are 3 SIMATIC-controlled presses which will send continuously messages
> to the VAX. All 5 seconds each press will send a telegram over the line to
> the VAX. Each message will hold some data referring the state of each press.
> The messages should be read by the VAX and the data has to be send to another
> program (Workstream). This is all !
That configuration WILL work. The rate is about 1 message/second. You are
under the limits of:
On a local line of 9.600 you can reach up to
4.2 msg of 128 bytes/sec using 10% CPU on a �VAX II
On a Terminal server line, delay 40 msec, you can reach up to
2.5 msg of 128 bytes/sec using 4% CPU on a �VAX II
On a Terminal server line, delay 80 msec, you can reach up to
1.6 msg of 128 bytes/sec using 6% CPU on a �VAX II
These are measurements for a "minimal" user application doing only SIMATIC
data transfers.
>- are there any restrictions in using VAX_SIMATIC-S5 ?
I don't know any, apart the ones mentionned next.
>- are there any restrictions concerning ther telagrams which will be send over
> the line (except the length of 128 bytes) ?
Unsollicited output is not supported, meaning, that the PLC takes
the initiative to read data from the VAX.
(Unsollicited input, meaning, that the PLC takes the initiative to
write into the VAX, is supported).
Regards, Dominique.
|