adccommunitymod (AutomationDirect) asked a question.
Created Date: August 06,2016
Created By: kewakl
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Can someone show me where to find the documentation that describes the rationale for the downward revisions of the hardware/firmware specification revisions? I assumed that Ethernet/IP had some impact, but am not sure. Whatever the reasoning, I think the original 116K+ I/O was somewhat optimistic for the software (at that time) -- except, maybe, in a white-coat environment. (2014-DEC) (2015-FEB) Bases Groups 33 17 Total Bases 165 85 Max I/O Points 116,160 59,840 GS Drives 64 32 ScanTime 600uS 650uS
Created Date: August 06,2016
Created by: kewakl
Can someone show me where to find the documentation that describes the rationale for the downward revisions of the hardware/firmware specification revisions?
I assumed that Ethernet/IP had some impact, but am not sure.
Whatever the reasoning, I think the original 116K+ I/O was somewhat optimistic for the software (at that time) -- except, maybe, in a white-coat environment.
(2014-DEC) (2015-FEB)
Bases Groups 33 17
Total Bases 165 85
Max I/O Points 116,160 59,840
GS Drives 64 32
ScanTime 600uS 650uS
Created Date: August 10,2016
Created by: ADC_CommTeam01
There is no documentation that you can be pointed to for this. Basically as we were working to get a QA program initiated the development and engineering team decided that the specs that were originally given to the P3000 while in theory would work in reality were not feasible. Also looking at future additions to the system we decided that we should reduce these specs to prevent problems that we may encounter with future enhancements. This allowed us to set up a complete system that meets the specs for sw and fw testing. Even in a "white-coat environment " the original specs required a lot of resources. We have had no customers to date, that we know of, that have gotten close to the limits of the new specs much less the original specs. So we felt at that time it was a good point to make the change.
Created Date: August 10,2016
Created by: kewakl
There is no documentation that you can be pointed to for this. Basically as we were working to get a QA program initiated the development and engineering team decided that the specs that were originally given to the P3000 while in theory would work in reality were not feasible. Also looking at future additions to the system we decided that we should reduce these specs to prevent problems that we may encounter with future enhancements.
-> referring to (my) italicized sentence of your post ---> I assumed as much, just wanted to confirm.
This allowed us to set up a complete system that meets the specs for sw and fw testing. Even in a "white-coat environment " the original specs required a lot of resources. We have had no customers to date, that we know of, that have gotten close to the limits of the new specs much less the original specs. So we felt at that time it was a good point to make the change.
I understand and agree completely.
Thanks for the insight!