Webbs

Here is the wireshark capture when i used network configurator to download and upload the parameters from the AL1322 (192.168.94.246) from my laptop (192.168.94.241). Network Config.pcapng

I have tried the setup via network configurator and in sysmac studio.  The ifm setup examples for Omron show both methods.  I have tried 100 & 150 and also 101 & 151 with the same result.

This is the first device i have had trouble with setting up Ethernet/IP.  Yes once you have the data sizes the same it should just work.....  ifm have a downloaded setup tutorial which i followed (and also online with an ifm tech) and still had the same issue.  There is an example program which has a tag set that matches the structure of the data coming back and this also has no joy. I haven't used wire shark before so not 100% sure on how it works.  I did install it and found this in the log.  192.168.94.246 is the AL1322 and 192.168.94.50 is the PLC 35    19.650259    OmronTat_bb:80:55    Broadcast    ARP    60    Who has 192.168.94.246? Tell 192.168.94.50 Attached is the error i get.  If is set the data transfer size to be in correct i still get the same error.  

I have been able to configure the IP address and that all works as expected.  There are no jumpers on this unit and the only setting that can be changed via the ifm software is the Port Process Size.  The documents from ifm for setting this up show you can also change this also with Network Configurator.   I have had devices where there are no parameters to configure in Network Configurator and understand that.  This one offers settable parameters but then won't allow them to be set. I have set it up using the default tag size settings and it doesn't work.   I also set up a NX-EIC202 on the same network to make sure that side was all working ok and that happily worked but the AL1322 still had the issues.

Here is a copy of the code currently running. NC413_Mach_5_Setup is where the NC card is setup. Servo_Control_A_Side_Car (X axis) and Servo_Control_B_Side_Car (Z axis) are the 2 sections of code which generate the error . I currently don't have a copy of the PLC memory but will try and get one.L4C_Unloader_2008_07_24.cxp

We currently have a C200HG-Z with a NC413 card. This machine operates 24/7. Axis X & Y control one side of the machine and Z & U the other. Around once or twice a month we get a #8000 error (Double Command Error) on the X or Z or both axis. After clearing this error the machine will run for 30 seconds and the error will occur again. The only way to properly clear it is to restart the PLC and it will work for another 2-3 weeks. The code for each axis operates via Step Step Next and only sends a move signal via one step then waits until the Position Complete flag before moving to the next step and giving another move command. After speaking to Omron NZ they suggested adding a not P_Step before sending the next move command but this hasn’t solved the problem. Can anyone help??

I have a NJ301-1200 and I am wanting to set up an EtherCAT encoder on the machine to replace a incremental encoder.  I have only found absolute versions and purchased a Sick AFS60A single turn encoder (part Number 1059067). I have the EDI file installed and setup the encoder and it moves through its 0-262,144 pulses and then goes back to zero as expected.  I want to set it up as a motion axis and have a linear count and to have it continue to increase with each rotation (like an incremental encoder does).  Is there anyway to set this up? I am wanting to use a motion axis so i can adjust the current encoder position as the machine is running.

The Omron engineer had the unit for a week and wasn't able to make it do anything other than reset its count after each rotation. I have written some math to eliminate the need for the motion axis.  I will look to extend that to keep track each time the encoder goes back to zero and just keep track of encoder turns.

Hi Michael, I have tried all 4 combinations of these all delivering the same result.  I spent some time with the Omron engineer yesterday trying a few different things including gearing with a virtual encoder/servo etc without success.  I have left the encoder with him and he is going to have a look at options. I have also looked an an IO Link incremental encoder but i can't set it up as a motion axis - any ideas on is as an option?  

Hi eulno, I looked at a multi turn encoder but running at a reasonable resolution it would count for about an hour of running and then reset back to zero.  The machine can run for several hours without stopping so there would be an issue when the encoders returned to zero.  There are 4 chains the product moves along each with pushers at different spacing  (process requirement).  The encoders are used to measure the current position (and speed) of each chain and an offset can be adjusted to align the pushers to transfer the product between chains.  The chains are driven by AC motors and  VSDs. Having the encoders position resetting its count to zero at different times while the line is running would cause adjustments to go out.  I could look at having some maths set up to try and deal with this but would be easier to have a continuous count that only reset when the line stopped like we do now.    

We currently use several NX-EC0222, one as a motion axis (encoder on a press) and others i just do the maths with the encoder count to convert it to mm.  For my new project to replace the Trajexia unit i was hoping to use the EtherCAT encoders but may have to use the current SEW TTL output encoders and use 4 NX-EC0142 cards.

Thanks viman, I have thought about something like that, using a counter for each rotation and adding on the current encoder count to that but that could get messy and as you say there could be an issue with speed depending on the final PLC selection as a NX1P2 has a 2ms cycle time. I will see if anyone else has any ideas otherwise i will go back to the incremental encoder and an encoder slice. 

Is it possible to have a custom unit setting when setting up a motion axis?  I would like to set up my movement in "tiles".  Is this currently possible or can it be added?

