lostcontrol

Display the commanded value instead of the actual value.

Have you tried using the same ModbusTCP driver? The ML range does support modbusTCP as well.

Can you post your NS application, or a shot of the config? I think in the NS there is a tick box to 'use CIF41'? Have you set the Dip Switch as recommended for slot 2? Can you connect to the PLC with CX-programmer?

Hi, Does anyone have an example on doing a standard trend graph with scroll bar..? I can log data, but getting the scroll bar to work as well as display time stamps is a little more work...

Not forgetting, that REAL datatypes consist of 2x consecutive integer locations (32bits). A lot of newbies are not aware of this.

Post your PLC & HMI files (or snippets if you are worried about people copying your code... ) The other option is screen shots Also, highlight the sections required.

I don't think they need to be different FINS ports, they should all be the same

Thanks guys, Hopefully I will get a chance to get back to site today to do this.

It would be really good if I could add a gateway to a customers ETN21 without having to stop the PLC, can this be done? I know there are restart bits that can be set independant of the CX-Programmer, but do they work? Or is the only way to set these parameters via the CX-Programmer configuration GUI's?

If MyCondition And Not DifUp Then Count := Count + 1; EndIf; DiffUp := MyCondition;

Unless of course, you are going to 'Map' your IO...

There are a couple of variants, the most similar is the 'UP' instruction.

How is the comparison table structured? One would think that it is done in 7x word blocks? Do you have the address setup?

Why would you though? To many, this is very bad practice & only adds to confusion.

What is the specific issue you are having? Are you having bandwidth issues, or these 2 PLC's behaving oddly?

Your problem has nothing to do with the altivar settings, if what you are telling us about them all having the same setup. The way the EasyModbus function works for DataWrite is that it only writes on a change, since at startup your values are the same the EasyModbus is not seeing a change! Simply have a timer that adds 1 every 10sec, the subtracts 1. This only needs to happen at startup, but won't make any difference if it is always done. There is another way, but I don't have your code so can't be sure. Send it to me & I'll have a look. If you need an example, let me know.

What PLC model are you using? Attached simple example that captures a value every second & shifts the previous values down the stack... ErikRobin.cxp

Peter, Try changing the speed reference by a value of 1 up/down every 5/10 seconds, to see if that solves it. The Easy modbus code only writes the speed reference on value change, so it likely that the value is not written when the drive powers up, as it would not of changed. if you change it every 5-10 sec, then it will always try & write it.

Actually, it cod be that the speed value is only sent on data change. I think the easy modbus of is configured to do that by default, but can be changed to always write. What documentation do you have for setting the easy modbus up? I not at PC so cannot check, if PMCR is snooping he may comment as well..

Modbus is not that complicated, if you think it is then why not use conventional IO. You could still set the speed from your HMI that way. I think your problem is that your altivars are not all set up the same. If you are using the same code for modbus that we worked on last time, & it works on the other machine, it won't be the code.! I am not too familiar with the ATV312, but think they are similar to the others, so can you copy the parameters to te HMI & download to the oes that don't perform the same?

I did this a couple of years ago with an Omron PLC, think it was a brick as well as a CJ2. I will have to check. All it was doing was reading data from the serial buffer, the GPS outputted a serial stream every 100ms that I read & split. I will try & find the code to refresh & post what I can.

Really? Right click on your program task & add section.

No, you can create sections which contain your blocks like you have done in RS500. You do not need to call these sections though, CX-Programmer scans them automatically.

CX-Programmer implements sub-routines differently than RS500. To the same as you have done in RS500, just create ladder sections in the order you wish them to be scanned. The PLC will automatically scan them as one consecutive program, whereas RS500 you could call a subroutine multiple times....

Crossbow makes an interesting point, why do you need to read the data as a string? Is it a requirement of the OPC server, or the application? What is your intent for this? There may be better ways to achieve the same thing without conversions... FET-Convert.cxp