MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

35 Excellent


About innoaloe

  • Rank
    Former Omron Engineer
  • Birthday 03/24/91

Contact Methods

  • Website URL,,
  • Skype

Profile Information

  • Gender Male
  • Location Jakarta
  • Country Indonesia
  • Interests Drawings, Piano, Japanese Music

Recent Profile Visitors

2643 profile views
  1. CX-Supervisor improvement requests

    Just going to let it out here... : WHY CAN"T I RENAME MY PAGE????
  2. Sysmac Studio Improvement Request

    Simply said, we can't :D
  3. NX1P2 to Indusoft communication

    @lostcontrol Cannot really guess why, since I believe the error 64 is not a FINS specified error. Typically we debug FINS protocol error using MRES / SRES information returned by the master unit when the error occurred. It you can find that info from Indusoft, that'll be helpful.
  4. [SOLVED] Color Pallete Size Problem

    Hi again! Resolved the issue. Turns out the "Zoom" thingy didn't changed as I expected before, so I manually change it again to 100%. Tried opening CX-Supervisor again and it shows properly now. Still, I think it's an overlooked bug, since the Zooming error only occurred on that particular part of the application. The other components retain its render sizes in all zooming condition.
  5. [SOLVED] Color Pallete Size Problem

    Hi Berti, I did tried that Zoom thing too. It was at 175% before, but I toned it down to 100% already without different result. Do you have a same app version (3.41)? Is it look like this or is it normal?
  6. Trying my luck to ask here, if anyone can help :D So I've started using CX-Supervisor v3.41 and found a very odd problem with the color palette, as shown in the picture below. As you can see, the palette size is abnormal that the Color Selector button is not visible anymore. This window is also not sizeable, so I cannot do anything to fix it. I never encountered such problem with v3.24 before. I confirmed this is not a screen resolution problem either since I've tried to change it. Anyone encountered same issue perhaps? Maybe someone know a workaround? Thank you
  7. CJ1M-CPU13-ETN modbus

    The Terminal mode is just your other HyperTerminal like Putty. If you're receiving too many data bytes, try giving a Differential Up to the SEND Instruction, so it should be executed only once on each trigger.
  8. CJ1M-CPU13-ETN modbus

    Yes. Hardware-wise, the connector is indeed RS232C. But software wise, that port can only send certain Omron protocols, like Toolbus (it's default. Also called C-Mode in W342 manual I believe), Host Link, or Serial Gateway. It doesn't support No-Protocol RS-232C. You can, however, sends the Toolbus command using the very same SEND or RECV instructions to the BR. But then it will be the same issue with the FINS protocol, where the BR plc need to interpret the data
  9. CJ1M-CPU13-ETN modbus

  10. CJ1M-CPU13-ETN modbus

  11. CJ1M-CPU13-ETN modbus

    No, that's not possible. See the plc Settings under the peripheral port. You'll see that Rs232 does not exist as an option.
  12. CJ1M-CPU13-ETN modbus

    The SEND/RECV instructions doesn't require you to input IP Address of the target PLC, since UDP is an unconnected socket communication. But you need to specify Destination Node Address, which is the 4th digit of BR PLCs IP Address, considering both Omron and BR is on a same subnet. E.g. Omron IP is and BR IP is, the Destination Node Address is set to 5 in that instruction. Still I'd say it's pretty troublesome to do.
  13. CJ1M-CPU13-ETN modbus

    Actualy you can, if the BR supports Udp socket. Just open a UDP port on BR side then send data from the omron plc using SEND or RECV instruction. The down side though, you need to manually process the Fins command sent by omron plc and generate proper fins response also to be sent back.
  14. CJ1M-CPU13-ETN modbus

    Hi @keal, unfortunately it's not possible. The said CPU does not support open Socket Service protocol. You can only use it for FINS, web server, or SNTP. It is stated in manual number W441, chapter 1-2. You need to connect a CJ1W-ETN21 or CJ1W-ETN11 to use Modbus TCP
  15. Read EF82 Analog Sensor - CP1E-N30DR-A with CP1W-MAD44

    I cannot say for sure... but I do believe moving D104 value to CIO 102 is not needed. Also if your Pressure Transmitter shows 4 (which is the Psi/kPA values I believe) the reading in CP1W-MAD44 will not be 4. It should be some number between 0 - 6000, because the analog module translates data that way. You need to scale the reading result using either APR or simple mathematics functions to get the same reading as the pressure transmitter shows. Chances are, value of 4 in the Pressure Transmitter is too small when translated into Voltage, so the reading of the analog input becomes 0.