• State TI Thinks Resolved
  • Locked Locked
  • Replies 41 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 729 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1310: After running the SimpleLink SDK TI 15.4 Stack Plugin protocol stack routine for about five minutes, the collector serial port does not print data.

Yolande Wang
Prodigy 540 points
Part Number: CC1310
Other Parts Discussed in Thread: CC3220SF

Hi Team,

There's an issue from the customer need your help:

The customer use SimpleLink SDK TI 15.4 Stack Plugin examples,

Under the premise of using the three-terminal routine of the sensor coprocessor collector, I connected to 38 sensor nodes, and the data can be transmitted stably. After running for about 5 minutes,

The collector serial port no longer prints data, but observe that the coprocessor's serial port is still sending data. Attached picture

You can see the timestamp in the picture above,

The left side is the serial port output of the coprocessor, and the right side is the serial port output of the collector. It is still outputting data at 15:03 minutes, while the last print on the right side is at 16:57 minutes, and it will never print again. May I ask? What is the reason for this and how to solve it?

Restarting the serial port has no effect

Thanks & Regards,

Yolande

  • 0
    TI__Intellectual 1230 points

    Hi Yolande, 

    I need some more details first.

    What version of the sdk is the customer using?

    What kind of configurations are used? (Which mode are the sensors and collector running on? What type of PHY is used?)

    Is the coprocessor printing out data that is received from the sensors, or printing out data that the collector sends out to the sensors?

    How often are the sensors sending data to the collector?

    Are you able to measure the interface between MAC-CoP and Host(collector), and see if data is still sent to the host?

    Could you ask the customer if they could do a test on 16 nodes for example. Could be that 38 nodes is to much for the collector to handle.

    Regards, 

    Marvin

  • 0 in reply to Marvin Ademi
    TI__Prodigy 540 points

    Hi Marvin,

    Here are the answers from the customer：

    Version number: simplelink_sdk_ti_15_4_stack_plugin_2_20_00_05

    Use default configuration (non-beacon mode, PHY 130)

    The coprocessor serial port prints the data sent to the collector.

    The frequency of sending data is the default 40 seconds

    It has been determined that the host has not received data and the coprocessor is still sending to the serial port.

    Tested on 20 nodes, the situation is the same,

    By the way, how many sensor nodes can CC1310 use the current SDK to connect to and run stably under the current version?

    Thanks & Regards,

    Yolande

  • 0 in reply to Yolande Wang
    TI__Intellectual 1230 points

    Hi again Yolande,

    According to LNT results that we run internally, stable performance was almost achieved with 150 nodes, running with a 50kbps PHY. LNT is large network testing. The amount of nodes should therefore not be an issue.

    How are they logging the data? 

    I will look into it and come back with an answer.

    Regards,

    Marvin 

       

  • 0 in reply to Marvin Ademi
    TI__Prodigy 540 points

    Hi Marvin,

    They used UartAssist.exe serial port debugging assistant to record serial port messages.

    Thanks & Regards,

    Yolande

  • 0 in reply to Yolande Wang
    TI__Intellectual 1230 points

    Hi Yolande,

    They should first be completely certain that the CoProcessor is sending data to the Collector. I can see that it s printing out data it receives, but have they tried measuring the TX pin and see the actual data is sent? 

    Are they using a linux machine as gateway? If they are using the linux gateway example that we provide they will have Gateway Application Web interface, where they have an overview over what sensors are connected and the data the collector is receiving. The linik is here: https://dev.ti.com/tirex/explore/content/ti154stack_linux_x64_4_20_00_05/docs/ti154stack/html/ti154stack-linux/linux-running-the-example-applications.html

    Since the sensors are still connected to the network and the CoProcessor is receiving data, the collector is still working. 

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    TI__Prodigy 540 points

    Hi Marvin,

    They are using CC3220 as the gateway, cc1310 as the coprocessor, and cc1310 as the sensor node.The TX pin of the test coprocessor has been sending data, but the 3220 collector did not receive the data.As shown in the first picture.

    Thanks & Regards,

    Yolande

  • 0 in reply to Yolande Wang
    TI__Intellectual 1230 points

    Okey, I understand.

    Which SDK version and software example are they using for the CC3220?

    Which SDK version is used for the CC1310?

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    TI__Prodigy 540 points

    Hi Marvin,

    3220 use:simplelink_sdk_ti_15_4_stack_plugin_2_20_00_05 

    1310 use:SimpleLink CC13x0 SDK  Latest (currently 4.20.02.07)

    Thanks & Best regards,

    Yolande

  • 0 in reply to Marvin Ademi
    TI__Prodigy 540 points

    Hi Marvin,

    Is there any update.

    Thanks & Regards

    Yolande

  • 0 in reply to Marvin Ademi
    TI__Prodigy 540 points

    Hi team，

    It was to be hoped that some constructive comments would be taken into account.

    Thanks & Best regards,

    Yolande

  • 0 in reply to Yolande Wang
    TI__Intellectual 1230 points

    Hi again Yolande,

    I have gotten the CC3220 device and will try to make the same setup. I will hopefully return with an answer by next week. Apologies for the delay.

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    TI__Prodigy 540 points

    Hi Marvin,

    Thank you for your help and we look forward to hearing from you.

    Thanks & Best regards,

    Yolande

  • 0 in reply to Yolande Wang
    TI__Intellectual 1230 points

    Hi Yolande,

    I have done the setup. Can I ask which mode you are running on(FH, beacon or non beacon)?

    Regards,

    Marvin 

  • 0 in reply to Marvin Ademi
    TI__Prodigy 540 points

    Hi Marvin,

    In non-beacon mode, the only modifier point in the routine is CONFIG_PHY_ID modified to APIMAC_GENERIC_CHINA_LRM_433_PHY_130.

    Thanks & Best regards,

    Yolande

  • 0 in reply to Yolande Wang
    TI__Intellectual 1230 points

    Is the customer using the hex files for the coprocessor and sensor that are provided in the stack plugin?

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    Using the coprocessor and sensor HEX files provided in the stack plugin

  • 0 in reply to faker wang
    TI__Intellectual 1230 points

    The coprocessor and sensor files have already compiled with a specific PHY(CONFIG_PHY_ID ). It can therefore be problematic to change the CONFIG_PHY_ID for the cc3220. As we discussed in the other thread, I will look into where to find the source project for coprocessor and sensor used in the stack plugin.

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    Yes, we can test the problems in our project in the simulation environment after we find the source code of the coprocessor supporting this stack plug-in.

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    May I ask what mode was used for the stable operation of the 150 nodes and 50kbps PHY mentioned earlier? Beacon mode, non beacon mode, or FM mode? What is the interval for transmitting data? Can low power consumption mode be achieved? Our current work scenario is also like this. Can you provide some assistance to help us work faster in this scenario?

  • 0
    Intellectual 436 points

    Part Number: CC1310

    Hi Guys:

    we have some questions want to discuss with you:

    1. The System Architecture:

    a. Our Gateway use the CC3220SF (Ext MCU) + CC1310 (CoProcessor)  for a Gateway.

    b. 51 pcs Sensor(use CC1310).

    c. CoPrecessor and the Sensors using the TI 15.4 Stack.

    2. SimpleLink SDK Version Information:

    a. External MCU(CC3220SF): Running the simplelink_sdk_ti_15_4_stack_plugin_2_20_00_05.

    b. CoProcessor(CC1310): Running the Hex(cc3220_coprocessor_cc1310lp.hex) below the folder of the simplelink_sdk_ti_15_4_stack_plugin_2_20_00_05.

    c. Sensors(CC1310): Running the Hex(sensor_cc1310lp_noFH.hex) below the folder of the simplelink_sdk_ti_15_4_stack_plugin_2_20_00_05.

    Five sets of data were tested, and the test data is as follows:

    3. Custom Modify Action:

    a. we just modifies the CONFIG_ PHY_ ID to APIMAC_ GENERIC_ CHINA_ LRM_ 433_ PHY_ 130.

    b. all of others as same as the SDK.

    4. Test Result:

    1. I found that some sensor can not join the Network in the 5 times Test.

    2. every Test, the sensor which can not join the Network is not same.

    3. every Test, the sensor which can not join the Network always send little massage successful.

    4. all of the Test, the data loss rate is high, the highest is 26.61%.

    5. all of the sensors's RSSI which can join the Network is -30dB~-50dB, and the RF Hardware design is refer to the TI's Demo, so we don't think the Bug come from the Hardware. 

    could you pls give us some help to analysis, what should we do next to find the issue?

    the test result like here:

    Test Times Total testing time Number of sensor Number of joined sensor Number of data send by sensor we set Number of data received by CoP+MCU Data loss rate
    1st 67min 51 47 5151 4067 21.04%
    2nd 117min 51 48 8976 6802 24.22%
    3rd 73min 51 48 5610 4484 20.07%
    4th 117min 51 46 8925 6550 26.61%
    5th 157min 51 45 12036 8920 25.89%

  • 0 in reply to faker wang
    Intellectual 436 points

    your test system architecture is mcu(CC3220SF)+CoP(CC1310) for a gateway?  the sensor use the CC1310? If your architecture is like this, what the SDK version do you use on the mcu(CC3220SF)+CoP(CC1310) and the Sensor(CC1310) ?

  • 0 in reply to faker wang
    TI__Intellectual 1230 points

    Hi,

    The test were done for FH, Beacon and non beacon mode. However, for beacon mode, only 50 nodes were used for the test.

    The transmission interval was not provided. 

    What do you mean by low power consumption mode?

    Regards,

    Marvin

  • 0 in reply to faker wang
    TI__Intellectual 1230 points

    I used this one: 15_4_stack_plugin_2_20_00_05

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    Hi.

    Can you provide a more complete solution? For example, as mentioned above

    1  collector，coprocessor，sensor  OR  collertor，sensor

    2  Which version of sdk does the protocol stack use?

    3  We currently use 15_4_stack_plugin_2_20_00_05   Can you realize the stable transmission of 150 nodes mentioned above?

    4  The low-power mode I mentioned above means that the device enters sleep when it is not transmitting data.

    5  Have you found the source code project of this plug-in? At present, we hope to use this scheme and find the corresponding source project as soon as possible.

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    Excuse me, has the non-beacon mode ever tested the above 150 nodes, and can it achieve stable transmission?Can the stable transmission of the above situation be achieved by using cc3220 stack plug-in?

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    Can you provide a detailed test report when testing 150 nodes? For example, information such as connection distance, packet loss rate, and test duration

    We use simplelink_ SDK_ Ti_ 15_ 4_ Stack_ Plugin_ 2_ 20_ 00_ 05 stack plugin testing in non beacon mode, with a slightly higher packet loss rate for 50 sensor nodes. The detailed data is shown in the figure. Did you modify the parameters in the firmware source code during the testing? Can you provide it to me for testing?

    Test Serial Number Total testing time Number of sensor Number of joined sensor Number of data send by sensor Number of data received by CoP+MCU Data loss rate
    1st 67min 51 47 5151 4067 21.04%
    2nd 117min 51 48 8976 6802 24.22%
    3rd 73min 51 48 5610 4484 20.07%
    4th 117min 51 46 8925 6550 26.61%
    5th 157min 51 45 12036 8920 25.89%
  • 0 in reply to faker wang
    Intellectual 436 points

    is there any update?

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    hey Marvin,is there any update?

  • 0 in reply to faker wang
    TI__Intellectual 1230 points

    These are the SDK used:

    simplelink_cc13x2_sdk_2_20_00_33_eng_t

    simplelink_cc13x0_sdk_2_20_00_20_eng

    I can provide you more information on the tests next week. Need to get hold of R&D.

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    hey Marvin,is there any update?

  • 0 in reply to faker wang
    TI__Intellectual 1230 points

    Hi,

    I propose you use the linux gateway solution instead: https://www.ti.com/tool/TI-15.4-STACK-GATEWAY-LINUX-SDK. It is more actively supported. We unfortunately don't  have the resources to help you further with this case on the stack plugin.

    However, I was able to fix the issue regarding finding coprocessor project that works with the stack plugin.

    1. Choose a coprocessor project from the SDK cc13x0 2_20_xx_xx. I used this SDK version: cc13x0_2_20_00_38.

    2. The problem with the coprocessor projects is that the uart pin routing does not match with the CC3220SF. The UART pins for the CC1310 are by default routed to IOID_2 and IOID_3, which don't match with the UART pins for CC3220SF. Go to CC13X0_LAUNCHXL.h file and find these lines of code:

    #define CC1350_LAUNCHXL_UART_RX IOID_2 /* RXD */
