General Comments Note: Some commands are multiline and lines will be broken by '..' Most commands are followed by \r\nOK or \r\n\r\nOK and these will be excluded from the table but denoted by '...' The minimum command set should be: +FCLASS to get into class2 +FCR to indicate you can receive Hmmm: has anyone done a class2 send only fax? +FLID to set your local station ID NOTE: some fax/modems implement this command but do not really support the CSID since they do not have the NVRAM chip to store it into. What you will see is when people call you then won't see a CSID being identified +FDCC to set the DCE capabilities +FDIS to set the session parameters +FDT to start sending a page's data NOTE: most vendors do not seem to implement the AT+FDT=x,y,z... command so it is impossible to change the T.30 parameters during the fax job except by using AT+FDIS +FET=0 to end a page's data +FET=2 to end the fax +FDR to start receiving a page's data The following commands are only supported by Everex and Multi-Tech: +FBADLIN=, +FBADMUL=, +FCQ=, +FDT=, +FLNFC=, +FVRFC=, +FWDFC= These commands can make for some very powerfull software since you can support larger pages and have the fax/modem shrink it if necessary. +FBOR seems to have vendors who implement only orders 0 and 1 and some that implement all 3 +FDCC=?/+FDIS=? seem to have various implementations in terms of capabilities: Everyone does normal/fine resolution. Anyone who has 14400 fax does the bit rate but alot of vendors are not going for the 14400. Most vendors are doing page widths for 1728, 2048, and 2432. A few do 1216 and Multi-Tech does all 5 widths. Everyone does the 3 page lengths. Everyone does the 1-D modified Huffman and 2-D modified Read compression. A few do 2-D uncompressed mode. NO ONE seems to do the 2-D modified modified Read compression. NO ONE does Error correction mode NO ONE does Binary file transfer Everyone implements the 8 scan line times +FDCC? seems to be handle OK except by EXAR who decide not too dislay the first number and instead start the line with a comma. +FET=? doesn't seem to be implemented by anyone except Multi-Tech. You can't tell which codes are valid so ?all? are assumed? or ?none? +FLID is well supported by all vendors NOTE: most eveyone supports characters 32-127 Everex supports 32,33,35-126 ROCKWELL RC9624AC supports 32,33,35-96 123-126 NOTE: watch out for handling of "s around the +FLID string. NOTE: watch out for concatenating strings NOTE: some vendors implement the +FLID in non-volative RAM and some fax/modem models may not have the NVRAM chip and the +FLID will not be stored/transmitted correctly. +FLNFC is implemented by Everex and Multi-Tech and supports the conversion of 1D where there is a length mismatch +FLPL is implemented by Everex, Frecom, Multi-Tech, ROCKWELL 2496 models and all SIERRA models. +FMDL is well supported by all vendors +FMFR is well supported by all vendors +FMINSP seems to be implemented in Everex, Frecom, Multi-Tech, ROCKWELL 2496 models, and all SIERRA models. +FPHCTO seems to be supported by Everex, Frecom, Multi-Tech, all ROCKWELL models, and all SIERRA models. +FPTS seems to be supported by Everex, Frecom, Multi-Tech, all ROCKWELL models, and all SIERRA models. +FRBC is not implemented by anyone! +FREL is advertised as supported by Everex, Frecom, Multi-Tech, ROCKWELL 2496 models, and all SIERRA models. But I have not been able to verify the correct operation of the byte alignment. +FREV seems to be implemented in most firmware with various formats. The most informative are the "version,date,chipset" type which give all the necessary information to work detect firmware version and chipset version to work around any problems. +FSPL seems to be implemented by Everex, Frecom, Multi-Tech, ROCKWELL 2496 models and all SIERRA models. +FTBC seems to be implemented in older ROCKWELL 2496 models and all SIERRA models. +FVRFC doesn't seem to be implemented by anyone except Everex and Multi-tech who both do 1D vertical resolution conversions. No one does 2D vertical resolution conversions. +FWDFC doesn't seem to be implemented by anyone except Everex (who only abort a connection on mismatch) and Multi-tech (who actually do width conversions). _________________________________________________________________ Sam Leffler. Last updated $Date: 1994/10/19 23:53:53 $.