Hi Ben, The CMV document is attached. The zip file includes a PDF document and an Excel sheet. The Excel sheet has the latest changes for each CMV and the PDF file has the general description of the CMVs.
In the driver, we do the following: 1- Load the L1 code ( DSP code ) to the modem. 2- Configure the modem. 3- Tell the modem to start negotiation with the CO. 4- Monitor the negotiation until the modem goes to the operational mode. 5- After the operational state, monitor the link. (if the link is bad, we bring down the link and start the negotiation again.) - We write CMVs to the modem to configure the modem.(step 2) - We read CMVS from the modem to monitor the link/ modem activity ( steps 4 & 5 ) - CO ( Central Office == DSLAM ). - Why do we have a CMV.txt file? ISPs have different DSLAMs (from different CO chip vendors ). In order to get our modem working with all the DSLAMs, we sometimes need to configure the modem differently. The best way to handle this is to read the CMVs from a file and write them to the modem before negotiation. - I had a quick look at the problems reported by the users and in almost all of the cases, having the driver properly installed, modem goes to the operational state ( with one exception ??? ). So, with a good confidence we can assume that the cmv.txt implementation is working fine. For the cases that the modem does not go to operational, two possible cases come to my mind: first, DSP code is not loaded properly(could be OS related). In this case, we should not be able to read any CMVs. second, the negotiation with CO fails. Here, we can read cmvs but the modem does not go to OPERATIONAL. CMV "STAT 0" is used to monitor the link status ( refer to cmv manual for the details ) Please study the document and send me the questions. I will try to answer them within 5 working days. Regards, Farinam
<<attachment: EagelUsbDoc_041205.zip>>
