Thanks for the reply, that's sorted the current recipe display...cheers.
When we used the E410 HMI's the recipe could be remotely changed from the PLC, I cannot see how to do this with the IX screen???
Search found 5 matches
- Mon Sep 17, 2018 5:25 am
- Forum: Application Development
- Topic: T4a recipe
- Replies: 4
- Views: 7770
- Mon Aug 13, 2018 5:19 am
- Forum: Application Development
- Topic: T4a recipe
- Replies: 4
- Views: 7770
T4a recipe
Hi, I've converted an old e410 project to T4a and I'm stuck with a couple of things. 1. The e410 had an Ascii box that displayed the recipe name in use. 2. The e410 recipe could be remotely changed from I/0 on the plc or a network signal through the PLC etc. How can i get these to work on the t4a???...
- Mon Dec 03, 2012 5:14 am
- Forum: Application Development
- Topic: Tranfer of Project from USB Pen Drive
- Replies: 2
- Views: 7136
Re: Tranfer of Project from USB Pen Drive
Hi, Yes, I transferred one last week but it wouldn't work with a 32gb USB stick, it did work with a 8gb stick so maybe it doesn't recognise high capacity sticks? To do it on IXD v2 click the export project button then select the root of the pen drive, once complete turn off the screen, insert the pe...
- Mon Dec 03, 2012 5:06 am
- Forum: Application Development
- Topic: .net framework
- Replies: 1
- Views: 5925
Re: .net framework
Thanks for no replies! the fix was to carry out a repair on all .net frameworks installed on the pc.
- Thu Nov 29, 2012 5:38 am
- Forum: Application Development
- Topic: .net framework
- Replies: 1
- Views: 5925
.net framework
Hi,
I was running IXD v1.3 and suddenly encountered a build error "ilink.dll with IAlink3" could not be found, mitsubishi recommended upgrading to IXDv2 which has been done but the same error occurs. I have just re-installed the .net framework v4 but it still persists. Can anyone help with a solution?
I was running IXD v1.3 and suddenly encountered a build error "ilink.dll with IAlink3" could not be found, mitsubishi recommended upgrading to IXDv2 which has been done but the same error occurs. I have just re-installed the .net framework v4 but it still persists. Can anyone help with a solution?