Gambit

MrPLC Member
  • Content count

    2639
  • Joined

  • Last visited

Community Reputation

330 Excellent

About Gambit

  • Rank
    Propeller Head
  • Birthday 09/29/74

Profile Information

  • Gender Male
  • Location Amsterdam
  • Country Netherlands

Recent Profile Visitors

15346 profile views
  1. Variable device access in gxworks 3

    the solution is to use the bit proicessing instructions  Like TEST - BSET etc
  2. Ok there are two things you can do. The esiest is using the refresh and use D Registers like you have now. You just write a line of code copying the outputs to a D register MOV KxY100 D98 where x=1 is 4 bits (or K4Y100 = Y100 to Y10F)   Or you can just write code instead of Refresh directly to the BFM TO   K...(module) K3000 K4Y100 K1 or  MOV K4Y100 U....\G3000    
  3. Cannot Write to D for Simulation

    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         
  4. Just do the step i posted in your other post
  5. 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    
  6. 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.  
  7. 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
  8. I am not familiar with factory IO
  9. 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
  10. HMI GS2107 startup error

  11. HMI GS2107 startup error

    Core OS only support for the higher models I see. Just do the BOOTOS than 
  12. D memory addresses dynamically with GX Works2

    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 
  13. 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   
  14. 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..  
  15. 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