Skip to content

Commit 5feaf84

Browse files
ehsan6shaehsan6sha
committed
added interaction with explorer doc
1 parent a3666f6 commit 5feaf84

File tree

4 files changed

+242
-0
lines changed

4 files changed

+242
-0
lines changed

‎docs/functionyard/troubleshooting/disconnected-blox.md‎

Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,104 @@
1+
# Disconnected Blox Troubleshooting
2+
3+
If your FxBlox appears disconnected or is not responding properly, you can diagnose the issue by checking the LED color patterns. Follow the appropriate troubleshooting steps based on what you observe.
4+
5+
## Step 1: Check LED Color Status
6+
7+
First, observe your FxBlox LED to determine its current state:
8+
9+
### Scenario 1: Continuously Flashing Cyan LED
10+
11+
**What it means**: Your FxBlox needs to be set up from scratch.
12+
13+
**Solution**:
14+
1. **Uninstall the FxBlox app** from your mobile device
15+
2. **Reinstall the FxBlox app** from your app store
16+
3. **Open the app** and follow the setup process
17+
4. **Set up your FxBlox from the beginning** as if it were a new device
18+
19+
:::info
20+
A continuously flashing cyan LED indicates the device is in setup mode and ready for initial configuration.
21+
:::
22+
23+
### Scenario 2: LED is Off
24+
25+
**What to do**: Test the firmware status with a power cycle.
26+
27+
**Steps**:
28+
1. **Unplug your FxBlox** from power
29+
2. **Plug it back in** and observe the LED sequence
30+
3. **Check the LED pattern**:
31+
- If you see: **Blue → Green → Off → Yellowish → Off**
32+
- This means your FxBlox is on the latest firmware
33+
34+
**If on latest firmware, perform factory reset**:
35+
1. After confirming the firmware sequence (blue → green → off → yellow → off)
36+
2. **Unplug and replug the device 4 times**
37+
- Each time, wait for the sequence: yellow → off
38+
- Then unplug and plug back in
39+
3. **On the 4th replug** (5th total including the initial test):
40+
- The LED will turn yellow, then **immediately purple**
41+
4. **Wait 10 minutes** while it processes
42+
5. After 10 minutes, it will start **flashing cyan**
43+
6. **Uninstall and reinstall** the FxBlox app
44+
7. **Set up from the beginning**
45+
46+
:::warning
47+
Make sure to wait for the complete yellow → off sequence before each unplug/replug cycle. Timing is important for this reset process.
48+
:::
49+
50+
### Scenario 3: Bluetooth Connection Method
51+
52+
If the above methods don't work, try connecting via Bluetooth:
53+
54+
**Steps**:
55+
1. **Open the FxBlox app**
56+
2. **Go to Settings → Bluetooth Commands**
57+
3. **Click the connect icon** in the top right corner
58+
4. The app will attempt to connect via Bluetooth to your Blox
59+
5. **If connection succeeds**, you'll see several buttons appear
60+
6. **Click "Hotspot"** to put your Blox into hotspot mode
61+
7. **Connect your mobile phone** to the "FxBlox" WiFi network
62+
8. **In the app**, click the **down arrow next to "Disconnected"**
63+
9. **Click "Connect to WiFi"**
64+
10. **Follow the on-screen instructions** to reconnect your Blox to WiFi
65+
66+
:::tip
67+
The Bluetooth connection method is useful when your Blox can't connect to WiFi but is still responsive via Bluetooth.
68+
:::
69+
70+
### Scenario 4: Re-imaging Required
71+
72+
If none of the above solutions work, you may need to re-image your FxBlox:
73+
74+
**For RK1 Model** (most common):
75+
- Follow the guide: [FxBlox Hardware RK1 Re-imaging](../hardware/fxblox-hardware-rk1-reimage.md)
76+
77+
**For Raspberry Pi Model**:
78+
- Follow the guide: [FxBlox Hardware RPi Re-imaging](../hardware/fxblox-hardware-rpi-reimage.md)
79+
80+
:::info
81+
Most FxBlox devices are RK1 models. If you're unsure which model you have, try the RK1 re-imaging process first.
82+
:::
83+
84+
## LED Color Reference
85+
86+
| LED Pattern | Meaning | Action Required |
87+
|-------------|---------|----------------|
88+
| Continuously flashing cyan | Setup mode | Reinstall app and setup from scratch |
89+
| Blue → Green → Off → Yellow → Off | Latest firmware detected | Perform 4x unplug/replug reset |
90+
| Yellow → Purple | Factory reset in progress | Wait 10 minutes |
91+
| Flashing cyan (after reset) | Ready for setup | Reinstall app and setup |
92+
| Off/No response | Possible hardware issue | Try Bluetooth method or re-imaging |
93+
94+
## Additional Support
95+
96+
If you continue to experience issues after trying these troubleshooting steps:
97+
98+
1. Check our [Support page](../support.md) for additional resources
99+
2. Visit our community channels for peer assistance
100+
3. Contact support with your specific LED pattern and model information
101+
102+
:::warning
103+
Always ensure your FxBlox is properly powered and connected to a stable power source before beginning troubleshooting procedures.
104+
:::