I have a TJ2-MC64 unit setup with TJ1-DRT in slot 0 and TJ1-FL02’s in Slot 1 & 2. I am using MX2 drives and can only take 0-10V as their reference voltage for control. I am wanting to use the SPEED_SIGN command to allow the 0-10V to be used for both forward and reverse. I have tried using the syntax SPEED_SIGN = ON and the programme compiles fine but when it runs it stops on that line with a “Parameter out of range“ error. Does anyone know the proper location and syntax or use to get this command to work?

I have updated the program using SPEED_SIGN = TRUE then tested the system and the motor ran fine backwards. The Australian support is finding out why it can't be reset and why the OUT1 light doesn't come on.

I have had some help from the Australian Omron support and it appears you need to use True (rather than On) and it sets it to -1, which i had found. Checking S_REF_OUT and this gave a -ve number so thought it wasn't working. Today I connected my multi meter to the output and the voltage was -ve without SPEED_SIGN on and then was +ve with SPEED_SIGN set to True (-1). Also the output OUT1 had +24V on it even though the output light wasn't on. It looks like the function is working so will give it a try on Sunday. Australian support is going to check with the UK.....

The latest firmware has made no difference so still no further ahead.....

We have both NE1A's with Devicenet expansions and the G9SP's. Value for money the G9SP win hands down. The NE1A does have the advantage of expansion safety I/O (that are very expensive) as the G9SPs expansions are standard I/O which is OK for indication lamps etc. We have found it is a case of number of safety I/O required. Our latest project we used 3 G9SPs linking 2 outputs from one unit into second unit, i.e. all the E-Stops into the first unit.. We have also used the Sick Flexisoft controller as you can add I/O as required. They all program a very similar way (including the Sick) so for us it comes down to the best value for each job. We have all 3 types onsite so not limited by a site standard.

Omron has given me the latest firmware version so I will update the unit and see if that makes a difference. Not sure it will as the command was available with the TJ1 unit and in the earlier versions of the TJ2 manuals.

I have tried several combinations for that syntax and SPEED_SIGN AXIS(1) = ON compiles but the programme stops with the Parameter out of range error. I have our spare Trajexia setup at my desk and have tried all variants of commands but haven't had any success. I have set it to -1 as per the simulator and then cant set it back to Off or 0. I will also contact our Trio supplier and see if they have ever used the command.

Thanks for your reply Rickard.... I commissioned the system last night and is now working (other than currently no reverse). I have successfully used a four pole relay to switch the order of the pairs of A and B pulses around so when I set the VDS to run in reverse, switch on the relay and give the Trajexia a forward command the relay delivers the pulses as if its traveling forward and the Trajexia can control the VSD. This option works but adds complexity to the system when the speed_sign command would work nicely. I have defined the ATYPE as 44. I have tried setting the speed_sign both before and after i set up each axis with no joy. I tried speed_sign = -1 and this worked and then print SPEED_SIGN which gave me -1 as per the motion perfect 3 simulator. I was then unable to set it back to zero, when i restarted the controller speed_sign went back to 0. I have just tried SPEED_SIGN=1 axis(1) in the simulator and it gives a syntax error. I have asked Omron if they have made any more progress with their support network.

I have had a reply from the Australian Omron engineers : With the Speed_Signal parameter, he should type in PRINT SPEED_SIGNAL at his command line to see what comes back. I can think of two causes of this error: i) It's looking for a integer, rather than Boolean condition. He could try SPEED_SIGNAL = 1 (rather than off) at the command line. ii) He's trying to do it when the servo is on. (My guess is that we can't change this one on-the-fly; it's much more of a "set once during power-up" type parameter and don't worry about it after that). He should try and change it when wdog, axis_enable and servo parameters are all off. In both cases, remember to use BASE (x) first to ensure the correct axis is changed. It's interesting that this parameter isn't included in the shell. From what I understand, servos and drives nearly always accept a -10 - 10V signal, which is the default anyway. I had tried all the above before with no joy. I have had a play with the Trio Motion Perfect software and simulator and it had the same issue except i could set it to -1 so will have a play with this tomorrow. Will post if i manage to solve this issue....

Unloader_2008_11_13.cxpI finally managed to implement the changes you suggested. I upgraded from a C200H to a CS1 a few weeks ago and carried out the changes then. I kept all the same hardware (other than Controller Link card) and the system was working fine, but over the weekend I got the double command error again. After the PLC and Drives where reset it was all OK again, the same as with the C200H. I have attached the new CS1 version of the code (it also includes a SFC for another part of the machine). The calibration section is only carried out on the first scan or when the button is pushed and is not used during normal operation.

Initially you had DIFU and RSET at the end and now have changed to SET and RSET at the start. The not P_Step should stop the jog command starting before RSET resets the bit on the next cycle..... I will try it on Monday when I can watch the machine for the day to make sure it doesn’t cause any other issues. Thanks

Thanks for the quick reply. The rung you have highlighted is actioned only when there is already a fault and then as you pointed out could cause another fault i.e. the #8000 Error. It is something we can put in to stop the error occurring if there is a fault. The only 2 Steps I can see where 2 commands are close is Step 55.08 and 55.08 - rung 37 and 41 where it changes from absolute movement to jog. But there is an Axis not busy to move to the next step and a Not P_Step also an Axis not busy before the bit for the jog command is set.