#define CC1350_LAUNCHXL_UART_TX IOID_3 /* TXD */

    Change it to this:

    #define CC1350_LAUNCHXL_UART_RX IOID_9 /* RXD */
#define CC1350_LAUNCHXL_UART_TX IOID_11 /* TXD */

    It should work after applying this change. 

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    Okay, I will try your suggestion. Thank you

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    Hi,

    Based on the modifications you described, I have tried and after modifying the UART pin, the network can now be successfully turned on

    Unfortunately, after I opened the network, the sensor could not join the network and could not even be searched. Attached is a screenshot of the serial port log:

      

    The above is the coprocessor log

    The above is the collector log

    The SDK version I am using: cc13x0_ 2_ 20_ 00_ thirty-eight

  • 0 in reply to faker wang
    Intellectual 436 points

    Hi  Marvin 

    We have basically completed testing using this stack plugin and hope to help us find the original 1310 coprocessor code and basic configuration to help us quickly build the project. Thank you

  • 0 in reply to faker wang
    TI__Intellectual 1230 points

    Hi,

    It does not seem that you have opened the network. You need to press the SW2 button on the CC3220.

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    The screenshot above did not capture PermitJoin-ON,

    I will send you the latest test logs






    Enabling devices to join and enabling 5 sensors,

    But unable to join

  • 0 in reply to faker wang
    TI__Intellectual 1230 points

    Have you made sure to only define one specific mode? Check the feature.h file on the sensor and collector project

    Regards,

    Marvin

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    Yes, I guarantee that both the collector and sensor use non beacon mode as shown in the figure. The left side is the collector, and the right side is the sensor

  • 0 in reply to Marvin Ademi
    Intellectual 436 points

    hi marvin

    I tried to download the sensor code again, as shown in the picture. A sensor was connected, but unfortunately, no data was received within two minutes after the connection. Additionally, the coprocessor automatically restarted, as shown in the attached image:

  • 0 in reply to faker wang
    Intellectual 436 points

    The following is a detailed log of the co processor uart:

    [2023-11-27 20:44:36.246]# RECV HEX>
    FE 14 42 81 6D 93 80 27 00 4B 12 00 80 00 00 00 00 00 00 00 00 00 00 00 57 FE 01 62 05 00 66 FE 10 42 84 F3 C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 E5 FE 01 62 33 00 50 FE 01 62 50 00 33
    [2023-11-27 20:44:37.259]# RECV HEX>
    FE 0C 42 91 03 6D 93 80 27 00 4B 12 00 01 00 01 DC
    [2023-11-27 20:44:37.428]# RECV HEX>
    FE 21 42 8D 00 02 BB AA 00 00 00 00 00 00 03 6D 93 80 27 00 4B 12 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FE 0C 42 91 02 01 00 00 00 00 00 00 00 01 00 01 DC
    [2023-11-27 20:44:45.193]# RECV HEX>
    FE 21 42 8D F3 02 01 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 0B
    [2023-11-27 20:44:59.364]# RECV HEX>
    FE 21 42 8D F3 02 03 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 09
    [2023-11-27 20:45:01.587]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:45:02.056]# RECV HEX>
    FE 01 62 05 00 66 FE 10 42 84 F3 81 00 00 00 00 00 00 00 00 00 00 00 00 00 00 A4
    [2023-11-27 20:45:02.289]# RECV HEX>
    FE 0C 42 91 02 02 00 00 00 00 00 00 00 01 00 01 DF
    [2023-11-27 20:45:04.063]# RECV HEX>
    FE 01 62 05 00 66 FE 10 42 84 F3 82 00 00 00 00 00 00 00 00 00 00 00 00 00 00 A7
    [2023-11-27 20:45:06.072]# RECV HEX>
    FE 01 62 05 00 66 FE 10 42 84 F3 83 00 00 00 00 00 00 00 00 00 00 00 00 00 00 A6
    [2023-11-27 20:45:37.395]# RECV HEX>
    FE 0C 42 91 02 01 00 00 00 00 00 00 00 01 00 01 DC
    [2023-11-27 20:45:45.181]# RECV HEX>
    FE 21 42 8D F3 02 01 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 0B
    [2023-11-27 20:45:59.361]# RECV HEX>
    FE 21 42 8D F3 02 03 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 09
    [2023-11-27 20:46:01.571]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:08.089]# RECV HEX>
    FE 01 62 05 00 66 FE 10 42 84 F3 84 00 00 00 00 00 00 00 00 00 00 00 00 00 00 A1
    [2023-11-27 20:46:10.090]# RECV HEX>
    FE 01 62 05 00 66 FE 10 42 84 F3 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 A0
    [2023-11-27 20:46:24.836]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:25.037]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:25.240]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:25.427]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:25.628]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:25.816]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:26.017]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:26.219]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:26.422]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:26.607]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:26.811]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:27.015]# RECV HEX>
    FE 0C 42 91 02 03 00 00 00 00 00 00 00 01 00 01 DE
    [2023-11-27 20:46:37.386]# RECV HEX>
    FE 0C 42 91 02 01 00 00 00 00 00 00 00 01 00 01 DC
    [2023-11-27 20:46:41.875]# RECV HEX>
    FE 06 41 80 04 03 01 02 00 01 C2 FE 01 62 01 00 62 FE 09 67 EE 01 0C 43 7E 22 00 4B 12 00 CB FE 01 62 09 00 6A FE 01 62 09 00 6A FE 01 62 09 00 6A FE 01 62 09 00 6A FE 01 62 09 00 6A FE 01 62 38 27 7C FE 01 62 30 27 74 FE 01 62 31 27 75 FE 01 62 30 27 74 FE 01 62 31 27 75 FE 01 62 30 27 74 FE 01 62 31 27 75 FE 01 62 09 00 6A FE 01 62 09 00 6A FE 01 62 0C 00 6F
    [2023-11-27 20:46:48.458]# RECV HEX>
    FE 16 42 8C EA 01 0A 82 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 BB FE 01 62 0C 00 6F
    [2023-11-27 20:46:54.855]# RECV HEX>
    FE 97 42 8C 00 00 0A 82 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 81 00 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF AF FE 01 62 09 00 6A FE 01 62 03 00 60 FE 01 42 8E 00 CD FE 02 62 08 00 00 68 FE 03 62 08 00 01 00 68 FE 09 62 08 00 0C 43 7E 22 00 4B 12 00 29 FE 03 62 08 00 BB AA 78 FE 01 62 09 00 6A
    [2023-11-27 20:47:37.389]# RECV HEX>
    FE 0C 42 91 02 01 00 00 00 00 00 00 00 01 00 01 DC
    [2023-11-27 20:47:45.155]# RECV HEX>
    FE 21 42 8D F3 02 01 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 0B
    [2023-11-27 20:48:37.381]# RECV HEX>
    FE 0C 42 91 02 01 00 00 00 00 00 00 00 01 00 01 DC
    [2023-11-27 20:48:45.164]# RECV HEX>
    FE 21 42 8D F3 02 01 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 0B
    [2023-11-27 20:49:37.366]# RECV HEX>
    FE 0C 42 91 02 01 00 00 00 00 00 00 00 01 00 01 DC
    [2023-11-27 20:49:45.155]# RECV HEX>
    FE 21 42 8D F3 02 01 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 0B
    [2023-11-27 20:50:37.369]# RECV HEX>
    FE 0C 42 91 02 01 00 00 00 00 00 00 00 01 00 01 DC
    [2023-11-27 20:50:45.130]# RECV HEX>
    FE 21 42 8D F3 02 01 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 0B
    [2023-11-27 20:51:37.348]# RECV HEX>
    FE 0C 42 91 02 01 00 00 00 00 00 00 00 01 00 01 DC
    [2023-11-27 20:51:45.126]# RECV HEX>
    FE 21 42 8D F3 02 01 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 0B
    [2023-11-27 20:52:37.339]# RECV HEX>
    FE 0C 42 91 02 01 00 00 00 00 00 00 00 01 00 01 DC
    [2023-11-27 20:52:45.113]# RECV HEX>
    FE 21 42 8D F3 02 01 00 00 00 00 00 00 00 02 BB AA 00 00 00 00 00 00 01 00 02 33 33 33 33 33 33 33 33 05 03 03 0B

  • 0 in reply to faker wang
    Intellectual 436 points

    It seems that the network of the coprocessor has been restarted. Could you please help me confirm the reason for this issue? Thank you