TOPIC:

@avra,

I'll attach file in zip.
System: WIN8.1 64 bit
simulator from: www.plcsimulator.org/

First is Modpoll connected do the Moxa DE-211 (RS-232, COM2) . Moxa is connectet to USB-RS-232 optoizolated and is connected to the simulator (RS-232, COM1).
Com2: baud 9600, data bits:8, parity: none, stopbits:1 ---- Modpoll
Com1: baud 9600, data bits:8, parity: none, stopbits:1 --- Simulator

Moxa setup:

modpool screen and simulator:

You can see that is recievied 21DEC [15Hex].

second is HTerm connected do the Moxa DE-211 (RS-232, COM2) . Moxa is connectet to USB-RS-232 optoizolated and is connected to the simulator (RS-232, COM1).
nothing change to moxa sets.
HTerm and simulator :


Now PascalScada connected do the Moxa DE-211 (RS-232, COM2) . Moxa is connectet to USB-RS-232 optoizolated and is connected to the simulator (RS-232, COM1).
Pascalscada and simulator:


@papelhigienico in attachment PascalScada_and_sim.zip there is the TTIPropertyGrid You told me to put on project.

@avra, Can You see for now these tests ? The rest I will test later.

EDIT:

@avra,, I can't use simulator (like www.modbustools.com/modbus_slave.asp) because my time of useing has expired. I use www.modbusdriver.com/diagslave.html
PascalScada connected do the Moxa DE-211 (RS-232, COM2) . Moxa is connectet to USB-RS-232 optoizolated and is connected to the simulator2 (RS-232, COM1).
Pascalscada and simulator2:


HTerm connected do the Moxa DE-211 (RS-232, COM2) . Moxa is connectet to USB-RS-232 optoizolated and is connected to the simulator (RS-232, COM1).
HTerm and simulator2 :

Today I put test with Scada and PLC XBC-DR20SU LS.
Moxa sets without any changes.

First is PascalScada and PLC connected with USB<->RS-232 (FTDI optoisolated)




Second is Pascalscada with PLC and MOXA



The ioDriverError on LastSyncWrite shows when I put some Value on HMIEdi1 and send value (enter button on PC)

More test will be soon.

EDIT:

I forgot about the cable info. I use about 1 meter 4x0,5mm2.
PC <->PLC
RX - TX
TX - RX
GND - GND

@avra and @papelhigienico please check it and tell me what more test is needed.
@avra You want me to change the cable, but please tell me what kind of cable should I use?
maybe shielded, I don't know .
This test I made at home, so there is without any noises.
If need, I can use another type of Moxa.

Test with two terminals:



Test with Virtual comm RS-232 pair
Pascalscada and simulator:



HTerm and simulator:

swicio1 wrote: First is Modpoll connected do the Moxa DE-211 (RS-232, COM2) . Moxa is connectet to USB-RS-232 optoizolated and is connected to the simulator (RS-232, COM1).
Com2: baud 9600, data bits:8, parity: none, stopbits:1 ---- Modpoll
Com1: baud 9600, data bits:8, parity: none, stopbits:1 --- Simulator

It looks like you have virtual COM1 made by USB-RS232 convertor and virtual COM2 made by MOXA driver (it does show as serial com port but it is virtual driver tunneling MOXA communication through ethernet cable). This does not affect your problem.

The ioDriverError on LastSyncWrite shows when I put some Value on HMIEdi1 and send value (enter button on PC)

That doesn't show in MODBUS.TXT log from scada_plc_moxa.zip. Can you send log showing this error, together that small test PascalSCADA project causing it?

Well it seams you do not need another cable. Pascal SCADA properly sets PLC register 1 (modbus protocol level addr 0) to 870 getting good reply, and sends command to get content of that register, receiving 870 which is good. I can not find any error documented in logs from your 3 previous messages. It seams that PascalSCADA reads and writes well to/from PLC. Once again, you have to show me the error. You say when it happens but it doesn't show in your logs. This behavior is also in conflict with your first message, when you were complaining for a very different problem, when timeouts shown from log were pointing in a different direction. That made confusion and that's why I wanted to check few other things. Now it seams that PascalSCADA has a bug, but you need to document your findings very clear and without confusion. What exactly happens and at what moment when you want to manually send value to PLC? If you didn't already then provide logs where that problem is visible and small test project showing it. Is that the only bug you have found, or you have more to report? Repeat the procedure for each bug found. That will highly increase your chance for author fixing the bug. Also, project is open source so everyone can peek into it and try to fix if needed.

avra wrote:

The ioDriverError on LastSyncWrite shows when I put some Value on HMIEdi1 and send value (enter button on PC)

That doesn't show in MODBUS.TXT log from scada_plc_moxa.zip. Can you send log showing this error, together that small test PascalSCADA project causing it?

When this error happend, MODBUS.TXT does't report it on log. This is the problem, because i can't see errors on the logs.

What exactly happens and at what moment when you want to manually send value to PLC?

Program in the HMIEdit shows always 0.
When i put some value in HMIEdit and send it, PLC get correctly value from HMIEdit, but HMIEdit in program shows 0. On HMIEdit should be the value entered earlier, but it's change to 0 - in PLC stay value recievied earlier.
In logs, you can see that everythings is ok, but i can't recieve any value from PLC through the MOXA virtual port.
I think that maybe something is with the MemReadFunction not right, but i can be wrong.
Through the virtual USB-RS232 everything is OK.

I tried to attach the program but I can't. It's too heavy I think

EDIT:

ok, i attach it here

Once again, you have to show me the error. You say when it happens but it doesn't show in your logs.

Exactly, error shows on TIpropertygrid, but not on the logs. Logs doesn't generate this error - scada_plc_moxa.zip .

first message, when you were complaining for a very different problem, when timeouts shown from log were pointing in a different direction. That made confusion and that's why I wanted to check few other things.

This problem is resolved, I have to rise up the WriteReadDelay from 20 to 200.

Repeat the procedure for each bug found.

There is only one bug i found - I can't receiving the data from PLC through MOXA virtual com, and only trough MOXA. The rest of virtual or real com I can receive the data.

Do you have increased the Timeout property on SerialPortDriver?

Another strange behavior is the ioNone on write. I'm studing the code, and, if I'm not wrong, I found a bug,

Yes on SerialPortDriver.

EDIT:

I set 100

I have a suspect: Your serial port does caching of write requests, so WriteFile completes without wait the operation ends. Associated with this bug, everything goes wrong.

Can you use the development version of PascalSCADA? Or in the best case, can you edit the file serialport?

Yes, I can edit file serialport. What i have to do with it?

Go to line 497 and 498, they should be like this:

replace these lines by:

Recompile everything and test.

You are reallllly Gooood

Working now!!!!!!!!!!!!!!
logs:



Many Thanks!!!

I'll commit the fix. Thanks!!

@sternas update your copy of PascalSCADA for CodeTyphon. We found a bug!

Ok guys
I love this step....

@swicio1 how are your tests today?

Hej papelhigienico.
For now it's working very good, also with the usb-rs232. Even if I back to the default property WriteReadDelay and Timeout on SerialPort it's working good.
I wish that, I had not written about this problem earlier. I was waiting for an update in the hope that in the newer Version will work properly.
Thanks again, good job!
Regards