ChrisKozanecki

I understand that you want to go a long distance between the two PLC's (where you are using the RS422) but with CX Integrator and ___ (cant remember the program name before CX-I ~too early in the AM lol) you can connect to one PLC through the peripheral port, and then talk to the other PLC over the RS422.

In the downloads Section on the website there is a VB sample program which allows you to talk to the PLC with hostlink commands. Try playing around with it and see if it does what you want. Hostlink Demo Program

I dont have any serial ports on my laptop, and I do all of my programming on it (PLC, Touchscreens, Barcode Readers, and C# programs) What I use is a USB to Serial adapter from CDW. Personally I feel this is the way to go if you need to connect to external things where serial is the normal connection because you can add as many as you want through a USB hub. The Targus one I linked to works without any additional software (assuming you use XP) and the computer knows what serial port it was assigned so you always have the same port per adapter. Dont know if this will help your problem, but for me it was the smart choice due to the small ($25) investment allowing me to avoid the headache of trying to adapt something.

it sounds like the meter on the touchscreen isn't set up correctly. What settings do you have for it? The things that I can think of off the top of my head for you to check: *Is the address set up correctly? (SerialA:D02050) *Is the range set correctly? (top limit of the meter should be above your reading) *Is the format the same as what is in the memory? (if the meter is setup as INT and your DM location has a negative result while the meter range is positive only, it wont display)

Can I ask why you are using the Rotate command and not just a normal shift register? Try using SFT instead and see if it give you the results you want. Another thing, you might try using a mask on the words before comparing so that you ONLY compare the 3 bits. Ex: [CMP 202 200] will compare all 15 bits, if you AND 202 and 200 with 0007 it will mask off all bits except the value in *.0, *.1, *.2 so it would be: [LD 253.13] [AND #0007 202 D0] [AND #0007 200 D1] (do both of these as an always on) [CMP D1 D0] Try these two options and see how they work for you.

I am not sure I understand your question, but the EM should be addressable as easilly as the DM. I may be completely off on what you are trying to do, but with the way you are writing your addresses, perhaps you are addressing them in the wrong format. the extended memory is done as: E0_00000 You need to put the E, followed by which bank, then an underscore, and the address. Is this how you are addressing it in your program?

I have an ID231, ID261, OD231, & OD261. I assume that the 261's are just doubles of the 231 versions, (correct me if I am wrong), but I cannot find a pinout of either one. Here is my problem. I have the cables for them (which are 1 to 1) and instead of going to an omron termnal block with them like they were designed for, I am wanting to connect to a custom made board that will be creating the input signals based on the output I turn on. What I need though is the pinout of the PLC card so I can make sure to connect my common correctly, power for outputs, and correctly provide the I/O locations. Anyone know where I can find this info? I dont want to blow up my cards!

Thank you both for your help. http://oeiwcsnts1.omron.com/pdfcatal.nsf/P...pdf?OpenElement That BITS N BYTES posted is actually the document that I had and was refering to when I mentioned that I thought A1->1, B1->2. Your newest document confirms that for me, but I will still ohm out the cable before I submit the board to be made. The document that you posted Jay (CJ1_Module_Wiring.pdf) and the document from BITS N BYTES (Module Pinout One) both have the same information, just slightly different format. I think the one BITS posted is a bit easier to read as a quick reference, although yours Jay has a lot more of the precautions in it. The combination of all these documents will come in very handy for ensuring that I get my signals correct.

Yeah, I dont know either.... personally I wanted to use the MIL style I/O Module instead of the Fujitsu, but when the company says "we have all of these other cables here, and we want to standardize" you are left using what style is already in the plant. Too bad the ones in the plant were done against our specifications and the person in charge didn't have the *ahem* to stand up for our company. Now we are stuck using a cable set that isn't what we originally wanted.

Your drawing has confused me.... I have one that shows A1 = Pin1, B1 = Pin2, etc... Your drawing shows A1= Pin 40, B1 = Pin 39, etc... I am not sure which one to believe now, I guess I will have to use a meter and ohm out whether it flips or not.

That is exactly what I was looking for Jay! thank you. You said that it came from the operation manual for the CJ1, but I thought I looked there. I sure can be blind some times LOL! What I meant by 1 to 1 cable is: PLC Side Cable End Pin 1 Pin 1 Pin 2 Pin 2 . . . . . . . . Pin 39 Pin 39 Pin 40 Pin 40 Basicly, I have the XW2Z-050B Cables, and I needed to know what signal was supposed to be on each pin by the time it got back to the PLC. from what I can tell the PDF you linked has this information.

The reason why is because it will cause the add functions to always be running. This way the sum total is immediately calculated at the time a counter is changed. If you only want it to add when you ask it to, then just change the P_On to a different bit

NS Screens are far easier to program in my opinion, and seem to be far more capable.

Thank you. I will look through it.

Does anyone know of a good resource for learning CX-Protocol? This is my weakest skill when it comes to PLC's and I just cant seem to pick it up. Any help would be appreciated as I am baffled where to look.

Sounds like he is not reading the forums at all.

Again, I think that Omron dealers would be your best bet. The only reason I could ever see making a cable is if you were making actual buss lines on an etched circuitboard or some other specialty application. Making a cable for one type of PLC from a different type leaves you with a cable that is not guaranteed to work and also cant be used in its intended manufacturing vision. To me, a hack should only be attempted if it adds something that would be otherwise impossible, not just to save a few $$ on something that already exists for cheap.

Yes, you can use DM's as compare data as much as you want.

On smaller PLC's such as the CPM1A there is a capacitor in addition to the battery which will keep the data for about 5 minutes (to facilitate a battery change) I dont know if its the same for the CQM series, but I imagine this would be true. the only question is whether you can detach the memory and transfer it in time. If you are talking about memory that you have on the memory card (in the slot on front) then this should be movable between PLC's because its a flash based memory that does not require a battery.

If I am understanding correctly, you are re-wiring the ports in the PLC to allow a normal RS232 Cable? If this is the case, I would be curious as to *why* you would want to do this. Please correct me if I am misunderstanding you, but it seems to me that you would be better off making the cable instead of altering the PLC.

I know it will work with the hardware you have listed. Now, dont quote me on this, but I believe anything that can be programmed in CX-P 5.0 can be programmed in CX-One. I was told what won't be able to be done, but I cannot remember off the top of my head. It was only two types of old legacy PLC's.

I agree, I am loving the CX-One Software. I will have to look today, but there is a way to change the CX-Integrator from "new Project" to something else, I just cant remember off the top of my head since I have been using NS-Designer 6.2 (in cx-one) more than I have been using integrator this week. One of the things I like the best is the fact that if your network is set up between all of your devices (I am using Ethernet) That everything flows easilly from one device to the next due to one software talking to everything now. It also makes it a lot easier to be connected to more than one device through the same Serial Port than it was before with having to run CX-Server and CX-Programmer and NS-Designer and.... EDIT: I checked, to change the project name in CX-Integrator, go to View>Properties>Project Name (name cannot have spaces)

I have an issue with trying to make a subroutine for my program. I want to have the program run normally the way it is, but if a condition exists I want it to stop running its normal program and begin running a different sequence. Basicly I want a mode where functions could be operated manually, but ONLY if its in the manual mode, and none of the automatic funtions will work. I am really kind of stumped on how to make the PLC do this. I can get the two parts to work independently of each other but not in the same program. I tried subroutine, jump and conditional jump commands but it seemed to just break the existing program and not run anything. I know its something simple that I am missing. Any Ideas?

I have tried both of these methods now and I think I like the method that BITS N BYTES uses because I can trigger the outputs to reset on the same condition that puts me into manual or automatic mode. Thank you everyone once again for your help! This site is amazing!

I just managed to get it to work with making the main program a subroutine and the manual mode a subroutine and having the program go to one or the other. It works but I dont think its the "proper way" to do it (or is it?) I will look into the Task instructions you mention BITS N BYTES. One question I have, is there a way to make the PLC ignore any settings in the part not being used? For instance: if I turn on a solenoid in the manual mode, can I have it ignore that it was turned on when I leave manual mode? I dont want an output that is set to ON in one part of the program to interfere with what the other part is doing.