Changes for page Notes for Helium
Last modified by Edwin Chen on 2024/03/25 08:22
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Edwin - Content
-
... ... @@ -1,4 +1,4 @@ 1 -**~ Table ofContents:**1 +**~ Contents:** 2 2 3 3 {{toc/}} 4 4 ... ... @@ -5,11 +5,10 @@ 5 5 6 6 7 7 8 -= **1. 8 += **1. Use Dragino Gateways/Hotspots with Helium** = 9 9 10 -== **1.1 10 +== **1.1 Support Models** == 11 11 12 - 13 13 //There are three types of hotspots that can connect to Helium. They are (% style="color:#4f81bd" %)**full-hotspot**(%%), (% style="color:#4f81bd" %)**light hotspot** (%%)and (% style="color:#4f81bd" %)**data-only hotspot**(%%). Definition of these three types of hotspots can be found here: [[of Helium Hotspots>>url:https://docs.helium.com/mine-hnt%7CTypes]]. Different hotspots support different mining abilities.// 14 14 15 15 ((( ... ... @@ -23,10 +23,10 @@ 23 23 [[LPS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]], [[DLOS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]], 24 24 25 25 [[LG308>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]],[[LIG16>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]] 26 -)))|(% style="color:#4f81bd; width:126px" %)**Data-Only Hotspot**|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:203px" %)[[Data-Only Hotspot Instruction>>||anchor="H2. A0ConnectData-OnlyHotspottoHelium"]]25 +)))|(% style="color:#4f81bd; width:126px" %)**Data-Only Hotspot**|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:203px" %)[[Data-Only Hotspot Instruction>>||anchor="H2.ConnectData-OnlyHotspottoHelium"]] 27 27 |(% style="width:132px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% style="color:#4f81bd; width:126px" %)**Full Hotspo**t|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:203px" %)[[Full Hotspot Instuction-Not Finish>>doc:Main.User Manual for All Gateway models.HP0D.WebHome]] 28 28 29 - (% style="color:blue" %)**Frequencies on the Helium Network**28 +**Frequencies on the Helium Network** 30 30 31 31 * //The frequencies currently available are CN470/EU868/US915/AU915// 32 32 ... ... @@ -33,30 +33,26 @@ 33 33 (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]** 34 34 35 35 35 += **2. Connect Data-Only Hotspot to Helium** = 36 36 37 -= **2. Connect Data-Only Hotspotto Helium** =37 +== **2.1 Prerequisites** == 38 38 39 -== **2.1 Prerequisites** == 40 40 41 - 42 42 * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]// 43 43 42 +== **2.2 Step 1: Configure Frequency Band** == 44 44 45 -== **2.2 Step 1: Configure Frequency Band** == 46 46 47 - 48 48 //Each country has a requirement for frequency region. Choose the right one for your area.// 49 49 50 50 [[image:image-20220531175337-1.png]] 51 51 52 52 50 +== **2.3 Step 2: Download the Helium-gateway-rs** == 53 53 54 -== **2.3 Step 2: Download the Helium-gateway-rs** == 55 55 56 - 57 57 //Click Download Helium Server and the gateway will download the Helium-gateway-rs// 58 58 59 - 60 60 [[image:image-20220615150600-1.png||height="559" width="1045"]] 61 61 62 62 ... ... @@ -72,10 +72,9 @@ 72 72 [[image:image-20220615150717-3.png||height="605" width="1039"]] 73 73 74 74 70 +== **2.4 Step 3: Install the Helium-gateway-rs** == 75 75 76 -== **2.4 Step 3: Install the Helium-gateway-rs** == 77 77 78 - 79 79 //Click **Install Helium Server** to install gateway-rs.// 80 80 81 81 [[image:image-20220615150734-4.png||height="619" width="1035"]] ... ... @@ -82,30 +82,25 @@ 82 82 83 83 Install the Helium gateway-rs 84 84 85 - 86 86 (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.** 87 87 88 88 82 +== **2.5 Step 4: Save&start the Helium Server** == 89 89 90 -== **2.5 Step 4: Save&start the Helium Server** == 91 91 92 - 93 93 //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.// 94 94 95 - 96 96 [[image:image-20220615150903-5.png||height="592" width="1031"]] 97 97 98 98 90 +//Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.// 99 99 100 -//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.// 101 - 102 102 [[image:image-20220615151057-6.png||height="580" width="1026"]] 103 103 104 104 95 +== **2.6 Step 5: Check Gateway Connection before onboarding** == 105 105 106 -== **2.6 Step 5: Check Gateway Connection before onboarding** == 107 107 108 - 109 109 //A hotspot can transfer data to Helium after finishing step4. We can add a device to Helium and see if the device can join Helium. For example, we add an LGT92 sensor and see below info.// 110 110 111 111 ((( ... ... @@ -118,13 +118,10 @@ 118 118 (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.** 119 119 120 120 110 +== 2.7 Step 6: Onboarding Data-Only Hotspot == 121 121 122 -== **2.7 Step 6: Onboarding Data-Only Hotspot** == 123 - 124 - 125 125 (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .** 126 126 127 - 128 128 //User can refer [[this link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]] for how to onboarding a data-only hotspot. After onboarding the data-only hotspot, user can see the hotspot on Helium Console.// 129 129 130 130 //Below are the steps we do as per above link here.// ... ... @@ -131,7 +131,7 @@ 131 131 132 132 133 133 ((( 134 - (% style="color:blue" %)//**1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**//120 +//**1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**// 135 135 ))) 136 136 137 137 (% class="box" %) ... ... @@ -158,15 +158,13 @@ 158 158 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 159 159 ))) 160 160 161 - 162 162 ((( 163 163 (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.** 164 164 ))) 165 165 166 166 167 - 168 168 ((( 169 - (% style="color:blue" %)//**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**//153 +//**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**// 170 170 ))) 171 171 172 172 (% class="box" %) ... ... @@ -199,15 +199,11 @@ 199 199 200 200 ((( 201 201 //We got the txn info from this step.// 186 +\\//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**// 202 202 203 203 204 - 205 -(% style="color:blue" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**// 206 - 207 - 208 208 (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** 209 209 210 - 211 211 //Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.// 212 212 ))) 213 213 ... ... @@ -251,9 +251,7 @@ 251 251 ))) 252 252 253 253 ((( 254 - 255 - 256 -(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 234 +//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 257 257 ))) 258 258 259 259 (% class="box" %) ... ... @@ -307,21 +307,19 @@ 307 307 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 308 308 ))) 309 309 310 - 311 311 ((( 312 - (% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**289 +**Note: The add hotspot and assert location step might need some time to be effect.** 313 313 ))) 314 314 315 315 ((( 316 316 //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.// 317 317 318 - 319 319 320 320 ))) 321 321 322 -== **2.8 298 +== **2.8 Debug Connection** == 323 323 324 -=== **2.8.1 300 +=== **2.8.1 Check pkt-fwd running Log** === 325 325 326 326 327 327 //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// ... ... @@ -352,22 +352,20 @@ 352 352 ))) 353 353 354 354 331 +=== **2.8.2 Check gateway-rs Log** === 355 355 356 -=== **2.8.2 Check gateway-rs Log** === 357 357 358 - 359 359 //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 360 360 361 361 [[image:image-20220531175809-7.png]] 362 362 363 363 364 - (% style="color:red" %)**Note**:**logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**339 +**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system. 365 365 366 366 342 +=== **2.8.3 View the public key address and animal name** === 367 367 368 -=== **2.8.3 View the public key address and animal name** === 369 369 370 - 371 371 (% class="box" %) 372 372 ((( 373 373 ((( ... ... @@ -389,10 +389,8 @@ 389 389 Hostpot key and animal name 390 390 391 391 366 +=== **2.8.4 Backup/Restor gateway-rs key** === 392 392 393 -=== **2.8.4 Backup/Restor gateway-rs key** === 394 - 395 - 396 396 ((( 397 397 //For the date-only hotspots, the key is the only unique identifier, the users can backup the key by the button of Download. And once the uses upgrade the gateway or the gateway lose the key, the gateway-rs will generate a new key for which the data-only hotspot is the new unit. so if the user would restore to last time which can upload your backup key to the gateway by the button of upload.// 398 398 ))) ... ... @@ -400,24 +400,12 @@ 400 400 [[image:image-20220531175919-9.png]] 401 401 402 402 403 -=== **2.8.5 How to manually download helium gateway-rs via SSH access to the gateway Linux console** === 404 404 376 +== **2.9 Forward the data to the other server** == 405 405 406 -(% class="box infomessage" %) 407 -((( 408 -cd /tmp;wget -O helium-gateway-rs-dragino.ipk [[https:~~/~~/github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk>>https://github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk]] 378 +=== **2.9.1 Introduction** === 409 409 410 -opkg install helium-gateway-rs-dragino.ipk 411 -))) 412 412 413 -[[image:image-20230320141404-1.png]] 414 - 415 - 416 -== **2.9 Forward the data to the other server** == 417 - 418 -=== **2.9.1 Introduction** === 419 - 420 - 421 421 ((( 422 422 //The Dragino gateway has supports the double server settings.// 423 423 ))) ... ... @@ -425,29 +425,26 @@ 425 425 ((( 426 426 //Users can back to the page of Semtech UDP to configure other server settings.// 427 427 428 - 429 429 430 430 ))) 431 431 432 -=== **2.9.2 391 +=== **2.9.2 Example** === 433 433 434 434 435 435 //The following takes The Things Network as another LoRaWAN server as an example.// 436 436 437 437 397 +==== **2.9.2.1 Step 1: Back to Semtech UDP page** ==== 438 438 439 -==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ==== 440 440 441 - 442 442 [[image:image-20220531180002-10.png]] 443 443 444 444 Back to Semtech UDP page 445 445 446 446 405 +==== **2.9.2.2 Step 2: Configure the double server forwarding** ==== 447 447 448 -==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ==== 449 449 450 - 451 451 [[image:image-20220531180048-11.png]] 452 452 453 453 ... ... @@ -454,20 +454,17 @@ 454 454 //The user can configure the secondary server and then click the button of **Save&Apply**.// 455 455 456 456 414 +== **2.10 Connect Full Hotspot to Helium** == 457 457 458 -= =**2.10ConnectFull HotspottoHelium** ==416 += **3. Use Dragino Sensors with Helium** = 459 459 460 460 419 +== **3.1 How to add up user's end-node with Helium console** == 461 461 462 -= **3. Use Dragino Sensors with Helium** = 463 463 422 +=== **3.1.1 Step 1: Login the Helium console** === 464 464 465 -== **3.1 How to add up user's end-node with Helium console** == 466 466 467 - 468 -=== **3.1.1 Step 1: Login the Helium console** === 469 - 470 - 471 471 //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 472 472 473 473 [[image:image-20220531180150-12.png]] ... ... @@ -475,10 +475,9 @@ 475 475 login Helium console 476 476 477 477 432 +=== **3.1.2 Step 2: Add up your end-node's key** === 478 478 479 -=== **3.1.2 Step 2: Add up your end-node's key** === 480 480 481 - 482 482 //User add up end-node's key from console ~-~->dervice// 483 483 484 484 [[image:image-20220531180224-13.png]] ... ... @@ -486,10 +486,9 @@ 486 486 To add a device 487 487 488 488 442 +=== **3.1.3 Step 3:Activate the end-node** === 489 489 490 -=== **3.1.3 Step 3: Activate the end-node** === 491 491 492 - 493 493 ((( 494 494 //Users can activate the end-node with OTAA in which the end-node will Join the network from the Helium server **Eventually you will see traffic**// 495 495 ))) ... ... @@ -499,30 +499,19 @@ 499 499 end-node traffic. 500 500 501 501 454 +== **3.2 How to use decoder** == 502 502 503 -=== **3. 1.4CheckRawPayloadforEndNode** ===456 +=== **3.2.1 Step 1:Users can create decoders on functions** === 504 504 505 505 506 -Users can check what the end node has uplinked by checking the raw payload. as below: 507 - 508 -[[image:image-20220912161818-1.png]] 509 - 510 - 511 - 512 -== **3.2 How to use decoder** == 513 - 514 -=== **3.2.1 Step 1: Users can create decoders on functions** === 515 - 516 - 517 517 [[image:image-20220531105325-3.png]] 518 518 519 519 Decoder. 520 520 521 521 464 +=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** === 522 522 523 -=== **3.2.2 Step 2: Add a decoder in functions and apply it to the specified label** === 524 524 525 - 526 526 [[image:image-20220526095629-6.png]] 527 527 528 528 ... ... @@ -531,22 +531,18 @@ 531 531 532 532 [[image:image-20220526100057-8.png||height="352" width="1133"]] 533 533 475 + 534 534 **//Add decoder complete.//** 535 535 478 +=== **3.2.3 Where is the decoder?** === 536 536 537 - 538 -=== **3.2.3 Where is the decoder?** === 539 - 540 - 541 541 [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]] 542 542 543 543 [[image:image-20220617140118-1.png||height="550" width="883"]] 544 544 484 +== **3.3 How to send a downlink to end device from Helium** == 545 545 546 546 547 -== **3.3 How to send a downlink to end device from Helium** == 548 - 549 - 550 550 ((( 551 551 //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~:// 552 552 ))) ... ... @@ -561,7 +561,7 @@ 561 561 562 562 (% class="box" %) 563 563 ((( 564 - **01 00 00 3C ~-~-> AQAAPA==**501 +01 00 00 3C ~-~-> AQAAPA== 565 565 ))) 566 566 567 567 [[image:image-20220524171341-21.png]] ... ... @@ -569,12 +569,11 @@ 569 569 Downlink 570 570 571 571 509 +== **3.4 How to add integration to different IoT Servers** == 572 572 573 -== **3.4 How toadd integration to differentIoT Servers** ==511 +=== **3.4.1 TagoIO** === 574 574 575 -=== **3.4.1 TagoIO** === 576 576 577 - 578 578 **//The steps to add integration are very simple. Please see the following process.//** 579 579 580 580 ... ... @@ -615,10 +615,9 @@ 615 615 TagoIO. 616 616 617 617 554 +=== **3.4.2 Cayenne** === 618 618 619 -=== **3.4.2 Cayenne** === 620 620 621 - 622 622 //The process of creating devices is similar to Tago.// 623 623 624 624 [[image:image-20220526101616-18.png||height="456" width="1097"]] ... ... @@ -651,35 +651,11 @@ 651 651 Cayenne. 652 652 653 653 589 +== **3.5 Trouble Shooting** == 654 654 655 -== **3.5 Shooting** ==591 +=== **3.5.1 Trouble to Join Helium** === 656 656 657 657 658 -=== **3.5.1 Data-Only Hotspot is not connecting to Helium console** === 659 - 660 - 661 -//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**// 662 - 663 - 664 -1). The hotspot does not finish the onboarding to the helium blockchain. 665 - 666 - after the 23 version of the gateway-rs, Helium requests the user to onboarding the devices to the blockchain, otherwise, your devices can't connect to the helium console. ~-~--> Please refer to [[Step 2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Helium/#H2.7A0Step6:OnboardingData-OnlyHotspot]] to do it. 667 - 668 - 669 - 670 -=== **3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ** === 671 - 672 - 673 -Make sure your blockchain region is the same as your hotspot settings. For example, as below, the blockchain is CN region, and software is configure to EU. The hotspot is able to get the OTAA Join Request from End Device on EU region. but due to block chain is CN region, Server will send the Join -Accept in CN region, so end device can't get the OTAA Join Accept. 674 - 675 - 676 -For example, if you are in USA, you have to use the US915 frequency plan. More frequency plans details on the helium network: [[https:~~/~~/docs.helium.com/lorawan-on-helium/frequency-plans>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans]] 677 - 678 - 679 - 680 -=== **3.5.3 Trouble to Join Helium** === 681 - 682 - 683 683 ((( 684 684 **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 685 685 ... ... @@ -697,11 +697,10 @@ 697 697 ((( 698 698 //3) You have input the wrong keys into Helium Platform ( You can send us the screenshots for the keys and Dragino support team can check for you)// 699 699 700 - 701 701 702 702 ))) 703 703 704 -=== **3.5. 4Packet Loss for AU915 / US915 Band** ===614 +=== **3.5.2 Packet Loss for AU915 / US915 Band** === 705 705 706 706 707 707 ((( ... ... @@ -710,12 +710,10 @@ 710 710 711 711 ((( 712 712 //The reason for this problem is that the node does not lock the channel after joining the network.// 713 - 714 - 715 715 ))) 716 716 717 717 ((( 718 - (% style="color:red" %)**Solution:**626 +**Solution:** 719 719 720 720 721 721 ))) ... ... @@ -725,17 +725,15 @@ 725 725 ))) 726 726 727 727 * ((( 728 - (% style="color:blue" %)**//AT Command: AT+CHE//**636 +//AT Command: AT+CHE// 729 729 ))) 730 730 731 731 * ((( 732 -// **Example:(% style="color:#037691" %)**AT+CHE=2**(%%)640 +//Example:**AT+CHE=2** ~/~/set channel mode to 1// 733 733 ))) 734 734 735 735 * ((( 736 -(% style="color:blue" %)**//Downlink Command: 0x24//** 737 - 738 - 644 +//Downlink Command: 0x24// 739 739 ))) 740 740 741 741 ((( ... ... @@ -742,14 +742,14 @@ 742 742 //Format: Command Code (0x24) followed by 1 bytes channel value.// 743 743 ))) 744 744 745 - 746 746 ((( 747 747 //If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.// 748 748 ))) 749 749 750 750 * ((( 751 -// **Example 1**: Downlink Payload:(% style="color:#037691" %)**0x2402**(%%)~/~/ set channel mode to 2//656 +//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2// 752 752 658 + 753 753 754 754 ))) 755 755 ... ... @@ -759,14 +759,4 @@ 759 759 760 760 ((( 761 761 //The latest firmware for end node will have this bug fixed.// 762 - 763 - 764 - 765 -=== **3.5.5 ADR doesn't work in EU868 band.** === 766 - 767 - 768 -See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]] 769 - 770 - 771 - 772 772 )))
- image-20220912161818-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -53.7 KB - Content
- image-20230320141404-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -57.8 KB - Content