Search the Community

Showing results for tags 'qseries'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 11 results

  1. hello guys, I´ve got this wierd error (wtf1), if i switch it from NC to NO contact it goes through rebuild without problem (wtf2), relevant part of SDT on picture wtf3... I´ve GX works ver: 1.612N Anyone ever encountered this? What was your solution?   thanks  
  2. Hi guys, So I want to divide two D value and comparing the result to setpoint and trigger alarm accordingly. Most the time, the result of the division will come out with decimal point. I am not familiar how to deal with decimal, floating, integer, etc before this.  I try to do as below, actual result is 1.666.  D8100 - 1 , D81001 - 6 How do I properly put decimal value in D and to show in HMI? Thanks!
  3. 3301 SP. PARA ERROR

     I cannot get this CPU parameter error to clear and need some fresh ideas. CPU was running without error. Installed a QD75M4 card, got the 3301 alarm on the CPU after that. Took the QD75 card off, deleted the intelligent function module, updated the I/O assignment in the PLC parameters. Still can't get rid of the 3301 alarm, CPU is forced stop.
  4. Q series - MQTT

    I'm using PLC mitsubishi Q series. I'm finding a solution to send data from PLC to local MQTT broker as a publisher and recive data from MQTT broker as a subcriber. I don't know what is the simplest way to do it. Anybody did it before?  Can you give me any advice? please. Thank you very much. 
  5. Hi guys, i got some problem when connecting to ethernet modules to 1 virtual computer. My virtual computer has IP (11.20.103...) my 1st ethernet has IP (11.20.52...) and my 2nd ethernet has IP (11.20.96...) i can connect the 1st ethernet to virtual computer with mx component, but i cant do that with second ethernet module. Are 1 virtual computer just can connect to 1 etherner? Or the third IP must same each other? Can anyone help me Thank you
  6. Hello everyone. I'm new to  Mitsubishi PLC . My device is  Mitsubishi PLC  Q Series(Q03UDV) and GX worker2 to set up parameters. I'm now implementing an application to communicate PLC with MC protocol. After some research, the application can now read or write data to PLC. But here's the problem, I have found that once an application is connected to PLC and read/write data(without closing the connection), other application must wait until the first application close the connection to read or write data. I have read these manual, but no solution has found. Hope someone knows the reason, thanks. http://forums.mrplc.com/index.php?/files/file/1086-q_l-melsec-comms-mc-sh080008lpdf/ http://dl.mitsubishielectric.com/dl/fa/document/manual/plc/sh080779eng/sh080779engai.pdf  
  7. GX Work2 Comments in Arrays

    I am very new to the Mitsubishi PLC world (I have a lot of experience with A/B and Omron though).  I am having an issue trying to assign comments to an array of Globally scoped bits - I am also using Structured Ladder - NOT simple ladder.  Is it possible to do this?  I have contacted there tech support group and they were of little help.  I don't care if I update the label comment or the device comment, I just want to assign a simple comment that can be displayed (i.e. I am using this for step sequences).   Any help would be greatly appreciated!  
  8. We have a QSeries PLC. Q25HCPU. We also have a PLC program. We found that the address registers (also known as device addresses) attain a z-value added next to it - automatically over time. We are not sure why this is the case. Nonetheless, when these values get added (by the PLC - not the engineering software), some of the functions in the PLC doesn't work. We found that by formatting the CPU, and reloading the program, allows for the system to work again (temporarily) for a few weeks, up until this problem occurs again. This problem occurs across various CPUs (eliminating the potential for hardware problems. These z values can be seen when a program comparison is done. (see attached file). The questions become; 1. What is the function of these values? (why does the PLC add them? 2. How can they be permanently removed?
  9. We have a QSeries PLC. Q25HCPU. We also have a PLC program. We found that the address registers (also known as device addresses) attain a z-value added next to it - automatically over time. We are not sure why this is the case. Nonetheless, when these values get added (by the PLC - not the engineering software), some of the functions in the PLC doesn't work. We found that by formatting the CPU, and reloading the program, allows for the system to work again (temporarily) for a few weeks, up until this problem occurs again. This problem occurs across various CPUs (eliminating the potential for hardware problems. These z values can be seen when a program comparison is done. (see attached file). The questions become; 1. What is the function of these values? (why does the PLC add them? 2. How can they be permanently removed?
  10. Absolute value in ST

    Hi everybody I'm trying to create a code to count an absolute value from my Q64AD module. I found absolute value function ABS, but its working somewhat strange, and i do not see the difference between real value and absolute value. Then I created a timer for an absolute value with some mathematics: SUM1:= SUM1 + napr1; Nsum := Nsum + 1; IF timer_sr.Q THEN timer_sr(IN:= NOT timer_sr.Q , PT:= T#100ms); outsr := SUM1 /Nsum; Nsum := 0; SUM2 := 0; END_IF;   where napr1 - is value from Q64AD module ch1. It worked on codesys, but not working here. Data type of sum1, napr1, nsum is Word[signed]. In codesys Nsum was INT type. What's the difference and what i did wrong?
  11. Good day Please assist me - pertaining to the QSeries GXWorks2 Programming  - and in particular the utilization of the macrocode functionality. The information required includes; [1] Purpose of macrocode (incl advantages) [2] its utilization's effects on the PLC programming memory (it appears that it consumes more programming memory. [3] any reference documentation that could be used - containing specifically information regarding this feature (note most manuals doesn't discuss this)