‎docs/functionyard/troubleshooting/index.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Troubleshooting
2+
3+
This section contains solutions to common issues you might encounter while using FxBlox and the Functionland ecosystem.
4+
5+
## Common Issues
6+
7+
### Reward Claiming Problems
8+
9+
If you're having trouble claiming your rewards through the FxBlox app, we have alternative methods available:
10+
11+
- **[Manual Claim Rewards](manual-claim-rewards.md)** - Step-by-step guide to claim rewards directly from the blockchain explorer
12+
13+
### Connection and Setup Issues
14+
15+
If your FxBlox appears disconnected or unresponsive:
16+
17+
- **[Disconnected Blox](disconnected-blox.md)** - LED-based troubleshooting guide to diagnose and fix connection issues
18+
19+
## Getting Additional Help
20+
21+
If you can't find a solution to your problem in this troubleshooting section:
22+
23+
1. Check our [Support page](../support.md) for general support resources
24+
2. Visit our community channels for peer assistance
25+
3. Contact our support team for personalized help
26+
27+
:::tip
28+
Before reaching out for support, try the troubleshooting steps provided here. Many common issues can be resolved quickly with these guides.
29+
:::
30+
31+
## Contributing to Troubleshooting
32+
33+
Found a solution to a problem not covered here? Help the community by contributing to our documentation. Check out our [contribution guidelines](../../introduction/contribute/contribute.md) to learn how you can help improve these docs.

‎docs/functionyard/troubleshooting/manual-claim-rewards.md‎

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
# Manual Claim Rewards
2+
3+
If the "Claim Rewards" button in the FxBlox app is not working or the transaction fails, you can manually claim your rewards directly from the blockchain explorer. Follow these step-by-step instructions:
4+
5+
## Prerequisites
6+
7+
- You must have a Web3 wallet (like MetaMask) installed and connected
8+
- You need to have completed at least one transaction that generated rewards
9+
10+
## Step-by-Step Instructions
11+
12+
### Step 1: Find Your Transaction Details
13+
14+
1. **Go to the Pool Contract Explorer**
15+
16+
Navigate to: [https://elated-tan-skat.explorer.mainnet.skalenodes.com/address/0xF7c64248294C45Eb3AcdD282b58675F1831fb047](https://elated-tan-skat.explorer.mainnet.skalenodes.com/address/0xF7c64248294C45Eb3AcdD282b58675F1831fb047)
17+
18+
2. **Find Your Transaction**
19+
20+
Look through the transaction list to find your transaction and click on the **transaction hash** to view details.
21+
22+
3. **View Transaction Details**
23+
24+
Click on **"View Details"** to expand the transaction information.
25+
26+
4. **Copy Required Information**
27+
28+
From the transaction details, copy and save the following values:
29+
- **peerid** - Your peer identifier
30+
- **poolid** - The pool identifier
31+
32+
:::tip
33+
Keep these values handy as you'll need them in the next steps. You can paste them in a text file temporarily.
34+
:::
35+
36+
### Step 2: Manually Claim Rewards
37+
38+
1. **Go to the Contract Interface**
39+
40+
Navigate to: [https://elated-tan-skat.explorer.mainnet.skalenodes.com/address/0xF7c64248294C45Eb3AcdD282b58675F1831fb047?tab=read_write_proxy](https://elated-tan-skat.explorer.mainnet.skalenodes.com/address/0xF7c64248294C45Eb3AcdD282b58675F1831fb047?tab=read_write_proxy)
41+
42+
2. **Connect Your Wallet**
43+
44+
Click the **"Connect Wallet"** button and approve the connection in your Web3 wallet.
45+
46+
3. **Find the claimRewards Function**
47+
48+
Scroll down to find **"claimRewards"** and click the arrow to expand it.
49+
50+
4. **Enter Your Information**
51+
52+
Fill in the required fields:
53+
- **peerid**: Enter the peerid you copied from Step 1
54+
- **poolid**: Enter the poolid you copied from Step 1
55+
56+
5. **Execute the Transaction**
57+
58+
- Click the **"Write"** button
59+
- Your wallet will prompt you to approve the transaction
60+
- Click **"Approve"** in your wallet to complete the claim
61+
62+
:::success
63+
Once the transaction is confirmed on the blockchain, your rewards will be claimed and transferred to your wallet!
64+
:::
65+
66+
## Troubleshooting
67+
68+
### Common Issues
69+
70+
**Wallet Connection Problems**
71+
- Make sure you're connected to the correct network (SKALE Mainnet)
72+
- Try refreshing the page and reconnecting your wallet
73+
74+
**Transaction Fails**
75+
- Ensure you have enough gas fees in your wallet
76+
- Double-check that the peerid and poolid are entered correctly
77+
- Wait a few minutes and try again if the network is congested
78+
79+
**Can't Find Transaction**
80+
- Make sure you're looking at the correct contract address
81+
- Check that your transaction was actually processed on the mainnet
82+
83+
### Need More Help?
84+
85+
If you continue to experience issues with manual reward claiming, please:
86+
87+
1. Check our [Support page](../support.md) for additional resources
88+
2. Join our community channels for assistance
89+
3. Contact our support team with your transaction details
90+
91+
:::warning
92+
Always double-check the contract addresses and ensure you're on the correct network before executing any transactions. Never share your private keys or seed phrases with anyone.
93+
:::

‎sidebars.js‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -214,6 +214,18 @@ const sidebars = {
214214
},
215215
]
216216
},
217+
{
218+
type: 'category',
219+
label: 'Troubleshooting',
220+
link: {
221+
type: 'doc',
222+
id: 'functionyard/troubleshooting/index',
223+
},
224+
items: [
225+
'functionyard/troubleshooting/manual-claim-rewards',
226+
'functionyard/troubleshooting/disconnected-blox',
227+
]
228+
},
217229
],
218230
mvpSidebar: [
219231
{

0 commit comments

Comments
 (0)