panic mode

you can replace it with many products. the question is why... are you running out of I/O or need something that you do not find in that product? alternatives are likely going to cost more not to mention time to create documentation, code and have it all approved.

using speed control allow you to control the speed but it will not get you precision when it comes to position. for precise position cuts you need position feedback. doe your axis have an encoder?

well, time is running out, got to make it work... drive memory is organized in menu/parameter fashion. until i have time to investigate closer, i will be using few unassigned menu locations. this is less than ideal since they are scattered ... would prefer single (or two) blocks of memory without tiptoeing around used ones.  oh well...

hello everyone, I am able to connect to servo using driver  device/server "Control Techniques SI-Ethernet Modbus TCP". this accesses servo by specifying memory locations in form of menu entry and parameter number. But i need to exchange more than that. drive has built in PLC and i did not find out what device driver or settings would allow that.  any ideas?    

did you try manually setting the outputs on? are you sure there is nothing clearing them? did wiring change at all? problem started after program download?

exactly  

those are just shared properties. clicking on radio button 'All properties' should show longer list...   

check the wiring including terminations. also, check the baud rate. what is the expected role of this unit? it can be bus master/slave or both. bus must have a master("scanner") and one or more slaves ("devices"). some slaves can autodetect baud rate. this is convenient when it works but unfortunately sometimes they also get it wrong and that is a bad situation to be in as there is next to nothing one can do to solve it. unlike other bus types, DeviceNet uses additional pair of conductors that need to be powered by 24VDC. somehow this is also a pretty common issue as many fail to realize that they are responsible to bring this power to the bus. some fail to ground the bus shield or they ground it in more than one place (this allows for ground loops and interference) or they strip way too much of the shield so that shielding is ineffective.   if your  CJ1W-DRM21 is working as a master (scanner), you need to load correct configuration into it ("scan list" is usually created in PC software after importing suitable EDS files for each of the slaves)

using safety PLC does not mean that end result is safe. it only means that it is capable of applications requiring safety - if used correctly. ultimately it is still up to programmer to configure and program it correctly. without software one cannot check your program. you may considering printing or exporting it into a PDF form so anyone can offer feedback.  even for EStops, it is not enough to put them in series with something. safety standards have various criteria that need to be met and this is determined through evaluation process (aka Risk Assesment).

coil instruction is used to assign both true and false values: variable := expression; or in your case start := (i_SW1 or start) AND NOT I_Off; I_Off := start AND i_sensor4; ...etc.  

in DotNet one could use PathGeometry and ArcSegment. to go beyond 180deg property IsLArgeArc would need to be set to true btw, have not seen it in years but it looks like required level of customization for something like this may be possible with factorytalk view studio SE as well. what properties are exposed for objects like arc or wedge?

VisualStudio.... initially it would be the 3rd party driver/ActiveX/SDK as this is the fastest way to get results. but that is something we rarely do today. just about all are done internally, either from scratch or by using open source or SDK if and when vendor offer it. many devices use simple protocols that are easy to reverse engineer.  the usual application would be some GUI software that has many simultaneous connections to different devices (PLCs, robots, other PCs, CNCs, RFIDs etc.). and if don't want to waste the time on something new (fieldbus etc), we just add the option (driver or hardware) to one of the system components (PLC or robot) as we can already talk to those.

well that is one of the reasons we went away from integrated solutions built around industrial HMIs and use industrial PCs with our own software. they are usually comfortable and learning curve is short but one has to live with limitations. for us it meant initially we had to develop more but - it is up to us what we do with it and that means everything is possible. no more limitations like screen size or resolution, number of displays, number of tags, type of controls available etc. when something is needed but not already there, we create it. once done it can be used many times and in any project.  

i am guessing you are trying to make a custom HMI object but i cannot figure out why would border need to change and why would that need to depend on assigned tag instead of tag value. one should be able to accomplish by scaling (height/width).  what software you are using? 

number of pulses tells how far to move... rate at which pulses are sent controls the speed.   so maximum frequency of the PTO is one of limiting factors. small PLCs often have PTO that only get to few kHz, some may go to 100kHzor 200kH, dedicated modules for larger PLCs are definitely more capable (MHz). by parametrizing drive one can accomplish certain scaling so that for example axis can reach higher speed even when driven by slow PTO. but don't be fooled - this is a tradeoff... you may gain at one end (speed) but you loose at another (resolution). so one need to read the manual, do the math and set parameters correctly to get needed performance. but once you reach point where PTO cannot handle it, it is time to upgrade to more capable PLC.