# Daily Logs -- SWC ###### tags: `Daily logs` This daily log is to store the process of implementing the MWNL project. You have to show the following elements New logs must be at the top of the document - What you have done today. - As detailed as possible. - The problem you are dealing with. - Why? - The problem you have solved. - How? :::warning > ## ***Stsheu: 對別人很認真在做的事情 要心存respect*** ::: ## 2023-12-20 - 流程圖 ## 2023-12-13 - time sync lib merge - Hao's nrf_esb.c = nrf_esb.c + time_sync.c - 只有需要的func - 有註解掉一些功能 - 基本上沒有修改太多功能,都是合併 - Logger for debug must set NRF_LOG_DEFERRED=0 - 卡死會卡住main同時卡住log process - Weekly Meeting - 要盡快開發準備DEMO給MOXA看 - 完成TS merge和CSA#1 - URLLC沒規範troughput,主要是End-End間傳輸時間小於1ms - 封包不會有先來後到的問題 - 用Wifi去打製造出干擾 - Meeting with Hao - nrf_esb.c和time_sync.c重複性很高 - TX需要自己實作 - ESB沒有要自己抓Timeslot - 用ESB處理sync pkt就好 - AFH - how to FH when ACK pkt error - 重構可以但盡快 - 完成示波器測試 ## 2023-12-12 - time sync - Testing PC->USBD-RX->ESB-TX/RX->USBD-TX->PC - ![1.4M pkt](https://hackmd.io/_uploads/S1N7XHSUT.png) - total 1.4M packects, 5 fail, 1422142/1422147=0.99999648…(99.9996%) - 100K掉包數跟1.4M相同(5 pkts) - 100K測試時PC有其他作業,半夜放著跑到1.4M沒有其他掉包 - 除掉包外有data error - data: {data}{seq_num} - 除此之外沒有其他類型資料損毀,不排除PC-RX問題 ## 2023-12-11 - 研究time sync <= `nordic-auko/nRF5-ble-timesync-demo` - 重構中... - USBD TX/RX - ESB TX/RX - 16Bytes data transmit test ## 2023-12-10 - Problem: Logger搞垮USBD - disable Logger - 減少輸出 - 參考新架構 https://github.com/nordic-auko/nRF5-ble-timesync-demo - 各種diff 找出改寫部分(Hao&TS) ## 2023-12-07 - 檢查 time sync 不間斷 ## 2023-12-06 - 僅同步第一次問題 - 在同步func內加入global遞增看呼叫幾次 - 老師Talk - Moxa 四零四科技 - for IIoT - Wireless做不到,目前都是Wired的Solution - 需要URLLC非Wi-Fi的Solution - 開發板是玩具,目標是將IC疊起來在lay在同一塊板子上減少體積產品化 - 干擾更嚴重 - 硬體廠商解決後需要軟體的操控 - 音訊傳播、家庭劇院?Bose喇叭不牽線? - NCC: 若使用至少15個無重疊之頻道,在0.4秒乘以跳頻頻道數之週期內,任一頻率佔用之平均時間不得超過0.4秒 - 不能完全搶走WiFi的使用 - WiFi會退避,藍牙可以不管 - node間資料傳輸和跳頻間隔須分開 - 完成產品化之間有無限多問題需要解決 - 不能只看到NCU的專題,要看MIT在幹嘛 - 要自己想可以改善的問題 - 不一定在要一塊controller底下,可以互相溝通,精進設計 - weekly meeting - 加入CAS#1 - 縮短間隔時間 - 目標Demo給404 ## 2023-12-05 - RX Python - 同時收集兩邊資料放入queue - 比較seq num丟棄重複資料 - - Problem - 其中一對斷開後錯誤率明顯提升 - 斷開原因? - 第一次同步後不再重新同步 ## 2023-12-01 - meeting with @Hao 1. python 和 esb_tx / esb_rx介接 2. 跳頻(固定票頻表)先略過掃頻那部分 3. 時間同步流程 4. EGU? - timer/counter - ppi - TO-DO - [ ] 2-pair RX/TX ## 2023-11-30 - trace: PC端跳頻表傳送、產生 - after rssi < thershold, keep channel disable until `disable_count` decrements to 0 from `DISABLE_LIMIT` ![image](https://hackmd.io/_uploads/HyLBd-8r6.png) - scanner board >>(rtt)>> PC >>(USB CDC ACM) >> TX board - trace: ESB - `nrf_esb_set_rf_channel(esb_chn_index)` - As a PTX, the application must wait for an idle state and as a PRX, the application must stop RX before changing the channel. After changing the channel, operation can be resumed. - ESB channel index not equal to BLE channel index - https://devzone.nordicsemi.com/f/nordic-q-a/39688/esb-rf-channels---recommended-to-be-2-to-81---how-do-they-map-to-ble-channels# - ![image](https://hackmd.io/_uploads/SJPG9Z8Sp.png) - 按照channel map順序一個一個跳 - **可加入CSA#1** - 透過PPI和timer觸發跳頻 - problem: 二對以上跳頻表互撞/two hop後再撞 - 不同channel map? - 不同start index? ## 2023-11-29 - weekly meeting - weekly goals: - [ ] data/rssi from scanner board to pc - [ ] transform rssi value to channel map - [ ] channel map from pc to TX board - [ ] receive channel map and setup ## 2023-11-28 - meeting with @Hao - trace: rx/tx架構 - urllc_pkt - ppi - timer/trigger - transmit data after time sync ## 2023-11-25 - 被老師電...