katmandoo tortoise

Thanks very much. Problem resolved. Reloading the Boot OS did indeed return it to factory state. Help much appreciated

Ah, ok. That may be it. The HMI has been used to test another project, so maybe it has something stored in there. How do I reinstall the boot os?

Hi I am making a new project on a GT2512 HMI, and I want operator authentication. My problem is the first login. I have loaded the project from scratch, but when I go into Operator Management I am challenged for the administrator password. I guess there must be a default first time password, but I don't know what it is, so I can't get in to set our own oprrstors and passwords There must be something obvious I am missing! Any help gratefully received 

Hello Well, the legal position of "abandoneware" aside, I have a similar problem. A system has an old TSX17, and the PLC needs to be replaced with something more up-to-date. However, the OEM that built the system (helpfully left a plate with their name and phone number attached to the cabinet) has gone out of business. Nobody in-house has a backup copy of the program. So I'd like to find a way to extract the program. I don't need to use the program as an editor, just to read out the program then view the existing ladder code. If there is someone in the UK who has a licensed copy of the program (and the programming lead) we'd be happy to pay them to read the program out. However, we haven't been able to find anyone with that capability. In the absence of that, does any one have a copy of the software I can use for the one time then erase?  

Hello Diraemon A Series Motion Control is very old now, you may have trouble running the software on Windows 10 - it was designed in the Windows 98 / NT era. I assume this is an old project you are trying to maintain, you wouldn't be starting a new project using hardware this out-of-date.  Can you migrate the hardware to something newer?  Really, whoever is relying on this system is making themselves very vulnerable to any failure, since it is no longer supported by Mitsubishi, and if hardware fails, they will struggle to get their system back up running again. The SW3RNC software is of course, copyright Mitsubishi.  Also the file would be 97MB which is too large to post here. Regards

Hi Personally, I would go straight to remote IO. Especially for your analogue IO, long multi-core cables aren't the best thing. Is there some reason you don't want to start out with remote IO? In any case, I can't see anything wrong with what you are thinking, but I don't know of any standards or preferred practices. Keep the analogue signals well away from noisy stuff and use shielded cables for them. Are you sending power down your multicore cables or using power supplies in the junction boxes - watch out for volt drop on long 24V feeds. Just my opinion. Cheers

Hi, The Motion CPU has two separate parts in it, a regular control PLC (which you can program with GX Developer) and a separate motion controller. The motion part has it's own programming software - which is recognisably the great-grandfather of MT Works (MT Developer)... The software you need doesn't have a snappy name like MT Works - I have it as "SW3RNC-GSVE". There are several parts to it, and the one you want depends on what OS is installed in the PLC. For the commonest applications (Real and Virtual modes) the programming software is SW3RNC-GS22P - the 22P lines up with the OS... What are the problems you are needing to investigate? Hope this helps PS, the SW6 version mentioned above supports the Q Series motion CPUs whereas the SW3 is for the A Series.

Well, the original message said PWM (PWM_M) so I would read that as the PWM command, and PWM_M in GX IEC. The simulator does not replicate the instruction, but it has also been tested really on FX PLCs (so the message says). The instruction works, I have used it many times. My guess is that it is not being applied correctly. The instruction will only work with one of the two high speed outputs (Y0 or Y1) so trying to use it on any other output won't work. It can only reasonably be used on a transistor output, since a relay output will have to be driven slowly, and the relay will eventually fail being pulsed on and off so many times. That said, the PWM instruction *will* work with a relay output, but you must set the times long enough for the relay to operate. The first operand is the ON time in mS and the second is the total period, also in mS. So: PWM K500 K1000 Y0 will operate Y0 with a 1 second cycle, the relay being on for half of the time and off for the other half. The second operand must not be less than the first, otherwise the cycle can't work. On a relay output PLC, this will make the PLC tick like a clock! In what way is the "not working" being exhibited? Hope this helps