PINK: Undocumented issues
TimC
Posts: 77
Hi all,
While running my PINK for the last 5 days whout stopping I am finding that every time I do an FTP upload and a query status (Nb_varST) at the same time I am getting a status return of:
Returned Status: 01001111 .
Network Status Normal (Bit 0) set
Got Changed Variable (Bit1) set
Email Busy bit (Bit 2) set
Error sending Email (Bit3) set
?? (Bit6) set
In all other situation the status report code works perfectly.
Why so many flags set at the same time?
What is really strange is that the changed variable is reported to be # 255!
Variable # 255 would not make much sense except that the NetBurner SB70 actually has 512K of flash and 2MB of RAM. PINK users are only able to access 256K of storage for web files and about 5K of variable space. So there is a lot of extra system memory we do not have access to.
For my PINK I put in a delay of 2secs (DELAY 2000) if Bit 6 is ever set and now the FTP part of the web server has not crashed for a day.
Regards
Tim
While running my PINK for the last 5 days whout stopping I am finding that every time I do an FTP upload and a query status (Nb_varST) at the same time I am getting a status return of:
Returned Status: 01001111 .
Network Status Normal (Bit 0) set
Got Changed Variable (Bit1) set
Email Busy bit (Bit 2) set
Error sending Email (Bit3) set
?? (Bit6) set
In all other situation the status report code works perfectly.
Why so many flags set at the same time?
What is really strange is that the changed variable is reported to be # 255!
Variable # 255 would not make much sense except that the NetBurner SB70 actually has 512K of flash and 2MB of RAM. PINK users are only able to access 256K of storage for web files and about 5K of variable space. So there is a lot of extra system memory we do not have access to.
For my PINK I put in a delay of 2secs (DELAY 2000) if Bit 6 is ever set and now the FTP part of the web server has not crashed for a day.
Regards
Tim
QuickStatus:
SEROUT NBReceiveLine,Baud,[noparse][[/noparse]"!NB0ST"]
SERIN NBSendLine,Baud,300,Looper,[noparse][[/noparse]RiStatus]
' if the next two events happen it is best to wait 2 secs so as not to crash the PINK
IF (FTP_Busy = 1) OR (LinkStatus = 0) THEN
DEBUG "." ' show that the PINK is sweating
PAUSE 2000
GOTO Quickstatus ' RETURN may be better depends on your code
ENDIF
IF RiStatus > 1 THEN
DEBUG "RiStatus: ", BIN8 RiStatus, CR
ENDIF
RETURN
Comments
other than getStatus command. So while bit6 is set, do not issue other
commands.
regards peter