ParaffinPower

Can you confirm the times? You have mentioned 0.2us and 0.1ms. If it's 0.2us, then the CP1E is not going to work. Options: 1. Use the CP1E's quick response interrupt. This will recognise a 50us signal and capture it until the next I/O refresh. It is available on inputs 0.2 to 0.7 No programming is required (just 'Settings') If there are two signals within one scan, it won't recognise the second. 2. Declare the input as an interrupt. The interrupt will respond to a 50us signal. This will call an interrupt task. This means you need to write some code, BUT you can handle multiple signals within one scan. Pp

If you are using a high speed counter, then this is ok. If you need to recognise a 20us pulse as an input then even using the quick response input only allows 50us. Can you explain further your intentions? Pp

Andy - right-click the column heading and you can clear the sorting from the context menu. Pp

I would use Hostlink to talk to the NB7 from the plc (is it a cp1wcif11?) and modbus from the second port on the NB to talk to the modbus device. Pp

Hi all I'm using CMND instructions to send FINS messages to a CORT21 card which is on the same rack as the CPU. I'm a little unclear about the 'C' part of the CMND instruction. C = Number of command bytes - no problem C+1 = Number of response bytes - no problem again C+2 = Destination network. Is this 0 (local), or the network address I set in a routing table for the card? C+3 = Destination FINS address (no problem with this part),Destination node address - is this the node on the CAN network? C+4 = no problem C+5 = no problem Thanks guys; have a great weekend Pp

Yes. The plc also supports 64 bit floats, too. I think precision near the 'limits' of a floating point number decreases so adding 1 may not give expected results. However, if you're just adding 1 every second, we'll probably be dead by the time it's a problem. Have a nice day! Pp

Hi You have correctly identified the problem. Just 'differentiate up' the 1s pulse. Right-click the contact and select from the context menu. Pp

Hi lc I've used the NB as a modbus master a few times with MX2 inverters. Whilst testing I just had the Comms wiring thrown at it on my desk and saw exactly the same results as you. I changed to proper screened twisted pair and it worked perfectly. The message obviously 'got through' to write, but the NB couldn't interpret the reply. Pp

Hello I'd connect pins 3 and 5 to the CP1E's pulse output terminals (via 2K2 resistors), and pins 4 and 6 to 0v (same 0v as the plc). Pp

I guess you mean NC471, not CN471? The units are determined by the electronic gear ratio applied in your servo drive itself. The parameter numbers vary depending on the family. I would always start at the G5 familiy myself for the built-in safety if nothing else. You will almost cetainly end up with sub-mm units, sometimes down to microns (obviously a ballscrew won't be that precise, but the servo will 'think' in microns). The speed and position registers are within the 'Axis Operating Output Area' This is the specific terminology used in the manual. Manual W426 is your friend. As the numbers are likely to be big (100mm may be represented as 100,000,000 for instance) the position and speed commands are DINTs. From the PLC's point of view, we're now in units and never need think encoder edges. Each axis takes 25 Words Out (sent to the servos from the PLC) and 25 Words in (from the servos to the PLC). You define the start point of both areas (Axis Operating Output area and Axis Operating input area), that's all. Again, W426 tells you where the speed and position commands need to go, but to start you off, it's a+2 and a+4 for position and speed respectively. Remember, it's a DINT so MOVL, not MOV instructions are the order of the day. This is standard PLC memory So if you define 5000 as your Axis Operating output memory area, then Axis 1 position command goes in 5002 (DINT) and the speed in 5004 (DINT). Axis' 2 position and speed would be 25 words further on ie 5027 and 5029 etc... Pp

Hello Just change your offline project's version to match that in the NJ. Even if you're uploading, you need a dummy project (same type and version) to upload in to. Pp

If that's your biggest frustration, you are very lucky :/

I meant the 232 cable isn't standard. There's a 'universal' omron cable detailed in the downloads on here I think. Every CP1E I've seen has a Comms led next to the serial port (built-in aswell as the add on unit) As your frame looks ok, once you see the activity led flicker it can only be the port isn't set for hostlink or the baud rate/framing doesn't match. Pp

Hello A couple of things. 1. Your Hostlink frame is missing the checksum (41 in your example). 2. The LED next to the comm port...any activity? It's not a 'standard' RS232 cable. 3. Is the plc's port set for Hostlink? Cheers Pp

It's two lower case letter i's

Yes, there's a bit count instruction. Upto LWORD is accepted as the source. For long arrays, you'd need multiple instructions and add up the results as you go. Or write your own, of course. Pp

Hello 1. A G5 motor requires a G5 drive; an MX2 isn't suitable at all. 2. CJ1MCPU22 is a great choice if you need 1 or two axes of point-to-point control. CJ2M doesn't have an exact equivalent, although an additional card (MD211) can be fitted to replicate pretty much identically. There are pre-made breakout cables to connect CJ to the G5 drive. 3. Mechatrolink2 is just bad advice for a 1 axis system imho. Over 3 axes and it comes into its own, though. 4. Be aware that a 750W induction motor won't necessarily mean a 750W servo is suitable. 5. A servo will give you infinitely better accuracy, and probably better speed. The motor selection, and especially the gearhead choice is critical. The axis inertia and desired motion profile will be required for this. 6. Using a CJ, the drive will be in pulse control; there are specific Pulse control instructions. You'll nedd an ORG to home the axis, and then the PLS2 will do everything else you need. 7. I'd fit an end of travel at each end of the axis (they can go to any inputs on the CJ) and a home proximity switch (there's a specific input for this). In this instance, read 'proximity' as 'I am in the proximity of the origin'. The actual 'home' switch is ideally the motor's Z pulse. The premade cables wires this through to the correct input. Pp

Hello All the settings are made in Sysmac Studio. The EtherCAT network is just 'drag and drop'. Very easy, very fast. Pp

If you need to check for over-torque, you can set (or dynamically change) the torque limit.

+1

Which encoder? The one on the motor itself, or the pseudo encoder from the drive. The motor's encoder certainly isn't 24v, and the drive's encoder output is line driver. The servo will follow the pulses. If you need position feedback to the controller, use a motion controller, not a position controller (PLC), although I doubt this is what you need. Pp

You can't stop a motor instantly. You can slow down when you're 'near' then stop on the target, which is better. I don't know if 1024 pulses are enough. How are you controlling position? You're results will never be as good as closed loop.

Hello Ting You can achieve excellent results with a flux-vector inverter (the 3G3RX family as you're posting in the Omron forum). It has built-in positioning and may do what you need. You need the additonal encoder card (3G3AX-PG01) I've used it by sending a position command (Modbus), although you can store 8 positions in the inverter, and select them with a binary pattern of inputs It can also use pulse and direction as a position command too; similar to a SmartStep. You'll need an encoder on your motor shaft, and possibly a force-vent fan for cooling. The 3G3MX2 inverter can do positioning, but it's open-loop so the positioning results aren't as good. Pp

Hello The syntax '$1E'is interpreted as hex 1E. For example: MyString1:= 'Hello'; (* Just text *) MyString2:= MyString1 + '$1E'; (*RS appended to the end *) (I've used the alternative to CONCAT, too) Using this method, you can access any control character Pp

This is referred to as interrupt feeding. There's an example of exactly what you're trying to do in the cp1l operation manual. It will be very similar (identical?) for the cp1e. Pp