Dave W.

I have already used this module and the function blocks. However, only the function blocks in the POU “Axis_1_Manager” and only with MR-J4-B. But it should also work with MR-JE. I would delete the other POU's. What does the Axis monitor say about the axis? Attached is a demo project for FX5-40SSC and MR-J4. I made some FB myself.   FX5U_4SSC_MRJ4_ORAG_Demo_v0.4.gx3

I know, I'm late. But maybe it will help in the future. You can also set all hardware inputs in this dialog. This is helpul for "servo-on" and position limits to.  

Hello I'm not sure if I understand your question correctly. If you measure the resistances while the encoder is connected and supplied with voltage, then no reasonable value can be measured. If the encoder is connected but not supplied with voltage, it can also be the encoder that leads to these measurements. Depending on whether track A or track B or both or neither is active, this could lead to different resistance values. BR, Dave

Hi, If the torque limits should be fixed, the parameters PA11/12 can be used. If the limit is reached, the TLC output is set. However, the torque limit could also be set via an analogue input. You can find all the information in the MR-J4-A manual: External Link I wish you success Dave

Sorry late, USB barcode scanner works fine with GOT 2000 at least with GT25 / GT27

Same with GX Works3 or use "Cross Reference"

R64P is the power supply. OK, I'm late but I've already taken this screenshot. Maybe it helps someone else. Dave

Just to clarify, with Modbus the slave is called the server. This never sends anything on its own. The client (master) reads and writes data provided by the server. Here is an example in which the holding registers 40000..40033 are mapped to the device D1..D34. Also register 42000..42059 to D100..D159. A client can than write and read only in these areas. You can configure this freely according to your needs. For testing I always use the tool QmodMaster a free master for MB-TCP and RTU Dave Settings Test: One important thing: the slave ID / slave address must be 255. (See screenshot) This could be your problem.   FX5U_MB-TCP-Server.gx3

For a step by step solution for MB-TCP Server (Slave): - Download the manual JY997D56101 to e-manual viewer. - Put this site-ID in the search field of the "e-maual viewer" and select PAGE in Filter section. JY997D56101-BF If you don't change anything in the settings here:  JY997D56101-C3.P2, all registers of the PLC are available on Modbus. If this is not what you want, delete the unwanted registers there: If that doesn't help you, describe your problem in more detail. Dave  

Hi I think the option module FR-A7AN give you two more analog outputs. (4..20 mA) There may be other modules as well Greetings Dave

I don't speak ladder but in ST I would do it like this. Maybe that helps. Greetings Dave P.S. If you need INT not REAL (with one decimal place) you can add this at the end. nResult := REAL_TO_INT(rResult * 10.0);

Hi DavidOtt I have made tests with this Node for Node Red. works find with FX5U. Maybe you can read the code behind this Node? node-red-contrib-mcprotocol (node) - Node-RED (nodered.org) I wish you success Dave

Yes, I work for Omni Ray AG which is the representative of Mitsubishi Electric Factory Automation in Switzerland. Unfortunately, I'm more likely to get help here than at the European headquarters. And you?

Hi DWIM Thanks for your answer. My L-CPU doesn't have much to do. Cycle time approx. 2.5ms. It's more of a problem with the predefined protocol. I made communication with many stations with FX5U and Ethernet / IP - Module. With 30 slaves from Moxa (ioLogik E1214) Unfortunately I can't remember the total transmission time. Really fast communication is possible with iQ-R and CCLINK IE Field, but it is very expensive.

Hello, everyone I have to query a SICK distance sensor from an L26CPU via the onboard Ethernet interface. I have created a simple protocol which I start with the function block SP_ECPRTCL. Unfortunately it takes at least 25ms until the next telegram is started. The sensor responds within approx. 1.5ms. Does anyone know whether that works faster or is that a limitation when using the predefined protocols? Sensor manual:  OD5000, 8021391 (sick.com)  (Chapter 7.4) I am grateful for all the hints. Thanks and regards Dave SICK_Protocol.tpc Messaufbau_vTest.gxw