kaare_t

What kind og ping does NOT find it?? I mean; you can either ping it, or you cannot ping it (and I refer to DOS pings)...... And further on, what/how are you going to communicate with the E71 module?

Yes, the message/warning is easy to misunderstand.... There should be a list of un-supported items (if any), and in case there's no problems the message shouldn't appear at all (in my opinion)..... But most often, after converting any E-Designer application, if you run "Test Project" you'll be informed of any mismatch and/or errors in the new project

The message saying that some parts are "not compatible" always show in E-Designer if you try to change versions or terminal-types. Most likely, everything is compatible and I doubt that any functionality is missing if you upgrade the terminal! I don't remember right now if v4.0 can be updated to 6.0, but I can check tomorrow (unless maybe Gambit knows it right now), but if I were you I would just upgrade the terminal and use the newest E-Designer (though there's really no problem using E-Designer v6.13)

What program do you want to "view"?? The HMI application, or det PLC application? You can't view the PLC application, but if you want to view the HMI application, you can use the remote access viewer which came with E-Designer. This is basically a standard remote access viewer (like Windows Remote Desktop, or VNC Viewer), which connects to the HMI via TCP/IP. You can set passwords so that some users only have view-rights, while another password makes it possible to operate the HMI via the remote viewer (you can press buttons, change values and so on....). Yo use this you must enable remote access viewer in E-Designer. You can find those settings via "Setup->Network->Services->Remote Access.

The "help" documentation in E-designer isn't always the best..... Check this link (the title is a bit off, but if you read it you'll find out how): http://www.beijer.no/web/web_aut_no.nsf/do...12575C2004BCC9D

Hi. No, I don't do any PC Programming (Java/C/C++) so I can't help you much with your specific application. However, I've programmed some PLCs to communicate using Computer Link (the PLCs only have slave protocol so I've been into programming the Master protocol). Basically the same thing you do, except I've done it in PLCs and you are using a computer

I would go with the 232BD card (since you can connect directly to the PLC without the need of the GOT). You will have to set up the 232BD card with a software to make it use Computer Link Format 1. This is pretty easy to do with the software and are stored in data inside the PLC. However, your problem is that you can't send down the parameters using Java before you have initialized the BD card with Computer Link Format 1..... In other words, you will need a software to set parameters to the BD card. There exists "FX" versions of the Mitsubishi software which are cheaper than full-version software, and you could set the parameters using this.... But I guess the PLC has some code inside it.....!? Maybe the original developer could help you?

First of all: What serial port are you going to connect to on the PLC? (BD/ADP/232ID)? I guess you've programmed the MC protocol, since this is an open protocol with a manual/reference document. You can send requests using MC protocol and whatever external software you would like. If you have a BD/ADP card on the PLC you will have to set up the card to communicate using MC protocol (instead of CPU protocol).

Alvi: As mentioned in my post, talk about hacking/cracking passwords (or any other kind of software) is strictly FOBIDDEN in this forum! Please remove the attachment from this forum ASAP! For a reference, just check out the TOS (Terms of service) on this website! Edit: You might get banned unless you remove the document ASAP!

DINT_TO_BCD instruction (or INT_TO_BCD)? Will that work correctly?

Any special (or standardized) combinations you are looking for (BCD or input matrix)? You can also use a BMOV and move the int into an array of bools, or just compare the int value to another number.

There is no direct way to do this. Some SIM operators have customized services for these kind of things, e.g. we used to have a service where we could send an e-mail to [phone-number]@[operator].no and this e-mail address would be interpreted as the phone number to send SMS to. (e.g. 12345678@telenor.no would forward the message to the phone number 12345678). Telenor is in this case the SIM operator, and they are offering the service itself. You might want to check out this with your SIM operator.

Use DDIV for DINT numbers. The result will be an array of DINT with two elements, where the first element is the value and the second element is the remainder (if any)

When working with "Double's", the compiler in GX IEC will only accept defined variables (you have to define the variable with a name and the correct type), and not HW addresses. The programming manual usually use GX Developer (which allows for HW addresses directly). As long as you only want to add up some numbers I wouldn'y bother thinking about the special registers (M80**). The output is by the way NOT a 64bit number, but a 32bit number (but you are correct regarding the output value). DINT is not floating point (it's simply double integer). If you want to use floating point (REAL), then you'll have to use the instruction "DEMUL_M". See both examples:

