【正文】 10: }TDAddr。 8: }strAddr6。 5: struct{ 6: TIP6Addr addr6。 this section es to some technical details when integrating LwIP and EIPv6 together. The following discussion covers the aforementioned dualstack address, integration of network interface and prepile option. All these details are critical to code size and system performance. A. Dualstack AddressAs mentioned above, layers of TCP and API will be shared in the dual stack. Because of the difference between IPv4 address and IPv6 address, we have to design a unified format of address that can be used in the two layers. One possible solution is adopting IPv4patible IPv6 address, which is patible with IPv4 address by setting the first 96 bits to zeros and last 32 bits to IPv4 address. This type of address was proposed originally for tunneling technique, so it will be unfeasible in the following situations:? There are two special addresses in IPv6: loopback address and unspecified address. The first 64 bits of both addresses are zeros. So it is not capable to judge if an address is a real IPv6 address by checking the first 64 bits. ? The concept of address scope is one of the significant features of IPv6. There are three scopes of unicast address: sitelocal, linklocal and global. A global address is unique in the whole internet, while a linklocal address remains unique only in the scope of one specified interface. So there exists a same linklocal address which belongs to more than one interface even in the same node. In this case, it is not sufficient to determine the sending interface by providing only a linklocal address. As for this, RFC 4007 introduces a 32bits zone ID to mark an interface uniquely and requires that the zone ID of sending interface must be specified when the destination is a linklocal address. Furthermore, the information of zone ID is required to pass down through the destination address, and it is out of range of capacity of the patible address. To provide a more efficient and practical solution, we propose an innovative format of address named dualstack address ,which is used in API and TCP layers of dual stack. The structure of the dualstack address is defined as follows: 1: typedef struct _TDAddr{ 2: u8_t family。 ? Fullfeatured stateless address auto configuration, for a node to obtain automatically both linklocal and global addresses。 hence the protocol should be reduced to acmodate target platform. Considering that the TCP protocol already has a MSS (Maximum Segment Size) mechanism to control packets size to fit network MTU (Maximum Transmission Unit), fragmentation turns out unnecessary and is not supported in our implementation. In IPv6, there are one main header and six extension headers designed for specific purposes. Two of the six are for security purpose, and the other four are for fragmentation, forwarding and routing. EIPv6 assumes its target systems and applications to be the simplest case, which eliminates the support of extension headers. Similar reduction is made in the process of ICMPv6 error messages. Error messages are used to notify a transmission error that certain packet cannot be handed to its destination. In our implementation, the stack simply extracts parameters from these messages and reports it to the upper layer to stop any further transmission. Conclusively, EIPv6 provides the following functions: ? Basic IPv6 packet transmission。 ? An innovative method is developed to integrate addresses and interfaces of EIPv6 and LwIP together。 Dualstack。 IPv6。它克服了通訊距離短、性能不穩(wěn)定的缺點，真正實現(xiàn)無縫覆蓋。它的特點如下：低功耗、單電源電壓5V，應(yīng)用靈活、方便。它使用起來局限性小，功能強大，它能把數(shù)據(jù)發(fā)送到服務(wù)器里。解決方案：所以我認(rèn)為在以后可以采用GPRS通信模塊進行溫濕度的傳輸。其次，由于該系統(tǒng)工作的首要條件就是需要接入有線網(wǎng)絡(luò)。首先，農(nóng)作物環(huán)境監(jiān)控除了溫濕度之外還包括其他的各種環(huán)境信息，如光照信息。雖然我的設(shè)計已經(jīng)能夠完成題目要求，但是由于個人能力問題和時間問題，本設(shè)計仍有一些方面存在不足，需要改進的地方還有很多。開發(fā)板數(shù)據(jù)通信的傳輸層采用了TCP協(xié)議，保證了數(shù)據(jù)的可靠性。用戶界面端的開發(fā)采用了最新的QT技術(shù)，利用配套工具可方便的開發(fā)出豐富、友好的人機界面。雖然本系統(tǒng)只監(jiān)測溫濕度，但系統(tǒng)接口豐富、擴展性強，接入其他傳感器就能實現(xiàn)相應(yīng)環(huán)境數(shù)據(jù)的監(jiān)測，如光照，CO2等。 查詢溫濕度信息界面。 歷史信息查詢界面在查詢界面下，用戶可以根據(jù)查詢要求選擇所需要的信息，也可以選著顯示方式。 ARM板接收到的串口數(shù)據(jù)在服務(wù)器端啟動服務(wù)器程序，然后在QT2440開發(fā)版輸入服務(wù)器IP，開發(fā)板通過網(wǎng)絡(luò)服務(wù)將串口數(shù)據(jù)傳輸?shù)椒?wù)器。}4 系統(tǒng)連接和測試 系統(tǒng)各模塊的連接是先通過單片機采集數(shù)據(jù)后由串口線連接到QT2440開發(fā)板，QT2440開發(fā)板通過網(wǎng)線接入網(wǎng)絡(luò)。 uitableViewshow()。 modelsetHeaderData(1, Qt::Horizontal, tr(temperature))。)。 and date =39。 modelsetQuery(SELECT date,temperature FROM tem_hum WHERE date = 39。 +=( 23:59:59)。 +=( 00:00:00)。 uipushButton_2show()。 uilineEditshow()。 uilabelshow()。 uimonthEdithide()。 uipushButtonhide()。 uilabel_4hide()。 te_hu=0。 te_tab=1。}void select::sel1(){ tem=0。 tem_hum[1][i]=(2).toInt()。 if(()=1) { ()。+num_2+39。 num_2+=(%)。 if(i10) num_2+=(0)。i24。 num_1+=( )。 num_1+=()。 +=()。 ()。void select::sel() //查詢某一天的溫濕度記錄用曲線顯示出{ QString num_1。 return true。 return false。 (123)。//主機名字 (vegetable)。；（4）數(shù)據(jù)庫連接源碼bool Widget::createDataBase(){ QSqlDatabase db=QSqlDatabase::addDatabase(QMYSQL)。(`date`)PRIMARYNULL,char(20)NULL,char(20) NOT`date``tem_hum`環(huán)境日期時間溫度濕度 ER圖（2）根據(jù)上述ER圖，表的關(guān)系模式結(jié)構(gòu)如下所示：環(huán)境（日期時間，溫度，濕度）（3）建立數(shù)據(jù)庫CREATE由于其體積小、速度快、總體擁有成本低，尤其是開放源碼這一特點，許多中小型企業(yè)為了降低企業(yè)總體擁有成本而選擇了MySQL作為網(wǎng)絡(luò)數(shù)據(jù)庫。SQL是用于訪問數(shù)據(jù)庫的最常用標(biāo)準(zhǔn)化語言。這樣就增加了速度并提高了靈活性。 start()。 }//end if tcpServerConnectionclose()。ok,16))。 ((amp。ok,16)*10+(amp。 (date)。 QSqlQuery query。ok,16)))。 uilabel_5setText(QString::number((amp。ok,16)*10+(amp。ok,16)+(amp。ok,16)+(amp。 if((amp。 qDebug()tem2=tem2。 qDebug()hum2=hum2。 bool ok=true。 qDebug()inBlock:inBlock。 QString tem2=()[3]。 QString hum2=()[1]。 qDebug()size=size。void Widget::Receive(){ inBlock = tcpServerConnectionreadAll()。}服務(wù)器端接收到網(wǎng)絡(luò)上的數(shù)據(jù)后首先要對數(shù)據(jù)進行解析，然后對解析后的數(shù)據(jù)進行校驗，如果校驗正確，將數(shù)據(jù)插入數(shù)據(jù)庫，如果不正確，對數(shù)據(jù)作丟棄處理。 connect(tcpServerConnecti