@ke4pjw said:
Such a simple little fix. I created a new method to see if the socket was disconnected. I just check it after every packet is sent in a TCP connection. If it returns True, close your file and open the listener again.
pub isdisconnected(socket) : rtv
if (readreg(REG_Sn_IR,socket,1,@REGBUFFER) & Sn_IR_DISCON) == Sn_IR_DISCON
return True
else
return False
I have found an issue where shared hubram between cogs can cause issues with the W6100dvr.spin2 driver. This appears to be obvious now, but never manifested itself as a bug until recent testing revealed it. Specifically, these relate to the following variables:
REGBUFFER - Fixed
TX_WR - Fixed
RX_RD - Open
RX_RSR - Open
Fix is incoming shortly. It will not require any user code to be changed, just the W6100dvr.spin2 file needs to be updated.
Sorry for the delay in posting this update. Version 1.5 has been released and resolves the issue of corruption of data when multiple cogs access the W6100.
Comments
You can simplify this to:
pub isdisconnected(socket) : rtv return readreg(REG_Sn_IR,socket,1,@REGBUFFER) & Sn_IR_DISCON == Sn_IR_DISCONIn Spin the result of a comparison operator is True or False
I did not know you could do that. Cool!
I have found an issue where shared hubram between cogs can cause issues with the W6100dvr.spin2 driver. This appears to be obvious now, but never manifested itself as a bug until recent testing revealed it. Specifically, these relate to the following variables:
REGBUFFER - Fixed
TX_WR - Fixed
RX_RD - Open
RX_RSR - Open
Fix is incoming shortly. It will not require any user code to be changed, just the W6100dvr.spin2 file needs to be updated.
--Terry
Sorry for the delay in posting this update. Version 1.5 has been released and resolves the issue of corruption of data when multiple cogs access the W6100.
Let me know if it causes you any issues.
--Terry