Not sure what the problem is, could you publish (upload) the source MM+ project in the forum?

No, you're using the RS2 instruction, and therefore you will have to check D8063 (when using channel 1)!! D8062 only applies when using the RS instruction. I would start with re-checking the devices you are using to ensure that they correspond with the RS2 instruction - RS2 is not the same as RS. I would in general just re-check your program. Your last line of code is also adressed wrong, and a little "odd"...!?

There are two different modules: 1. QJ71MES96 ("simple" module, does not allow for PLC-PLC comm. This only logs data to a database, with a backup memory ++) 2. I don't remember the name (I think it's something like Q13UDDEH or something), but it's actually a CPU, which also allows for OPC Server functionality (the module can do so much so I suggest reading about it in Mitsu docs).

You've still got some problems with the adressing. First: D8062 should be D8063 for this card, check the error message in this memory instead. Also; you use an ADP card with Channel1. Does this mean that you have a CNV-BD card between the main unit and the ADP card? If you have a BD comm-card, the ADP will be Channel2.

Hi! None of the PLCs have the "Master" protocol (the one that actually polls data) in these cards, so this causes some problems for you. I see you want to use "Form1", which is a Mitsubishi protocol, the problem is that both these cards only have the Slave function implemented (they only work as a server, waiting for a client -master- to poll data from them). If I were you I would purchase a QJ71MB91 (Modbus RTU) card for the Q PLC, and simply set this up as a Modbus Master. Then you can use the Modbus Slave function block in the FX3U for the 232-BD card. Another option is to use fixed buffer/No-Protocol between the PLC's but then you'll have to do some more programming (all in all, I think that the QJ71MB91 will be a less expensive solution since you will cut down on development time). If you still wan't to use Fixed Buffer/No-Protocol, you'll have to set up NoProtocol in the serial cards (check bit-pattern in the correct buffer memories/switch settings), and then you can just send whatever data you would like.

In GX Developer: Diagnostics->System Monitor Select the module you have a problem with (probably colored red/orange/yellow) - you can dobbel-click on the module name, or you can single click and then click on "Module's Detailed Information" to open up the detailed information about the specified module.

Hi. FX2N PLC: You can basically choose if you want to use the 485BD or the 485ADP (with cnv adapter). 485ADP with cnv adapter will be more expensive, but note that the 485ADP card have a better spec regarding cable length: FX2N-485BD: 50m FX2NC-485ADP: 500m A2AS PLC: A1SJ71UC24 card

FYI: Beijer did not develop GX IEC Developer. They made Melsec Medoc ("Blue Screen"), but GX IEC Developer was developed by an external software company with specs/guidelines/assistance from Mitsubishi Europe. GX Works is as far as I know made by Mitsubishi Japan.

Higher numbers are "super-users", lower numbers are "users".... So if you "log in" to security level 7, you have the most access.

Hi! Not sure if I understood everything, but I think that your main problem is your security level (see 3). After checking that I'm pretty sure that 1 & 2 will be easy to figure out. 1. You can change the name in the header of the selected POU, or in the Global_Vars if the variable is a global one. 2. Red asterix means that the POU is not compiled, or part of the output code - you can verify this by removing one of the POU's from the Task_Pool, compile, and then you'll see that the specific POU will have a red asterix (and is not part of the compiled code). 3. When you enter "Properties" on POU's ("files" in the project tree), you can only change the security level within the same level you are actually "logged into". To change your current security level go to "Project->Change Security Level". There you can change to a higher level and you will be able to select other levels under the properties page for the different POU's (or files).

Hi. You should try to get a software package for Mitsubishi (GX Developer or GX IEC Developer), so that you are able to read out the error code (as Metallion suggested). You could try to download the DEMO version (free) of GX Developer from Mitsubishi. You have a maximum om 1000steps of programming, but you can connect and check the error code of the PLC.You will also need a programming cable "SC-09" to connect to the PLC The CPU can go into error even if the battery was low..... In addition; this CPU with most of the IO cards cannot be purchased or repaired anymore, so I would strongly recommend that you (or your customer) start to consider changing/upgrading this PLC