What could cause FNET (version 4.0.0) to actively refuse a connection? My client is getting this error, but no matter what I've tried I've been unable to get the error on my local network. Power-cycling their board does not clear the error, but issuing a reset command over telnet, which calls fnet_release() followed by fnet_cpu_reset() does clear the error. Searching the stack source for "refuse" or "deny" variations also yields no results. Any help would be great.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It appears that our Modbus service startup may have been getting delayed or failed for some reason, so the port to monitor for the traffic wasn't active.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What could cause FNET (version 4.0.0) to actively refuse a connection? My client is getting this error, but no matter what I've tried I've been unable to get the error on my local network. Power-cycling their board does not clear the error, but issuing a reset command over telnet, which calls
fnet_release()
followed byfnet_cpu_reset()
does clear the error. Searching the stack source for "refuse" or "deny" variations also yields no results. Any help would be great.No guess, it's needed a deeper investigation.
BTW. The latest version is v4.6.2. Do not use old buggy versions.
Last edit: Andrej Butok 2019-08-26
It appears that our Modbus service startup may have been getting delayed or failed for some reason, so the port to monitor for the traffic wasn't active.