-
Content count
2637 -
Joined
-
Last visited
Community Reputation
329 ExcellentAbout Gambit
-
Rank
Propeller Head
- Birthday 09/29/74
Profile Information
- Gender Male
- Location Amsterdam
- Country Netherlands
Recent Profile Visitors
-
ducna liked a post in a topic: HMI GS2107 startup error
-
That is true when Z0 =40 on D30Z0 then it's D70. Z0 will probably be 11 sometimes. you can move any numer into Z0 the same as you would with a D register Strange maybe it's set from an HMI or something
-
d4rkm4n liked a post in a topic: Cannot Write to D for Simulation
-
I want my ladder logic to be sent via CPU ethernet modbus in Qseries melsec CPU 03UDE
Gambit replied to raheelredben's topic in Mitsubishi
Just do the step i posted in your other post -
Issue with mitsubushi melsec PLC modbus QJ71MT91 connection with FActory IO
Gambit replied to raheelredben's topic in Mitsubishi
Now lets change and let the System Q be the client. Then you need to change the basic parameter setting to user setting parameters Set the automat comms and refresh as you have set now. Now you are reading Coil 130 => D100.0 and writing coil 128 and 129 with the status from D200.0 and D200.1 So you code in the PLC schouls also be with hose devices where Y80 - D100.0 Y81 - D200.0 Y82 - D200.1 -
Issue with mitsubushi melsec PLC modbus QJ71MT91 connection with FActory IO
Gambit replied to raheelredben's topic in Mitsubishi
Ok First lets choose the first comm style with Factory IO being the client asking the questions. In this case all you have to to set the basic params and don't need the autom comm settings or Refresh. In this case Y80,Y81,Y82 reperesent Coil 128,129,130. So If you set Coil 128 on Factory IO coil 130 should set as well. -
Gambit started following Cannot Write to D for Simulation
-
Check if there are any index writing going on Example: mov K0 D5Z0 if Z =50 then 0 is written into D55. Also stop any other comms possible writing to this devoce
-
Issue with mitsubushi melsec PLC modbus QJ71MT91 connection with FActory IO
Gambit replied to raheelredben's topic in Mitsubishi
I am not familiar with factory IO -
Issue with mitsubushi melsec PLC modbus QJ71MT91 connection with FActory IO
Gambit replied to raheelredben's topic in Mitsubishi
But the code has nothing to to with the modbus devices when used as client !! Why would it turn on Also the basic paramter startup setting should be on user If you use the QJ71MT91 as a server than Y81 = Coil 128 If you use the QJ71MT91 as a Client than D200.0 = Coil 128 but you have to set user param -
Core OS only support for the higher models I see. Just do the BOOTOS than
-
Gambit started following D memory addresses dynamically with GX Works2
-
D memory addresses dynamically with GX Works2
Gambit replied to Schellenberger's topic in Mitsubishi
This is from a previous post from @Integrator_99 made in GX Works 3 but i should work the same for GX Works 2 aswell -
Issue with mitsubushi melsec PLC modbus QJ71MT91 connection with FActory IO
Gambit replied to raheelredben's topic in Mitsubishi
Wouldnt it be scada which is the client (asking the questions) instead of server ? Also you are using D100 and D300 for reading and writing the modbus devices. When you write a value of 1 to D300 does the light come on -
Gambit started following HMI GS2107 startup error
-
Open GT designer Commuinication > Write to memory card => TAB BOOROS/COREOS Write First Write the core os and boot the HIM With that. Than the same for the BOOTOS procedure is mentioned in the TAB..
-
pturmel liked a post in a topic: Variable device access in gxworks 3
-
Gambit started following Variable device access in gxworks 3
-
The constant used in the example can also be an variable. Check the example of @pturmel ...... MyArray[Index] This doesnt have to be structued text it can be used in all editors
-
You can download the latest version via your MyMitsubishi Account. V1.662 is the latest one i think