Simon

You can do it through info mode, correct. This is handy to make a quick change for testing and initial setup. If the change is to be permanent, I prefer to do it via a COM_INIT block in the ladder program, using SB2. That way the com settings will always be confirmed at power up. The settings are then part of the project so they will be transferred if you load the program into a new PLC.

OK, so it sounds like you will need to create each text message as a graphic and handle them that way.

For example, to place standard text on the screen. In English we would use the Text object and type the text. For your language, use Windows Paint (for example) and type the text in there. Then save as a graphic file. Go into Visilogic and use the Bitmap object to put the image of the text into the HMI. I am no expert with this, but does your Tamil language require only one keystroke per character? If yes, have you tried installing a Tamil font into the PLC font handler? It would be worth checking whether or not you can in fact type the text directly if a suitable font is installed.

What happens when you press the other option ("cancel" I think it is?) If you click "OK", it tries to open the recovery file. If you click "Cancel" it dumps the recovery file and opens with a blank project.

Which ever method you use to address multiple slaves, one thing is the the same - you do need to ensure that each Modbus function is complete before starting the next. The "standard" method is to use the "Function in Progress" MB that gets linked to the Modbus Config block. This bit will stay on while a function is in progress, so you can use the "off" state of this bit (via normally closed contact) to enable the next function.

Hi, bit of a tough one for your first Unitronics project You can use Modbus to drive the M91 as an I/O slave. Maybe that is a reasonable choice since your control system already uses Modbus for the motor drives. However, for ultimate speed as well as simplicity.I would probably opt for CAN bus, if you only want to transfer one encoder value. Select an M91 with CAN bus, such as the M91-2-R2C. Set up the Vision 570 to use CAN ISC protocol Once configured, the M91 can automatically send the encoder MI value to the V570 at an interval as short as 20ms. Search "CAN ISC" in the Visilogic help to get all the details.

Have a look at the examples in the "Motion Control" examples in the U90 ladder examples section. One aspect is to use the 2.5ms interrupt. Also, are you ramping the speed down as you approach the setpoint? There is also an example of this in the sample programs.

DNP website for the uninitiated (like me): http://www.dnp.org/default.aspx I agree with the suggestion, and would vote Ethernet/IP ahead of DNP3, as Ethernet/IP is more broadly used across different industries. Ethernet protocols in general are the way the industry is developing.

Wikipedia link for anyone interested: http://en.wikipedia.org/wiki/IEC_60870-5

I have pulled up the manual, and it includes a list of registers. There is quite a selection, since the PMDAIO has digital and analogue signals. However since the module is configurable via jumpers, that may change the mapping. I haven't read that deeply. Make sure you are using the right Modbus function type for the I/O point you are accessing. The PMDAIO manual should spell this out also. It can seem intuitive to use the "Read Inputs" and "Read Input Registers" since you are dealing with an I/O module. But not all vendors follow that type of logic. Check whether you need to use the "Read Inputs" (code 2) function or the "Read Coils" (code 1) function for digital inputs. Likewise analogue can either use "Read Input Register (code 4) or "Read Holding Register" (code 3). Product Page Link Direct PDF Download Link These comments are a bit fragmented, but hopefully something will be helpful.

I think the protocol is already there (PCOM) and supports the information transfer. Remote Access and Remote Operator both work fine on a PC. The sticking point is the app development, to give something like Remote Access on mobile platforms.

This isn't normal. I presume you are talking about the Ethernet sockets. What are you doing with the Socket init blocks in your ladder code, if anything? The default socket config will be done for you once you initialise the Card. If you are using Socket init blocks, make sure they are driven by transitional contacts or one-shot logic. If it gets deeper than that, I suggest posting your program to the forum or send to support@unitronics.com One of my standard debug techniques is to start with a new blank project and only add the features you are trying to test. That might sound time consuming, but so is going around in circles wondering what could be wrong. If the test program does the same thing as the real program, you have a nice simple example to use when asking for help. If the test program works properly, you can then compare with the real program to find out what is different.

Certainly the suggestion to send to support is a good one. It sounds like something simple, like the wrong MI, or you have used an MI for the X1,Y1,X2,Y2 values when you intended to use a constant value. Also, for decimal values, make sure you take into account the scaling factor. For example if you have scaled in hundredths, the 0.5psi value would be entered as 50. You could also try setting up a very simple project starting from scratch, just with the linear block in it, so you eliminate other distractions and possible factors.

Kore Telematics are now in Australia as well, that's exactly the kind of company I had in mind.

