TimothyMoulder
Member
In the past couple of years, I've softened my attitude towards Rockwell over charging for tech support. This is due to the fact that charging for tech support is increasingly an industry-wide practice.
Now, I saw a post a little while ago that stated that to access the KB, you needed to input a tech connect contract number. I checked for myself, and yes, there it is. You can also enter "PUBLIC" to view "basic content".
So what is the distinction between basic and premium content? Can you still find out how to do a high-speed counter on an ML1200? Or is that the reason we're seeing so many Micrologix questions lately?
Look, the arguement for charging for tech support runs something like "Techs have to be paid, so rather than making them a burden on the company, charging lets those who use the service support the service." I may not agree with the principle, but I do understand it.
But this makes no sense. KB articles are basic stuff. Quick start guides. OS bug info. Solutions to common application problems. And once written, they aren't a further burden on the company (let's not split hairs about server space and bandwidth, this is the 800-lb gorilla of the automation world we're discussing here).
- Deleted incorrect assumptions -
TM
Now, I saw a post a little while ago that stated that to access the KB, you needed to input a tech connect contract number. I checked for myself, and yes, there it is. You can also enter "PUBLIC" to view "basic content".
So what is the distinction between basic and premium content? Can you still find out how to do a high-speed counter on an ML1200? Or is that the reason we're seeing so many Micrologix questions lately?
Look, the arguement for charging for tech support runs something like "Techs have to be paid, so rather than making them a burden on the company, charging lets those who use the service support the service." I may not agree with the principle, but I do understand it.
But this makes no sense. KB articles are basic stuff. Quick start guides. OS bug info. Solutions to common application problems. And once written, they aren't a further burden on the company (let's not split hairs about server space and bandwidth, this is the 800-lb gorilla of the automation world we're discussing here).
- Deleted incorrect assumptions -
TM
Last edited: