Rodrigo Vieira Batista

@teddy1565 the drain is exactly what I found here. I think that probably will create some kind of delay in the communications, but only for this type of application that...

I studied the code a little bit and seems that need another layer for the physical connection (serial port) above the device layer, or assumes that the device is the...

@unocelli this will be faster to do, but will break the timeout and connect logic. I'm not experienced in node and zero experience in angular, but it's I'm interested in...

> By the way, sharedDevices in src don't seem to be useful  @PaDaBooo this sharedDevices was the beginning of development and really does nothing at this moment. I didn't...

Hello @sunjichao1226 Modbus-serial mentioned by @unocelli is the Modbus project used by FUXA to handle all types of Modbus requests. I already handled some issues on Modbus part of FUXA...

@sunjichao1226 I believe that this is the repository of the Modbus-serial project. https://github.com/yaacov/node-modbus-serial I took a quick look over the issues and was not able to find anything related, but...

@sunjichao1226 you are communicating with a real device or using a simulator? At first I was thinking that are one only two requests been packed in one Ethernet frame, but...

@sunjichao1226 I was studying the issue and for me FUXA send the data immediately, but it does using Modbus-serial project, that looks like don't have any kind of buffer. But...

@unocelli in Modbus TCP specification is clear that each TCP frame can carry only one Modbus request (MODBUS Messaging on TCP/IP Implementation Guide V1.0b 4.2.1.1 table implementation rules item 6)...

I believe that these addresses are not mapped to modbus in Schneider PLCs, which exact model are you using? Try to do the same with modscan or another modbus test...