-
Content count
453 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Calendar
Everything posted by ParaffinPower
-
Hello lostcontrol It's the percentage usage of the servo's torque limit. It integrates the torque with respect to the rated torque, taking into account the 300% current limit. Pp
-
Hello The -128 to 127 limitation is indeed very strange. I do this: d002Copy := d002 'take a copy of your parameter' MotorNamePlate := 1000 'lets you put in numbers greater than 127' Result := d002Copy / MotorNamePlate [old git mode]Programming an MX2 takes me back to the good old days when plc's had little memory and one used scratch areas.[/old git mode] It doesn't deal with floating points, but the DINT numbers allow you to multiply everything by 10, 100 or more prior to the divide so you don't lose precision. Cheers, Paul
-
You're absolutely right, Dick - the help for the TD is very difficult to understand. I use set td(x) inside case statements to make sure they're set just once. Pp
-
Hi Bob Never used this specific card, but with similar ones, you need to set the input span to 100%. It's 0% in your screenshots. Cheers, Paul
-
Hi Can you post them here? pp
-
Do we know if the NQ can now talk to a SCU21?
-
How to convert HEX to Floating point in CJ1M
ParaffinPower replied to thanya's topic in CX-Programmer
Hello There is no need to convert; it's already 43.030983. Just change the format in which its displayed (Hex to REAL) Pp -
Hello b_ I'm guessing you're using ST. I use this method: ResultWord:=SHL((Reply[4] & 16#00FF),8); (* Isolate low byte, and shift up *) ResultWord:=SHR((Reply[5] & 16#FF00),8) OR ResultWord; (* Isolate high byte, shift down, and merge *) Pp
-
Hello Svn, All of Omron's Smartslice IO is hot-swappable. If you choose ProfiNET then you can have a redundant ring, too (with suitable switches). Pp
-
Hello Yes, I use it extensively. Sets the MX2 a million miles apart from anything else IMHO. I particularly like the access to the MX2's positioning capability. Pp
-
try triggering when it reports Not busy, rather than every 20ms. Pp
-
CJ1M-CPU12-ETN, I guess? If you're using automatic FINS address generation, make the 2 rotary switches (node number, not Unit number) the same as the last octet of the IP address Example: 192.168.250.123 Set the rotary switches to 7B (123 as Hex)
-
1ms interrupt... Pp
-
Hello all As you guys on that side of the pond have had the JX/MX2 products longer than us, is there a 110V version available? We're struggling to find one, but can't believe that Omron-Hitachi haven't addressed this market. Cheers fellas Pp
-
Stu - I think the snippet of code is in an Action associated to an SFC step, so the First Cycle flag will have been and gone when it's executed.
-
Hello How is this bit being SET? Are you using a S action? If so, then this can ONLY be RESET with a R action qualifier in the same SFC. This is in the IEC61131-3 specification, I think. Incidentally, if you want to execute an action once as a step executes, use the P1 action qualifier. I love SFC! Pp
-
Hello Andy The CJ2M (not H) can accept upto two of the addional left-hand modules giving you HSC's, interrupts and pulse outputs(CJ2MMD212 and 211), each with the same (or better) performance than the CJ1M-CPU2x built-in IO spec. There's an NPN and PNP version; the NPN is identical pinout to the CPU2x you're currently using. There's an additional tab on the 'Settings' within CX-P to help (massively!) their setup over and above the CJ1M. Pp
-
Believe you me, I still get a buzz when things 'work'! When I don't, I'll give this up... Now, I don't want to sound patronising, but we don't want run before we can walk. Temperature control by way of a 0-10V motorised valve is (probably) going to need a PID loop. This is fairly advanced stuff; not that it isn't all documented (very well, as it goes) in the manual, but it takes a good understanding of both PIDs and PLCs. If indeed you're controlling via a PID, then you need to have two pieces of data - a setpoint, and a process variable. These are entered into the PID and an analog output is generated (for your motorised valve via the analog output card). You already have the temperature coming in -the process variable- (is it tenths of a degree resolution?) ie is 35 degC shown as 350? Make your setpoint of the same 'range' too. Forget BCD (the # prefix), make it all decimal...(& prefix) If you read the PID instruction help (available with CX-P), one of the parameters is the input and output ranges (10 bit, 11 bit etc). I prefer to scale the SP and PV to full scale of one of these ranges to give the PID maximum range to 'go at'. Scaling FBs exist if you need help with this. The PID will produce the output; again this needs to be scaled from the 13 bit (say) output from the PID to the limit of your analog output card (0-6000 IIRC?) Read the PID instruction help. This will undoubtedly prompt further questions, and come back with them. I'm using the CP1L's PIDs on a job myself at the minute, and once you've got all the right numbers in there, it just works. The key is getting the right numbers... Good luck, Pp
-
It was POETS day here today, Bob...
-
Don't leave us in suspenders...what was it??
-
I can use this phrase every day! Thank Sergei
-
Hello Sergei, I hear you; let me re-phrase. If you need the load to end up where you told it to go, use a servo. Pp
-
Hello What are you using the INI command for? If you try to stop a move with this, the position will not be repeatable - that's what the PULS instruction is for. Michael is correct, though; it's not the PLC but more likely the stepper. If high precision is required, then use a servo. Pp
-
Hello all, Me neither, Michael, although I think we have other issues. 1. What are you trying to do with the scale FB? The intention was to scale actual temperature and demand temperature to PID-friendly numbers. (10 bit, 11 bit...). My personal preference. 2. Too much BCD and binary. Choose one, and stick with it. Tip: choose binary. Although #1 and &1 are the same bit pattern, #10 and &10 aren't. Using # in a binary maths instruction will not give desired results. It would appear that the temperature written from the NQ is declared BCD. Change it to INTeger, and do away with the BIN instruction. 3. As mentioned previously, don't use P_GT flags and the like; inline comparisons are better. 4. Not sure I understand adding/subtracting 1 from temperatures. Can you elaborate? 5. What ranges are you trying to achieve on the DA041 and we can confim your range setting words. I'll hold my hands up here - this bit is outdated and, frankly, a ball-ache. Best, Pp