There are also the webinars in the Support section of the website, in particular the following: http://www.unitronics.com/Content.aspx?page=LightsandButtons

In terms of cycles, your process is 58 seconds long, and the heater cycles 3 times during that process. That equals approximately 1300 relay cycles per 7-hour day. The relay contacts are rated at around 100,000 cycles. This would be reached in approximately 76 days in your application. You should have RC suppressors, but even with those in place, based on the total number of cycles the relays would start failing sooner than you would like. I would suggest using the M91-2-T1 and external relay modules, solid state relays if you can, and also use RC suppressors. In that configuration the M91-2-T1 should last "forever" and if you lose an external relay they are easy to replace. On the other hand, since perhaps you have a lot of M91-2-R1 on site(?) maybe you can have a backup unit and swap it out when the relay fails. If you aren't planning to make a warranty claim for any other problems with the unit, an experienced technician can change the relays in the PLC quite easily. I only suggest going this way because you mentioned your other department that uses a large number of these.

You would need to discuss the warranty and return policy with the company you purchased the unit from.

If you haven't already done this I would fling a copy of this post directly to support@unitronics.com I have seen odd things from time to time, generally my advice is to try and get as close to a full re-write of the OS files as possible. As follows: Try starting the PLC in bootsrap mode (power up while holding your finger on the touchscreen). Then re-load the OS from this mode. Make sure your baud rate is set to 115200 in Visilogic to perform this step. To go back one step further, open the unit and remove the battery, leave for several minutes. Then leave the battery out and try the above step again. I hope this helps, and I repeat the suggestion to send a copy to support so they can help you if you don't solve it yourself.

Unfortunately I don't have any experience of the issue regarding "Launching User" and "Interactive User". I am glad I could provider at least some help.

Hi Raymond, I did a quick test with a V280. I used an OPC test client from Automated Solutions (www.automatedsolutions.com). It's one that I have had for a while, and I can't find it on their website, so here is another one that looks more current: http://www.matrikono...ndex.aspx. The test client can make it quicker to set up and change OPC tags, and see the real-time value. They are still looking at the same data your main SCADA looks at. Make sure you use the correct format. In UniOPC I called my PLC "V280". So in the test client to monitor RTC I used the tag V280.SI30 Since the OPC Server does not have a box to test PLC comm settings, go to the PLC built-in COM port sniffer and check if there is traffic when you are querying data (I can't (easily) do this on my V280, since it doesn't have that feature). I hope this helps.

Hi Emil, I am glad you think of Australia when modems are being talked about :-) I hope one day we will have a perfect solution. The complexity of setting up depends on what you are trying to do. If it is just SMS you have a better chance of success. If you need data, then good luck. I have found that GSM modems typically use a standard command set for SMS. However even subtle differences can be enough to prevent it working if the modem is not a standard type supported by Unitronics. My only attempt at getting a CDMA modem to work found they had used a completely non-standard set of commands for SMS, so it was a non-starter. If you have a CDMA modem that uses standard commands for SMS then you may be able to make it work by modifying the AT commands in one of the standard modem configurations provided by Unitronics. If this works, you then need to document this extremely well to make sure you can repeat your success. For data connections, I would follow Keith's suggestion and try to find a 3rd party re-seller who has expertise in M2M. They can then help with modem setup as well as assigning network access. You can run into several issues related to visibility of IP address, and segmented networks. Standard Telco helpdesks certainly have trouble with these types of concepts. You also find odd things like data not travelling between competitor networks. They can also change the rules to suit the majority (teenagers who want twitter and facebook on their mobile phones) and disregard the implications for M2M users. Sometimes the most suitable data solution is to put an ethernet card in the PLC and use an braodband wireless router with ethernet port. I hope this helps.

So where is the checkbox to make a V570 look like a V1040? I was not aware of this feature... Nice project btw

The sequence I have found to work in these cases is: * take battery out and leave at least 30 minutes with power off * put your finger on the screen then power up the PLC, you should get a countdown timer "Countdown to OS", touch again to get the status "Countdown Aborted" * set your Visilogic baud rate to 115,200 * run the OS update wizard. The sequence of the above steps is important, so if you have done those things, but can't be sure it was in that exact sequence, I suggest you try it again. I would also try it more than once if it doesn't work the first time. 2 or 3 times would be sufficient to confirm whether this method will recover the unit.

Good to hear it is solved.

I agree this is a reasonable expectation from the market, and I was asked about this in the last training session I ran.