1
Open Discussion / Re: AdvancedHMI TCP to DL05 RTU Communication
« on: May 26, 2024, 08:35:19 AM »
You can use Moxa MB3170. Communications RTU-TCP is both ways.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Support Questions / Re: Modbus RTU very slow recovery from slave not on line
« on: May 16, 2020, 06:06:51 PM »
So it seems nobody noticed same and I don't know if I am doing something wrong since this is just a matter of connectinng drivers and digital panel meters.
No big visdom yet I can't figure out why is this behaving like so.
Anybody ?
No big visdom yet I can't figure out why is this behaving like so.
Anybody ?
3
Support Questions / Modbus RTU very slow recovery from slave not on line
« on: April 26, 2020, 10:23:27 AM »
Hi to all,
I noticed that recovery of communication with slave if interrupted depends on how long slave was off.
That does not make sense to me so I would like to know if others have same issue.
I am using latest beta and have few digital panel meters on form connected to 4 rtu comm drivers.
If I disconnect slave for a few minutes then digital panel meters display new values within about 15 sec while at the same time slave log shows that request started to come same second when it is back on line.
If I disconnect slave for a day (normal situation if you have sensor on maintenance or without power) then when I put back slave on line digital panel meters needs a few minutes to recover and even when they display new values "Read Timeout" is showing on meters for some time and at the same time meters again needs a lot of time to display new values.
After number of minutes everything is again normal.
It looks like there is a big que waiting to resolve and then everything is back to normal.
In slave log I can see that requests are comming as soon as slave is on line.
Digital panel meters are just attached to driver and no event is used in either.
This is a big issue for me since values are changing and there is nothing on meters.
I have timeout set to default 3 sec.
I am not sure if this is a support question or bug report but Archie can decide and give some clue what is going on.
I am expecting that communication recovery is immediately when slave is back on line since slave respond in 200 ms.
Thank you
I noticed that recovery of communication with slave if interrupted depends on how long slave was off.
That does not make sense to me so I would like to know if others have same issue.
I am using latest beta and have few digital panel meters on form connected to 4 rtu comm drivers.
If I disconnect slave for a few minutes then digital panel meters display new values within about 15 sec while at the same time slave log shows that request started to come same second when it is back on line.
If I disconnect slave for a day (normal situation if you have sensor on maintenance or without power) then when I put back slave on line digital panel meters needs a few minutes to recover and even when they display new values "Read Timeout" is showing on meters for some time and at the same time meters again needs a lot of time to display new values.
After number of minutes everything is again normal.
It looks like there is a big que waiting to resolve and then everything is back to normal.
In slave log I can see that requests are comming as soon as slave is on line.
Digital panel meters are just attached to driver and no event is used in either.
This is a big issue for me since values are changing and there is nothing on meters.
I have timeout set to default 3 sec.
I am not sure if this is a support question or bug report but Archie can decide and give some clue what is going on.
I am expecting that communication recovery is immediately when slave is back on line since slave respond in 200 ms.
Thank you
4
Support Questions / Re: ModbusRTUCom CommError event
« on: April 15, 2020, 12:54:33 PM »
Godra thank you for link.
I already used similar workaround by using digital panel meter TextChanged event since panel display "Read Timeout"
when slave doesn't respond in timeout time.
I already had it on form and sampling timer for other tasks so combined the two.
ConnectionClosed is not working here since slave is not responding but communication is established.
Since I am new to AHMI I was thinking that there is an event I do not see.
DigitalPanelMeter "knows" about timeout so it would be nice if Archie expose OnTimeout event to driver itself.
I mean driver job is to establish communication read data, respond to timeout or error so please Archie can you add such event in driver itself.
Thank you
I already used similar workaround by using digital panel meter TextChanged event since panel display "Read Timeout"
when slave doesn't respond in timeout time.
I already had it on form and sampling timer for other tasks so combined the two.
ConnectionClosed is not working here since slave is not responding but communication is established.
Since I am new to AHMI I was thinking that there is an event I do not see.
DigitalPanelMeter "knows" about timeout so it would be nice if Archie expose OnTimeout event to driver itself.
I mean driver job is to establish communication read data, respond to timeout or error so please Archie can you add such event in driver itself.
Thank you
5
Support Questions / ModbusRTUCom CommError event
« on: April 10, 2020, 11:03:57 AM »
Hi guys,
I am new to AHMI and maybe doing something wrong but I do not see ModbusRTUCom.CommError event firing in case slave is off.
I use blank project with Beta 35 and put a label on screen which should show e.ErrorMessage.
Only if comm port is used I get event firing but in normal communication if I dissconect slave nothing happens.
Using digital panel meter I see Read Timeout BUT no CommError event.
Maybe I am using wrong event for detecting slave not communicating?
If that is a case what is a best way to detect and react on slave not responding?
I simulate slave with ModRSsim2.
Just to point that comm is working ok until I simulate slave not responding and after I put it back comm contiues ok.
Thank you
Quadro
I am new to AHMI and maybe doing something wrong but I do not see ModbusRTUCom.CommError event firing in case slave is off.
I use blank project with Beta 35 and put a label on screen which should show e.ErrorMessage.
Only if comm port is used I get event firing but in normal communication if I dissconect slave nothing happens.
Using digital panel meter I see Read Timeout BUT no CommError event.
Maybe I am using wrong event for detecting slave not communicating?
If that is a case what is a best way to detect and react on slave not responding?
I simulate slave with ModRSsim2.
Just to point that comm is working ok until I simulate slave not responding and after I put it back comm contiues ok.
Thank you
Quadro
Pages: [1]