@fy1000000
25My goal for this blog is to be a platform of information, learning & inspiration for those who are interested in lower power GPS & block chain technologies.
steemit.com/@fy1000000VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.034USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.001SP
├── Own SP
0.629SP
└── Incoming DelegationsDeleg
+4.372SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.629SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.372SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1023.578650 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7120.081156 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | fy1000000 |
| id | 634313 |
| rank | 665,118 |
| reputation | 133422689 |
| created | 2018-01-21T01:26:57 |
| recovery_account | steem |
| proxy | None |
| post_count | 25 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-06-20T17:55:24 |
| last_root_post | 2018-06-20T17:55:24 |
| last_vote_time | 2018-06-09T22:42:30 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1023.578650 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7120.081156 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 2018-05-13T23:56:45 |
| last_account_update | 2018-05-20T14:38:54 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 634313,
"name": "fy1000000",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM73sGX2JhTvia792treeyyoh3TCUnnZaRgwcDmyc8PbLMHhB1BQ",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5CuL3JcdeE78YxxNAcB8FaTsw1uq6Qgcz4rAscHE7NtKahey1i",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6T8d8AncrKqPiRJn3JbNR8RTMUebuEd46btVQaQadqHmYyS8CZ",
1
]
]
},
"memo_key": "STM6b8bAgoAp8DwecvzchNJm1sD8FonVon7eAHNfkxpSwYB6HK5ij",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://steemitimages.com/DQmVaqSwy7WszGohG7X6VqSTdtCnEA3TqoWwc5RqrZ95uzT/2015-9-29-22-2-58-42.jpg\",\"name\":\"fy1000000\",\"cover_image\":\"https://steemitimages.com/DQmZuEDSwpS7FdCs1jMHbXMzyMXC7CYnrpjHBCtGMd3d8pM/Untitled%20design.png\",\"location\":\"Calgary, Canada\",\"website\":\"http://www.basebandtech.com\",\"about\":\"My goal for this blog is to be a platform of information, learning & inspiration for those who are interested in lower power GPS & block chain technologies.\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://steemitimages.com/DQmVaqSwy7WszGohG7X6VqSTdtCnEA3TqoWwc5RqrZ95uzT/2015-9-29-22-2-58-42.jpg\",\"name\":\"fy1000000\",\"cover_image\":\"https://steemitimages.com/DQmZuEDSwpS7FdCs1jMHbXMzyMXC7CYnrpjHBCtGMd3d8pM/Untitled%20design.png\",\"location\":\"Calgary, Canada\",\"website\":\"http://www.basebandtech.com\",\"about\":\"My goal for this blog is to be a platform of information, learning & inspiration for those who are interested in lower power GPS & block chain technologies.\"}}",
"proxy": "",
"last_owner_update": "2018-05-13T23:56:45",
"last_account_update": "2018-05-20T14:38:54",
"created": "2018-01-21T01:26:57",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 25,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779064230
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779064230
},
"voting_power": 0,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "1023.578650 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7120.081156 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-06-20T17:55:24",
"last_root_post": "2018-06-20T17:55:24",
"last_vote_time": "2018-06-09T22:42:30",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 133422689,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 665118
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.372 SP to @fy10000002026/05/18 00:30:30
steemdelegated 4.372 SP to @fy1000000
2026/05/18 00:30:30
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 7120.081156 VESTS |
| Transaction Info | Block #106143753/Trx 1b49b07c701663de446d8113383efb552db8d9a9 |
View Raw JSON Data
{
"trx_id": "1b49b07c701663de446d8113383efb552db8d9a9",
"block": 106143753,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T00:30:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "7120.081156 VESTS"
}
]
}steemdelegated 2.707 SP to @fy10000002026/05/12 04:51:51
steemdelegated 2.707 SP to @fy1000000
2026/05/12 04:51:51
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 4407.870751 VESTS |
| Transaction Info | Block #105976938/Trx a64dd8b35a239e4777b68cb38008e52850dc90f1 |
View Raw JSON Data
{
"trx_id": "a64dd8b35a239e4777b68cb38008e52850dc90f1",
"block": 105976938,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-12T04:51:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "4407.870751 VESTS"
}
]
}steemdelegated 4.380 SP to @fy10000002026/04/25 23:50:57
steemdelegated 4.380 SP to @fy1000000
2026/04/25 23:50:57
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 7132.596912 VESTS |
| Transaction Info | Block #105511397/Trx c74536086afcf6474cfc3d82ebca556307fa184c |
View Raw JSON Data
{
"trx_id": "c74536086afcf6474cfc3d82ebca556307fa184c",
"block": 105511397,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-25T23:50:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "7132.596912 VESTS"
}
]
}steemdelegated 2.732 SP to @fy10000002026/01/23 08:29:00
steemdelegated 2.732 SP to @fy1000000
2026/01/23 08:29:00
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 4449.417570 VESTS |
| Transaction Info | Block #102852627/Trx 921056dd071c0688c59fb64fba5e1720abf52781 |
View Raw JSON Data
{
"trx_id": "921056dd071c0688c59fb64fba5e1720abf52781",
"block": 102852627,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-23T08:29:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "4449.417570 VESTS"
}
]
}steemdelegated 2.833 SP to @fy10000002024/12/17 03:47:33
steemdelegated 2.833 SP to @fy1000000
2024/12/17 03:47:33
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 4613.636767 VESTS |
| Transaction Info | Block #91299023/Trx 99942f2301b10da537f2a7c03172d53abbec381d |
View Raw JSON Data
{
"trx_id": "99942f2301b10da537f2a7c03172d53abbec381d",
"block": 91299023,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T03:47:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "4613.636767 VESTS"
}
]
}steemdelegated 2.937 SP to @fy10000002023/11/13 19:30:27
steemdelegated 2.937 SP to @fy1000000
2023/11/13 19:30:27
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 4782.770299 VESTS |
| Transaction Info | Block #79853222/Trx e0724a7d85368063f8756fe345a0e44275270d06 |
View Raw JSON Data
{
"trx_id": "e0724a7d85368063f8756fe345a0e44275270d06",
"block": 79853222,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-13T19:30:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "4782.770299 VESTS"
}
]
}steemdelegated 4.741 SP to @fy10000002023/09/21 22:07:36
steemdelegated 4.741 SP to @fy1000000
2023/09/21 22:07:36
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 7720.049085 VESTS |
| Transaction Info | Block #78348182/Trx 6aa9cf015bade42b67fd490f5df8a0b4e07c32c2 |
View Raw JSON Data
{
"trx_id": "6aa9cf015bade42b67fd490f5df8a0b4e07c32c2",
"block": 78348182,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-21T22:07:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "7720.049085 VESTS"
}
]
}steemdelegated 4.877 SP to @fy10000002022/11/03 11:53:03
steemdelegated 4.877 SP to @fy1000000
2022/11/03 11:53:03
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 7941.730523 VESTS |
| Transaction Info | Block #69113477/Trx acdeb137be24597d0a44f6a0c74e8e3cd1680688 |
View Raw JSON Data
{
"trx_id": "acdeb137be24597d0a44f6a0c74e8e3cd1680688",
"block": 69113477,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T11:53:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "7941.730523 VESTS"
}
]
}steemdelegated 5.012 SP to @fy10000002022/01/17 11:08:15
steemdelegated 5.012 SP to @fy1000000
2022/01/17 11:08:15
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 8162.263754 VESTS |
| Transaction Info | Block #60809629/Trx c6720a361f9372be7c10011f2ab562414adf44eb |
View Raw JSON Data
{
"trx_id": "c6720a361f9372be7c10011f2ab562414adf44eb",
"block": 60809629,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T11:08:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "8162.263754 VESTS"
}
]
}steemdelegated 5.125 SP to @fy10000002021/06/14 01:03:06
steemdelegated 5.125 SP to @fy1000000
2021/06/14 01:03:06
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 8346.032412 VESTS |
| Transaction Info | Block #54608009/Trx e423f0aa71e1b8f73c341dcad4177f71dc0074a8 |
View Raw JSON Data
{
"trx_id": "e423f0aa71e1b8f73c341dcad4177f71dc0074a8",
"block": 54608009,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T01:03:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "8346.032412 VESTS"
}
]
}steemdelegated 5.240 SP to @fy10000002020/12/11 11:21:21
steemdelegated 5.240 SP to @fy1000000
2020/12/11 11:21:21
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 8533.454386 VESTS |
| Transaction Info | Block #49355453/Trx 023f33675c4d504ca806f9b9b46536405a3ad9d0 |
View Raw JSON Data
{
"trx_id": "023f33675c4d504ca806f9b9b46536405a3ad9d0",
"block": 49355453,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T11:21:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "8533.454386 VESTS"
}
]
}steemdelegated 1.174 SP to @fy10000002020/12/06 04:58:30
steemdelegated 1.174 SP to @fy1000000
2020/12/06 04:58:30
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49207014/Trx 108ee6222c1affc5633385aca80e9582a3372faa |
View Raw JSON Data
{
"trx_id": "108ee6222c1affc5633385aca80e9582a3372faa",
"block": 49207014,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T04:58:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "1912.543513 VESTS"
}
]
}steemdelegated 5.244 SP to @fy10000002020/12/05 14:59:30
steemdelegated 5.244 SP to @fy1000000
2020/12/05 14:59:30
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 8539.662240 VESTS |
| Transaction Info | Block #49190548/Trx b9979a26cbdfb689882c62c56b997787ac864a59 |
View Raw JSON Data
{
"trx_id": "b9979a26cbdfb689882c62c56b997787ac864a59",
"block": 49190548,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T14:59:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "8539.662240 VESTS"
}
]
}steemdelegated 1.179 SP to @fy10000002020/11/02 16:08:00
steemdelegated 1.179 SP to @fy1000000
2020/11/02 16:08:00
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48258382/Trx 6e05d31b259246417eb80867c47ef5917c5a27c3 |
View Raw JSON Data
{
"trx_id": "6e05d31b259246417eb80867c47ef5917c5a27c3",
"block": 48258382,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-02T16:08:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "1920.017158 VESTS"
}
]
}steemdelegated 5.369 SP to @fy10000002020/05/09 05:56:06
steemdelegated 5.369 SP to @fy1000000
2020/05/09 05:56:06
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 8742.467599 VESTS |
| Transaction Info | Block #43217263/Trx c94dba5a99a7564280b0db89b61db01f3f35adf3 |
View Raw JSON Data
{
"trx_id": "c94dba5a99a7564280b0db89b61db01f3f35adf3",
"block": 43217263,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T05:56:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "8742.467599 VESTS"
}
]
}steemdelegated 1.200 SP to @fy10000002020/05/08 09:34:30
steemdelegated 1.200 SP to @fy1000000
2020/05/08 09:34:30
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43193406/Trx ddfb96009c184867e79aea86ea92d3236f642988 |
View Raw JSON Data
{
"trx_id": "ddfb96009c184867e79aea86ea92d3236f642988",
"block": 43193406,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T09:34:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "1953.311140 VESTS"
}
]
}2020/01/21 02:15:24
2020/01/21 02:15:24
| parent author | fy1000000 |
| parent permlink | what-is-snapshot-positioning-part-4-data-processing-module |
| author | steemitboard |
| permlink | steemitboard-notify-fy1000000-20200121t021524000z |
| title | |
| body | Congratulations @fy1000000! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@fy1000000/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@fy1000000) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=fy1000000)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #40109921/Trx 3ac71de532d4466dffcdbf7d810eef35f27f4bc5 |
View Raw JSON Data
{
"trx_id": "3ac71de532d4466dffcdbf7d810eef35f27f4bc5",
"block": 40109921,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-01-21T02:15:24",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "what-is-snapshot-positioning-part-4-data-processing-module",
"author": "steemitboard",
"permlink": "steemitboard-notify-fy1000000-20200121t021524000z",
"title": "",
"body": "Congratulations @fy1000000! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@fy1000000/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@fy1000000) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=fy1000000)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.456 SP to @fy10000002019/09/03 14:42:51
steemdelegated 5.456 SP to @fy1000000
2019/09/03 14:42:51
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 8883.923775 VESTS |
| Transaction Info | Block #36101399/Trx 0d668e67b44eed771f7b091abe2e60a75a587f36 |
View Raw JSON Data
{
"trx_id": "0d668e67b44eed771f7b091abe2e60a75a587f36",
"block": 36101399,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-09-03T14:42:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "8883.923775 VESTS"
}
]
}2019/03/29 13:39:21
2019/03/29 13:39:21
| voter | redfocs |
| author | fy1000000 |
| permlink | re-drumcrazy-external-links-open-in-new-window-steemit-edit-window-20180520t143140309z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #31579110/Trx e4b7add634bd6e90f421306879ebe6b852da7ce3 |
View Raw JSON Data
{
"trx_id": "e4b7add634bd6e90f421306879ebe6b852da7ce3",
"block": 31579110,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-03-29T13:39:21",
"op": [
"vote",
{
"voter": "redfocs",
"author": "fy1000000",
"permlink": "re-drumcrazy-external-links-open-in-new-window-steemit-edit-window-20180520t143140309z",
"weight": 10000
}
]
}2019/01/21 04:12:00
2019/01/21 04:12:00
| parent author | fy1000000 |
| parent permlink | what-is-snapshot-positioning-part-4-data-processing-module |
| author | steemitboard |
| permlink | steemitboard-notify-fy1000000-20190121t041157000z |
| title | |
| body | Congratulations @fy1000000! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@fy1000000/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_[Click here to view your Board](https://steemitboard.com/@fy1000000)_</sub> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #29639676/Trx 24c7afc7185f20a481155c86ad32e66f8f09ac4e |
View Raw JSON Data
{
"trx_id": "24c7afc7185f20a481155c86ad32e66f8f09ac4e",
"block": 29639676,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-01-21T04:12:00",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "what-is-snapshot-positioning-part-4-data-processing-module",
"author": "steemitboard",
"permlink": "steemitboard-notify-fy1000000-20190121t041157000z",
"title": "",
"body": "Congratulations @fy1000000! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@fy1000000/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_[Click here to view your Board](https://steemitboard.com/@fy1000000)_</sub>\n\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.577 SP to @fy10000002018/09/22 00:18:03
steemdelegated 5.577 SP to @fy1000000
2018/09/22 00:18:03
| delegator | steem |
| delegatee | fy1000000 |
| vesting shares | 9082.145578 VESTS |
| Transaction Info | Block #26152804/Trx dadff7a674af1c091333b769c24141c582be7192 |
View Raw JSON Data
{
"trx_id": "dadff7a674af1c091333b769c24141c582be7192",
"block": 26152804,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-22T00:18:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "fy1000000",
"vesting_shares": "9082.145578 VESTS"
}
]
}fy1000000published a new post: what-is-snapshot-positioning-part-4-data-processing-module2018/06/20 17:55:24
fy1000000published a new post: what-is-snapshot-positioning-part-4-data-processing-module
2018/06/20 17:55:24
| parent author | |
| parent permlink | technology |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning-part-4-data-processing-module |
| title | What is Snapshot Positioning? (Part 4 – Data Processing module) |
| body | # What is Snapshot Positioning? (Part 4 – Data Processing module) <div class="text-justify"><br>Welcome back to #BlockchainMyGPS!<br><br></div> <div class="pull-right"> <img src="http://basebandtech.com/wp-content/uploads/iStock_000002065973Small.jpg"> </div> <div class="text-justify">In the previous blog posts, I explained one advantage of #SnapshotReceiver which is, that, once the #GPS satellite signal has been captured, it does not need to be processed right away. This means that the parts which consume the most energy can be offloaded to a remote device sometime in the future.</div> <br>For reference purposes, you can find [Part-I](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning), [Part-II](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module) and [Part-III](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules) here. <div class="text-justify">In this blog post, I will be discussing how signal processing is performed in a snapshot receiver and what the advantages are.<br></div> ## #Ephemeris and #ExtendedEphemeris <div class="text-justify">The problem with older generations of snapshot receiver were the limiting requirements that made them undesirable for real-life use cases; these comprise of a valid Ephemeris, an approximate Time and Position of the receiver.<br><br></div> <div class="text-justify">Ephemeris describes a satellite’s position over a period of time. Conventional receiver obtains ephemeris by decoding the navigation message broadcast directly by the satellites, this downloading process consumes considerable amount of energy. Since the navigation message is broadcast at a very slow data rate – 50 bits per second, it takes ~30 seconds to download it. To make matters worse, when the receiver moves through poor signal areas such as high rise buildings, the incoming signal could be intermittently blocked and must be downloaded again. <br><br></div> <div class="text-justify">The GPS in my cellphone doesn’t seem to take 30 seconds to get a position. Why? Most smartphone-based GPS receiver get around this slow and energy-intense process by connecting to the wireless network to download the ephemeris from a server. This is typically referred to as Assisted GPS #AGPS. While this approach works very well for smartphones, the energy to operate a wireless radio often consumes more than it would by downloading the broadcast ephemeris.</div> <div class="text-justify"><br>An alternative to AGPS is Extended Ephemeris where an algorithm can predict the ephemeris for up to 28 days. A receiver can download the Extended Ephemeris file at a convenient time such as when it is being recharged. A receiver with Extended Ephemeris can operate autonomously without the need of additional ephemeris information, either from the satellite broadcasts or from a communication network.</div> <div class="text-justify"><br>Some new breed of conventional receivers has adopted a hybrid approach to combine Extended Ephemeris with occasional broadcast ephemeris download. This approach is suitable for applications that the receiver is ON most of the time (e.g. car navigation), the benefits for #Wearables and #IoT applications that prefer to be OFF most of the time is limited.<br></div> ## Approximate Time and Position <div class="text-justify">Older snapshot receivers also require a time accurate to sub-milliseconds to 60 seconds and position accurate to ~75km. While the rough time and position could be obtained from #WiFi or #Cell-ID, they offer little value for Wearables and IoT devices unless they are integrated with WiFi/Cell-ID radios. Fortunately, state of the art snapshot receiver has overcome these limitations without additional hardware.</div> <div class="text-justify"><br>NOTE: If you’re interested in knowing more about why GPS receivers take so long to get a position, you can find it [here].<br></div> ## Data Processing Module <div class="text-justify">Throughout the course of this ‘What is Snapshot Positioning?’ series, I have explained the basics of a snapshot receiver and three of its four discrete modules – Data Capture, Data Buffering and Data Storage modules. The last module – Signal Processing is a key differentiator between the state of the art snapshot receiver and the conventional receiver. </div> <div class="text-justify"><br>Signal processing involves the transformation of digitized IF data into ranging measurements (Code Phase and Doppler) and computing the receiver position using signal processing techniques.<br></div> <center>http://basebandtech.com/wp-content/uploads/Conceptual-GPS-receiver-components-output-files.png</center> <div class="text-justify">In snapshot receiver, each signal capture is digitized and saved as an ORS file. The user has total control over how often and how many milliseconds of IF data to capture. The diagram below is an example of captured IF data. For example, the highlighted IF data file was captured on 25th May, 2017 at 21:48:33 UTC time. Since each millisecond of IF data equals 2 KB (kilobytes), these files contain 20 milliseconds of IF data.</div> <center>http://basebandtech.com/wp-content/uploads/ors-files-IF-data.png</center> <div class="text-justify">Data Processing starts with running the Measurement Engine which converts the IF data to obtain Code Phase and Doppler information for each visible satellite. This process is sometimes called Pre-Processing. The diagram below shows the pre-processed results. Notice the ORS files have now become MSR files and their file size have reduced significantly from 40KB to 62 bytes.<br></div> <center>http://basebandtech.com/wp-content/uploads/msr-files-measurement-data.png</center> <div class="text-justify">Once the MSR file has been generated, the next step is to run the Position Engine to compute a user position.<br><br></div> <div class="text-justify">To illustrate the Data Processing concept, I described processing the IF data files by running the Measurement and the Position Engines in two steps. In practice, a graphical user interface (GUI) would be used to process IF data conveniently. For example, the GUI shown below provides the user a series of processing options such as the name of the input IF data file, how much IF data (in milliseconds) should be processed etc. The processing results include the Latitude/Longitude/Height, Date & Time, number of satellites found and used, Dilution of Precision (DOP) values, and how long the server took to process the IF data file.<br></div> <center>http://basebandtech.com/wp-content/uploads/DataProcessing-GUI.png</center> ## Summary <div class="text-justify">In this mini blog series, we have discussed three key advantages of snapshot receiver:<br></div> 1. Once the satellite signal has been captured, it does not need to be processed right away – designer can offload the parts which consume the most energy to a remote device. 2. When compared with the conventional receiver, the flexibility in designing with the snapshot receiver is unparalleled – designer can easily construct a #UltraLowPowerGPS receiver by mixing-and-matching the Data Capture, Data Buffer, Data Storage and Data Processing modules to optimize energy consumption for their unique hardware platform. 3. To minimize energy further, designer can force the snapshot receiver to remain in a ‘deep sleep’ state most of the time. The receiver will only wake up for a few milliseconds to periodically capture a user’s position, store the captured signal and then go back to a ‘deep sleep’ state to conserve power. <div class="text-justify">Our Internet connected smart-phones has created a constantly ON world that has us conditioned to expect everything to be ON instantly. The penalty for using traditional receiver to satisfy our ‘instant everything’ desire is the significant waste of energy. Hence, traditional receivers are too power-hungry for small electronics using small batteries.<br><br></div> <div class="text-justify">Snapshot receiver technology operates counter-intuitively by forcing the receiver to be always OFF to conserve this precious energy; it uses advanced processing techniques that enable the receiver to be turned ON just for a few milliseconds. For low-power Wearables and IoT applications where position fixes are needed but energy consumption must be kept to a minimum, snapshot receiver is ideal.<br><br></div> <div class="text-justify">Congratulations! You should give yourself a pat on the back because you now know more about Ultra Low Power GPS receiver than 99.9% of the people on this planet! <br><br></div> <div class="text-justify">This marks the end of the “What is Snapshot Positioning” series. My goal for this blog is to be a platform of information, communication and learning as well as being an inspiration for those who are interested in implementing Ultra-Low Power GPS and #Blockchain, my next blog series will be about the Block Chain technology and what GPS has got to do with it. I hope to see you then! Bye for now.<br><br></div> |
| json metadata | {"tags":["technology","gps","wearable","iot","blockchain"],"image":["http://basebandtech.com/wp-content/uploads/iStock_000002065973Small.jpg","http://basebandtech.com/wp-content/uploads/Conceptual-GPS-receiver-components-output-files.png","http://basebandtech.com/wp-content/uploads/ors-files-IF-data.png","http://basebandtech.com/wp-content/uploads/msr-files-measurement-data.png","http://basebandtech.com/wp-content/uploads/DataProcessing-GUI.png"],"links":["https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning","https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module","https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23493818/Trx d89381d0ee50bf9dfc5fbb89192332e8a63cc403 |
View Raw JSON Data
{
"trx_id": "d89381d0ee50bf9dfc5fbb89192332e8a63cc403",
"block": 23493818,
"trx_in_block": 45,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T17:55:24",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "technology",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning-part-4-data-processing-module",
"title": "What is Snapshot Positioning? (Part 4 – Data Processing module)",
"body": "# What is Snapshot Positioning? (Part 4 – Data Processing module)\n\n<div class=\"text-justify\"><br>Welcome back to #BlockchainMyGPS!<br><br></div>\n\n<div class=\"pull-right\">\n<img src=\"http://basebandtech.com/wp-content/uploads/iStock_000002065973Small.jpg\">\n</div>\n<div class=\"text-justify\">In the previous blog posts, I explained one advantage of #SnapshotReceiver which is, that, once the #GPS satellite signal has been captured, it does not need to be processed right away. This means that the parts which consume the most energy can be offloaded to a remote device sometime in the future.</div>\n\n<br>For reference purposes, you can find [Part-I](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning), [Part-II](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module) and [Part-III](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules) here.\n\n<div class=\"text-justify\">In this blog post, I will be discussing how signal processing is performed in a snapshot receiver and what the advantages are.<br></div>\n\n## #Ephemeris and #ExtendedEphemeris\n<div class=\"text-justify\">The problem with older generations of snapshot receiver were the limiting requirements that made them undesirable for real-life use cases; these comprise of a valid Ephemeris, an approximate Time and Position of the receiver.<br><br></div>\n\n<div class=\"text-justify\">Ephemeris describes a satellite’s position over a period of time. Conventional receiver obtains ephemeris by decoding the navigation message broadcast directly by the satellites, this downloading process consumes considerable amount of energy. Since the navigation message is broadcast at a very slow data rate – 50 bits per second, it takes ~30 seconds to download it. To make matters worse, when the receiver moves through poor signal areas such as high rise buildings, the incoming signal could be intermittently blocked and must be downloaded again. <br><br></div> \n\n<div class=\"text-justify\">The GPS in my cellphone doesn’t seem to take 30 seconds to get a position. Why? Most smartphone-based GPS receiver get around this slow and energy-intense process by connecting to the wireless network to download the ephemeris from a server. This is typically referred to as Assisted GPS #AGPS. While this approach works very well for smartphones, the energy to operate a wireless radio often consumes more than it would by downloading the broadcast ephemeris.</div> \n\n<div class=\"text-justify\"><br>An alternative to AGPS is Extended Ephemeris where an algorithm can predict the ephemeris for up to 28 days. A receiver can download the Extended Ephemeris file at a convenient time such as when it is being recharged. A receiver with Extended Ephemeris can operate autonomously without the need of additional ephemeris information, either from the satellite broadcasts or from a communication network.</div> \n\n<div class=\"text-justify\"><br>Some new breed of conventional receivers has adopted a hybrid approach to combine Extended Ephemeris with occasional broadcast ephemeris download. This approach is suitable for applications that the receiver is ON most of the time (e.g. car navigation), the benefits for #Wearables and #IoT applications that prefer to be OFF most of the time is limited.<br></div> \n\n## Approximate Time and Position\n<div class=\"text-justify\">Older snapshot receivers also require a time accurate to sub-milliseconds to 60 seconds and position accurate to ~75km. While the rough time and position could be obtained from #WiFi or #Cell-ID, they offer little value for Wearables and IoT devices unless they are integrated with WiFi/Cell-ID radios. Fortunately, state of the art snapshot receiver has overcome these limitations without additional hardware.</div> \n\n<div class=\"text-justify\"><br>NOTE: If you’re interested in knowing more about why GPS receivers take so long to get a position, you can find it [here].<br></div> \n\n## Data Processing Module\n<div class=\"text-justify\">Throughout the course of this ‘What is Snapshot Positioning?’ series, I have explained the basics of a snapshot receiver and three of its four discrete modules – Data Capture, Data Buffering and Data Storage modules. The last module – Signal Processing is a key differentiator between the state of the art snapshot receiver and the conventional receiver. </div> \n\n<div class=\"text-justify\"><br>Signal processing involves the transformation of digitized IF data into ranging measurements (Code Phase and Doppler) and computing the receiver position using signal processing techniques.<br></div> \n\n<center>http://basebandtech.com/wp-content/uploads/Conceptual-GPS-receiver-components-output-files.png</center>\n\n<div class=\"text-justify\">In snapshot receiver, each signal capture is digitized and saved as an ORS file. The user has total control over how often and how many milliseconds of IF data to capture. The diagram below is an example of captured IF data. For example, the highlighted IF data file was captured on 25th May, 2017 at 21:48:33 UTC time. Since each millisecond of IF data equals 2 KB (kilobytes), these files contain 20 milliseconds of IF data.</div> \n\n<center>http://basebandtech.com/wp-content/uploads/ors-files-IF-data.png</center>\n \n<div class=\"text-justify\">Data Processing starts with running the Measurement Engine which converts the IF data to obtain Code Phase and Doppler information for each visible satellite. This process is sometimes called Pre-Processing. The diagram below shows the pre-processed results. Notice the ORS files have now become MSR files and their file size have reduced significantly from 40KB to 62 bytes.<br></div> \n\n<center>http://basebandtech.com/wp-content/uploads/msr-files-measurement-data.png</center>\n \n<div class=\"text-justify\">Once the MSR file has been generated, the next step is to run the Position Engine to compute a user position.<br><br></div> \n\n<div class=\"text-justify\">To illustrate the Data Processing concept, I described processing the IF data files by running the Measurement and the Position Engines in two steps. In practice, a graphical user interface (GUI) would be used to process IF data conveniently. For example, the GUI shown below provides the user a series of processing options such as the name of the input IF data file, how much IF data (in milliseconds) should be processed etc. The processing results include the Latitude/Longitude/Height, Date & Time, number of satellites found and used, Dilution of Precision (DOP) values, and how long the server took to process the IF data file.<br></div> \n\n<center>http://basebandtech.com/wp-content/uploads/DataProcessing-GUI.png</center>\n\n## Summary\n\n<div class=\"text-justify\">In this mini blog series, we have discussed three key advantages of snapshot receiver:<br></div>\n\n1. Once the satellite signal has been captured, it does not need to be processed right away – designer can offload the parts which consume the most energy to a remote device.\n2. When compared with the conventional receiver, the flexibility in designing with the snapshot receiver is unparalleled – designer can easily construct a #UltraLowPowerGPS receiver by mixing-and-matching the Data Capture, Data Buffer, Data Storage and Data Processing modules to optimize energy consumption for their unique hardware platform.\n3. To minimize energy further, designer can force the snapshot receiver to remain in a ‘deep sleep’ state most of the time. The receiver will only wake up for a few milliseconds to periodically capture a user’s position, store the captured signal and then go back to a ‘deep sleep’ state to conserve power.\n\n<div class=\"text-justify\">Our Internet connected smart-phones has created a constantly ON world that has us conditioned to expect everything to be ON instantly. The penalty for using traditional receiver to satisfy our ‘instant everything’ desire is the significant waste of energy. Hence, traditional receivers are too power-hungry for small electronics using small batteries.<br><br></div> \n\n<div class=\"text-justify\">Snapshot receiver technology operates counter-intuitively by forcing the receiver to be always OFF to conserve this precious energy; it uses advanced processing techniques that enable the receiver to be turned ON just for a few milliseconds. For low-power Wearables and IoT applications where position fixes are needed but energy consumption must be kept to a minimum, snapshot receiver is ideal.<br><br></div> \n\n<div class=\"text-justify\">Congratulations! You should give yourself a pat on the back because you now know more about Ultra Low Power GPS receiver than 99.9% of the people on this planet! <br><br></div> \n\n<div class=\"text-justify\">This marks the end of the “What is Snapshot Positioning” series. My goal for this blog is to be a platform of information, communication and learning as well as being an inspiration for those who are interested in implementing Ultra-Low Power GPS and #Blockchain, my next blog series will be about the Block Chain technology and what GPS has got to do with it. I hope to see you then! Bye for now.<br><br></div>",
"json_metadata": "{\"tags\":[\"technology\",\"gps\",\"wearable\",\"iot\",\"blockchain\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/iStock_000002065973Small.jpg\",\"http://basebandtech.com/wp-content/uploads/Conceptual-GPS-receiver-components-output-files.png\",\"http://basebandtech.com/wp-content/uploads/ors-files-IF-data.png\",\"http://basebandtech.com/wp-content/uploads/msr-files-measurement-data.png\",\"http://basebandtech.com/wp-content/uploads/DataProcessing-GUI.png\"],\"links\":[\"https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning\",\"https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module\",\"https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}fy1000000published a new post: what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules2018/06/09 23:13:33
fy1000000published a new post: what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules
2018/06/09 23:13:33
| parent author | |
| parent permlink | technology |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules |
| title | What is Snapshot Positioning? (Part 3 – Data Buffering and Data Storage Modules) |
| body | @@ -1554,24 +1554,68 @@ %E2%80%93 I -0, I1, Q0 and Q1 +%3Csub%3E0%3C/sub%3E, I%3Csub%3E1%3C/sub%3E, Q%3Csub%3E0%3C/sub%3E and Q%3Csub%3E1%3C/sub%3E and |
| json metadata | {"tags":["technology","gps","wearable","iot","blockchain"],"image":["http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Buffering-Module.png","http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage-Module.png","http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage.png","http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Processing.png"],"links":["https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning","https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23184033/Trx 260ec082453606a675245af763e02ed04e0e345b |
View Raw JSON Data
{
"trx_id": "260ec082453606a675245af763e02ed04e0e345b",
"block": 23184033,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-09T23:13:33",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "technology",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules",
"title": "What is Snapshot Positioning? (Part 3 – Data Buffering and Data Storage Modules)",
"body": "@@ -1554,24 +1554,68 @@\n %E2%80%93 I\n-0, I1, Q0 and Q1\n+%3Csub%3E0%3C/sub%3E, I%3Csub%3E1%3C/sub%3E, Q%3Csub%3E0%3C/sub%3E and Q%3Csub%3E1%3C/sub%3E\n and\n",
"json_metadata": "{\"tags\":[\"technology\",\"gps\",\"wearable\",\"iot\",\"blockchain\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Buffering-Module.png\",\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage-Module.png\",\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage.png\",\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Processing.png\"],\"links\":[\"https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning\",\"https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}fy1000000upvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain2018/06/09 22:42:45
fy1000000upvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain
2018/06/09 22:42:45
| voter | fy1000000 |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23183417/Trx d62461e17fd59b3022a0351df914e0bb0603dcc6 |
View Raw JSON Data
{
"trx_id": "d62461e17fd59b3022a0351df914e0bb0603dcc6",
"block": 23183417,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-09T22:42:45",
"op": [
"vote",
{
"voter": "fy1000000",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"weight": 10000
}
]
}fy1000000upvoted (100.00%) @fy1000000 / why-does-gps-take-so-long-to-get-a-position2018/06/09 22:42:39
fy1000000upvoted (100.00%) @fy1000000 / why-does-gps-take-so-long-to-get-a-position
2018/06/09 22:42:39
| voter | fy1000000 |
| author | fy1000000 |
| permlink | why-does-gps-take-so-long-to-get-a-position |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23183415/Trx 9cbbe290fc9a5519a1beb0422041bf24363ef733 |
View Raw JSON Data
{
"trx_id": "9cbbe290fc9a5519a1beb0422041bf24363ef733",
"block": 23183415,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-09T22:42:39",
"op": [
"vote",
{
"voter": "fy1000000",
"author": "fy1000000",
"permlink": "why-does-gps-take-so-long-to-get-a-position",
"weight": 10000
}
]
}2018/06/09 22:42:30
2018/06/09 22:42:30
| voter | fy1000000 |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23183412/Trx 87158855209258ebddde85c509a50d5233ab773d |
View Raw JSON Data
{
"trx_id": "87158855209258ebddde85c509a50d5233ab773d",
"block": 23183412,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-09T22:42:30",
"op": [
"vote",
{
"voter": "fy1000000",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules",
"weight": 10000
}
]
}fy1000000upvoted (100.00%) @fy1000000 / what-is-snapshot-positioning2018/06/09 22:42:24
fy1000000upvoted (100.00%) @fy1000000 / what-is-snapshot-positioning
2018/06/09 22:42:24
| voter | fy1000000 |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23183410/Trx 34a7a525b3d586dff0b88165e8e8b8942f345abb |
View Raw JSON Data
{
"trx_id": "34a7a525b3d586dff0b88165e8e8b8942f345abb",
"block": 23183410,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-09T22:42:24",
"op": [
"vote",
{
"voter": "fy1000000",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning",
"weight": 10000
}
]
}fy1000000upvoted (100.00%) @fy1000000 / what-is-snapshot-positioning-part-2-data-capture-module2018/06/09 22:42:18
fy1000000upvoted (100.00%) @fy1000000 / what-is-snapshot-positioning-part-2-data-capture-module
2018/06/09 22:42:18
| voter | fy1000000 |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning-part-2-data-capture-module |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23183408/Trx e0f882d92a99680b27704d24a2b72010d7ec4bf1 |
View Raw JSON Data
{
"trx_id": "e0f882d92a99680b27704d24a2b72010d7ec4bf1",
"block": 23183408,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-09T22:42:18",
"op": [
"vote",
{
"voter": "fy1000000",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning-part-2-data-capture-module",
"weight": 10000
}
]
}fy1000000published a new post: what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules2018/06/09 22:37:27
fy1000000published a new post: what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules
2018/06/09 22:37:27
| parent author | |
| parent permlink | technology |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules |
| title | What is Snapshot Positioning? (Part 3 – Data Buffering and Data Storage Modules) |
| body | # What is Snapshot Positioning? (Part 3 – Data Buffering and Data Storage Modules) <div class="text-justify"><br>Welcome back to #BlockchainMyGPS!<br><br></div> <div class="text-justify">In the previous blog posts in this series, I explained #SnapshotReceiver and one of its discrete modules – Data Capture. </div> <br>To jog your memory, you can find [Part-I](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning) and [Part-II](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module) here.<br> <div class="text-justify">One advantage of snapshot receiver is that once the #GPS satellite signal has been captured, it does not need to be processed right away. This means that the parts which consume the most energy can be offloaded to a remote device that has a much greater processing capacity, speed and efficiency. In this blog post, we will be discussing why and how Data Buffering and Data Storage may be required in a design.<br></div> ## Data Buffering Module <center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Buffering-Module.png</center> <div class="text-justify">The MAX2769 #RFIC has a very flexible architecture in which it can be configured to output different IF data formats between 1 MSPS and 16 MSPS (mega-sample per second). For an optimized #UltraLowPowerGPS receiver design, we found out that the best configuration is by using 2-bit I, 2-bit Q at 4.092 MSPS – this means the RFIC will split the IF data into 4 separate data lines – I0, I1, Q0 and Q1 and output them at a fairly high data rate of 4.092 MSPS per data line.<br><br></div> <div class="text-justify">Although I mentioned in my previous blog posts that snapshot receiver requires only a few milliseconds of IF data to obtain a position and the data size is only a few kilobytes per capture, however the speed at which the RFIC outputs the IF data (data rate) could be too high for some low-cost MCUs to read. In this case, a Data Buffering module may be needed to temporarily store the data before sending it to the Data Storage or Data Processing Modules.<br><br></div> <div class="text-justify">There are many ways to implement the interface logic of the Data Buffering module. One simple way is to connect each data line to an 8-bit serial to parallel SIPO shift register chip such as the 74164 series to slow down the incoming 4.092 MSPS data stream to 0.5115 MSPS.<br></div> ## Data Storage Module <center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage-Module.png</center> <div class="text-justify">Similar to the Data Buffering module, depending on how the RFIC interfaces with the MCU – Microcontroller, the Data Storage module is optional.<br></div> <center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage.png</center> <div class="text-justify">For #Wearables and #IoT applications such as fitness watches that must continuously track a user’s position while operating on a small battery, minimizing power consumption is paramount. One strategy is to force the snapshot receiver to remain in a state of deep sleep most of the time. The snapshot receiver will only wake up to periodically capture a user’s position by turning ON the RFIC for a few milliseconds and store the captured signal data to non-volatile memory e.g. flash memory or SD card etc. As soon as the capture is completed, the snapshot receiver will immediately go back to a ‘deep sleep’ state to conserve power.<br><br></div> <div class="text-justify">Another unique advantage of snapshot receiver is that once the captured signal data is stored in non-volatile memory, it can be retrieved for processing at any time in the future which can be done on the device itself, a cloud server or even a computing device near the snapshot receiver. For example, a low power Bluetooth-enabled wristband can be programmed to continuously capture and store the IF data until it is connected to an external power source e.g. while recharging, where the captured data can be conveniently sent to a remote server or to a nearby smartphone for signal processing.<br></div> <center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Processing.png</center> <div class="text-justify">In this blog post, we have discussed why and how the Data Buffering and the Data Storage modules might be necessary for a snapshot receiver. By now, you have probably already noticed that there are rigid requirements for users to connect conventional receivers to their hardware environment. In contrast, state of the art snapshot receiver provides an extremely flexible architecture for users to integrate it to their hardware environment to achieve maximum energy efficiency.<br><br></div> <div class="text-justify">In the next blog post, which hopefully would mark the end of this “What is Snapshot Positioning” mini-series, I will discuss the Signal Processing module in more detail. I hope to see you then!<br></div> |
| json metadata | {"tags":["technology","gps","wearable","iot","blockchain"],"image":["http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Buffering-Module.png","http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage-Module.png","http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage.png","http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Processing.png"],"links":["https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning","https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23183311/Trx fbfec72f15539f5a267663d27890ce7a2428ee79 |
View Raw JSON Data
{
"trx_id": "fbfec72f15539f5a267663d27890ce7a2428ee79",
"block": 23183311,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-09T22:37:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "technology",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning-part-3-data-buffering-and-data-storage-modules",
"title": "What is Snapshot Positioning? (Part 3 – Data Buffering and Data Storage Modules)",
"body": "# What is Snapshot Positioning? (Part 3 – Data Buffering and Data Storage Modules)\n\n<div class=\"text-justify\"><br>Welcome back to #BlockchainMyGPS!<br><br></div>\n\n<div class=\"text-justify\">In the previous blog posts in this series, I explained #SnapshotReceiver and one of its discrete modules – Data Capture. </div>\n\n<br>To jog your memory, you can find [Part-I](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning) and [Part-II](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module) here.<br>\n\n<div class=\"text-justify\">One advantage of snapshot receiver is that once the #GPS satellite signal has been captured, it does not need to be processed right away. This means that the parts which consume the most energy can be offloaded to a remote device that has a much greater processing capacity, speed and efficiency. In this blog post, we will be discussing why and how Data Buffering and Data Storage may be required in a design.<br></div>\n\n## Data Buffering Module\n\n<center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Buffering-Module.png</center>\n\n<div class=\"text-justify\">The MAX2769 #RFIC has a very flexible architecture in which it can be configured to output different IF data formats between 1 MSPS and 16 MSPS (mega-sample per second). For an optimized #UltraLowPowerGPS receiver design, we found out that the best configuration is by using 2-bit I, 2-bit Q at 4.092 MSPS – this means the RFIC will split the IF data into 4 separate data lines – I0, I1, Q0 and Q1 and output them at a fairly high data rate of 4.092 MSPS per data line.<br><br></div>\n\n<div class=\"text-justify\">Although I mentioned in my previous blog posts that snapshot receiver requires only a few milliseconds of IF data to obtain a position and the data size is only a few kilobytes per capture, however the speed at which the RFIC outputs the IF data (data rate) could be too high for some low-cost MCUs to read. In this case, a Data Buffering module may be needed to temporarily store the data before sending it to the Data Storage or Data Processing Modules.<br><br></div> \n\n<div class=\"text-justify\">There are many ways to implement the interface logic of the Data Buffering module. One simple way is to connect each data line to an 8-bit serial to parallel SIPO shift register chip such as the 74164 series to slow down the incoming 4.092 MSPS data stream to 0.5115 MSPS.<br></div> \n\n## Data Storage Module\n\n<center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage-Module.png</center>\n\n<div class=\"text-justify\">Similar to the Data Buffering module, depending on how the RFIC interfaces with the MCU – Microcontroller, the Data Storage module is optional.<br></div> \n\n<center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage.png</center>\n\n<div class=\"text-justify\">For #Wearables and #IoT applications such as fitness watches that must continuously track a user’s position while operating on a small battery, minimizing power consumption is paramount. One strategy is to force the snapshot receiver to remain in a state of deep sleep most of the time. The snapshot receiver will only wake up to periodically capture a user’s position by turning ON the RFIC for a few milliseconds and store the captured signal data to non-volatile memory e.g. flash memory or SD card etc. As soon as the capture is completed, the snapshot receiver will immediately go back to a ‘deep sleep’ state to conserve power.<br><br></div> \n\n<div class=\"text-justify\">Another unique advantage of snapshot receiver is that once the captured signal data is stored in non-volatile memory, it can be retrieved for processing at any time in the future which can be done on the device itself, a cloud server or even a computing device near the snapshot receiver. For example, a low power Bluetooth-enabled wristband can be programmed to continuously capture and store the IF data until it is connected to an external power source e.g. while recharging, where the captured data can be conveniently sent to a remote server or to a nearby smartphone for signal processing.<br></div> \n\n<center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Processing.png</center>\n \n<div class=\"text-justify\">In this blog post, we have discussed why and how the Data Buffering and the Data Storage modules might be necessary for a snapshot receiver. By now, you have probably already noticed that there are rigid requirements for users to connect conventional receivers to their hardware environment. In contrast, state of the art snapshot receiver provides an extremely flexible architecture for users to integrate it to their hardware environment to achieve maximum energy efficiency.<br><br></div> \n\n<div class=\"text-justify\">In the next blog post, which hopefully would mark the end of this “What is Snapshot Positioning” mini-series, I will discuss the Signal Processing module in more detail. I hope to see you then!<br></div>",
"json_metadata": "{\"tags\":[\"technology\",\"gps\",\"wearable\",\"iot\",\"blockchain\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Buffering-Module.png\",\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage-Module.png\",\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Storage.png\",\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Processing.png\"],\"links\":[\"https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning\",\"https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning-part-2-data-capture-module\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}fy1000000published a new post: what-is-snapshot-positioning-part-2-data-capture-module2018/06/08 18:39:18
fy1000000published a new post: what-is-snapshot-positioning-part-2-data-capture-module
2018/06/08 18:39:18
| parent author | |
| parent permlink | technology |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning-part-2-data-capture-module |
| title | What is Snapshot Positioning? (Part 2 – Data Capture module) |
| body | @@ -552,16 +552,36 @@ Receiver +-Data-Capture-Module .png%3C/ce |
| json metadata | {"tags":["technology","gps","wearable","iot","blockchain"],"image":["http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Capture-Module.png","http://basebandtech.com/wp-content/uploads/RF-Front-end.png","http://basebandtech.com/wp-content/uploads/MAX2769-RFIC.png"],"links":["https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23149753/Trx c13da9e368e7398aaeab48f08b78a9a7529f3aba |
View Raw JSON Data
{
"trx_id": "c13da9e368e7398aaeab48f08b78a9a7529f3aba",
"block": 23149753,
"trx_in_block": 41,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T18:39:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "technology",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning-part-2-data-capture-module",
"title": "What is Snapshot Positioning? (Part 2 – Data Capture module)",
"body": "@@ -552,16 +552,36 @@\n Receiver\n+-Data-Capture-Module\n .png%3C/ce\n",
"json_metadata": "{\"tags\":[\"technology\",\"gps\",\"wearable\",\"iot\",\"blockchain\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver-Data-Capture-Module.png\",\"http://basebandtech.com/wp-content/uploads/RF-Front-end.png\",\"http://basebandtech.com/wp-content/uploads/MAX2769-RFIC.png\"],\"links\":[\"https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/06/07 02:09:15
2018/06/07 02:09:15
| voter | thetroublenotes |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning-part-2-data-capture-module |
| weight | 90 (0.90%) |
| Transaction Info | Block #23101176/Trx 727780f24e8cebe9f929fe9f791ec5616fe3d312 |
View Raw JSON Data
{
"trx_id": "727780f24e8cebe9f929fe9f791ec5616fe3d312",
"block": 23101176,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-07T02:09:15",
"op": [
"vote",
{
"voter": "thetroublenotes",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning-part-2-data-capture-module",
"weight": 90
}
]
}fy1000000published a new post: what-is-snapshot-positioning-part-2-data-capture-module2018/06/07 01:42:15
fy1000000published a new post: what-is-snapshot-positioning-part-2-data-capture-module
2018/06/07 01:42:15
| parent author | |
| parent permlink | technology |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning-part-2-data-capture-module |
| title | What is Snapshot Positioning? (Part 2 – Data Capture module) |
| body | # What is Snapshot Positioning? (Part 2 – Data Capture module) <div class="text-justify"><br>Welcome back to #BlockchainMyGPS!<br></div> <br>In the previous blog post, I explained what a #SnapshotReceiver is. If it all seems distant or sketchy, you can review it [here](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning). A typical snapshot receiver consists of four discrete modules: * Data Capture * Data Buffering * Data Storage * Data Processing <br> <center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver.png</center> <div class="text-justify">Conceptually, the Data Capture module is responsible for capturing the #GPS signals transmitted from the satellites and then digitizes it for the Signal Processor to compute a position.<br></div> <br>Essentially, the Data Capture module consists of: * An antenna that captures the analog GPS satellite signals and * A RF (Radio Frequency) Front-end that converts the signals into digital IF data format. <br> <div class="text-justify">Bear in mind that the GPS signals transmitted by the satellite is in the L1 frequency band – 1574.42 MHz. The RF circuitry for a front-end is usually quite complex because it has to convert the high frequency radio signals at the 1.5 GHz level down to a few MHz that is suitable for digital signal processing. In addition, to minimize cost, physical size and power consumption, the RF Front-end is usually implemented in an integrated circuit which is sometimes referred to as an #RFIC – Radio Frequency Integrated Circuit.<br><br></div> A typical RF Front-end consists of the following: * Antenna * SAW (Surface Acoustic Wave) filter * LNA (Low-Noise Amplifier) * TCXO (Temperature Compensated Crystal Oscillator) * Mixer * AGC (Automatic Gain Control) * ADC (Analog to Digital Converter) <center>http://basebandtech.com/wp-content/uploads/RF-Front-end.png</center> <div class="text-justify">While there are many RFIC products that can be purchased off-the-shelf, in principle, Snapshot Receiver can be made compatible with any RFIC. In choosing an RFIC for #UltraLowPowerGPS projects, it should comply with a few technical specifications such as sampling rate, I & Q bit format, physical size and low power consumption, etc. For applications that demand reliability and versatility, the de facto industry standard is the MAX2769 RFIC from Maxim Integrated.<br><br></div> <div class="text-justify">The MAX2769 is a single-conversion, low-IF GNSS receiver that is designed for high performance consumer applications. The MAX2769 is based on Maxim’s advanced low-power SiGe BiCMOS process technology and it incorporates a complete receiver chain including a dual-input LNA and mixer, followed by the image-rejected filter, Programmable Gain Amplifier (PGA), Voltage-Controlled Oscillator (VCO), fractional-N frequency synthesizer, crystal oscillator, and a multibit ADC. The total cascaded noise figure of this receiver is as low as 1.4 dB.<br></div> <center>http://basebandtech.com/wp-content/uploads/MAX2769-RFIC.png</center> <div class="text-justify">For most #Wearables and #IoT applications, the MAX2769 is ideal because it is housed in a compact 5 X 5 mm, 28-pin thin QFN package. For those that are interested in high volume applications, the MAX2769 is also available in die form.<br><br></div> <div class="text-justify">In this blog post, we have discussed the Data Capture module of a snapshot receiver and also, briefly touched upon a few RF terminologies as seen above. In practice, implementing the Data Capture module is actually as simple as wiring up an RFIC. <br><br></div> <div class="text-justify">In the next blog post, I will be discussing the Data Buffering and the Data Storage modules in more detail. I hope to see you then!<br></div> |
| json metadata | {"tags":["technology","gps","wearable","iot","blockchain"],"image":["http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver.png","http://basebandtech.com/wp-content/uploads/RF-Front-end.png","http://basebandtech.com/wp-content/uploads/MAX2769-RFIC.png"],"links":["https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23100636/Trx e6ea9899f8aa596f2f58a514ea24bc200167bd63 |
View Raw JSON Data
{
"trx_id": "e6ea9899f8aa596f2f58a514ea24bc200167bd63",
"block": 23100636,
"trx_in_block": 42,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-07T01:42:15",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "technology",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning-part-2-data-capture-module",
"title": "What is Snapshot Positioning? (Part 2 – Data Capture module)",
"body": "# What is Snapshot Positioning? (Part 2 – Data Capture module)\n\n<div class=\"text-justify\"><br>Welcome back to #BlockchainMyGPS!<br></div>\n\n<br>In the previous blog post, I explained what a #SnapshotReceiver is. If it all seems distant or sketchy, you can review it [here](https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning).\n\nA typical snapshot receiver consists of four discrete modules:\n* Data Capture\n* Data Buffering\n* Data Storage\n* Data Processing\n<br>\n\n<center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver.png</center>\n\n<div class=\"text-justify\">Conceptually, the Data Capture module is responsible for capturing the #GPS signals transmitted from the satellites and then digitizes it for the Signal Processor to compute a position.<br></div>\n\n<br>Essentially, the Data Capture module consists of:\n* An antenna that captures the analog GPS satellite signals and \n* A RF (Radio Frequency) Front-end that converts the signals into digital IF data format. \n<br>\n\n<div class=\"text-justify\">Bear in mind that the GPS signals transmitted by the satellite is in the L1 frequency band – 1574.42 MHz. The RF circuitry for a front-end is usually quite complex because it has to convert the high frequency radio signals at the 1.5 GHz level down to a few MHz that is suitable for digital signal processing. In addition, to minimize cost, physical size and power consumption, the RF Front-end is usually implemented in an integrated circuit which is sometimes referred to as an #RFIC – Radio Frequency Integrated Circuit.<br><br></div> \n\nA typical RF Front-end consists of the following:\n* Antenna\n* SAW (Surface Acoustic Wave) filter\n* LNA (Low-Noise Amplifier)\n* TCXO (Temperature Compensated Crystal Oscillator)\n* Mixer\n* AGC (Automatic Gain Control)\n* ADC (Analog to Digital Converter)\n\n<center>http://basebandtech.com/wp-content/uploads/RF-Front-end.png</center>\n\n<div class=\"text-justify\">While there are many RFIC products that can be purchased off-the-shelf, in principle, Snapshot Receiver can be made compatible with any RFIC. In choosing an RFIC for #UltraLowPowerGPS projects, it should comply with a few technical specifications such as sampling rate, I & Q bit format, physical size and low power consumption, etc. For applications that demand reliability and versatility, the de facto industry standard is the MAX2769 RFIC from Maxim Integrated.<br><br></div> \n\n<div class=\"text-justify\">The MAX2769 is a single-conversion, low-IF GNSS receiver that is designed for high performance consumer applications. The MAX2769 is based on Maxim’s advanced low-power SiGe BiCMOS process technology and it incorporates a complete receiver chain including a dual-input LNA and mixer, followed by the image-rejected filter, Programmable Gain Amplifier (PGA), Voltage-Controlled Oscillator (VCO), fractional-N frequency synthesizer, crystal oscillator, and a multibit ADC. The total cascaded noise figure of this receiver is as low as 1.4 dB.<br></div> \n\n<center>http://basebandtech.com/wp-content/uploads/MAX2769-RFIC.png</center>\n\n<div class=\"text-justify\">For most #Wearables and #IoT applications, the MAX2769 is ideal because it is housed in a compact 5 X 5 mm, 28-pin thin QFN package. For those that are interested in high volume applications, the MAX2769 is also available in die form.<br><br></div> \n \n<div class=\"text-justify\">In this blog post, we have discussed the Data Capture module of a snapshot receiver and also, briefly touched upon a few RF terminologies as seen above. In practice, implementing the Data Capture module is actually as simple as wiring up an RFIC. <br><br></div> \n\n<div class=\"text-justify\">In the next blog post, I will be discussing the Data Buffering and the Data Storage modules in more detail. I hope to see you then!<br></div>",
"json_metadata": "{\"tags\":[\"technology\",\"gps\",\"wearable\",\"iot\",\"blockchain\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver.png\",\"http://basebandtech.com/wp-content/uploads/RF-Front-end.png\",\"http://basebandtech.com/wp-content/uploads/MAX2769-RFIC.png\"],\"links\":[\"https://steemit.com/technology/@fy1000000/what-is-snapshot-positioning\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}fy1000000upvoted (100.00%) @flemingfarm / i-have-given-in-and-accepted-my-new-addiction2018/06/02 23:05:21
fy1000000upvoted (100.00%) @flemingfarm / i-have-given-in-and-accepted-my-new-addiction
2018/06/02 23:05:21
| voter | fy1000000 |
| author | flemingfarm |
| permlink | i-have-given-in-and-accepted-my-new-addiction |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22982327/Trx 07cdc601171a50d3fd03ca2e0e56b65519d479e6 |
View Raw JSON Data
{
"trx_id": "07cdc601171a50d3fd03ca2e0e56b65519d479e6",
"block": 22982327,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-02T23:05:21",
"op": [
"vote",
{
"voter": "fy1000000",
"author": "flemingfarm",
"permlink": "i-have-given-in-and-accepted-my-new-addiction",
"weight": 10000
}
]
}thetroublenotesupvoted (0.70%) @fy1000000 / what-is-snapshot-positioning2018/06/02 23:05:15
thetroublenotesupvoted (0.70%) @fy1000000 / what-is-snapshot-positioning
2018/06/02 23:05:15
| voter | thetroublenotes |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning |
| weight | 70 (0.70%) |
| Transaction Info | Block #22982325/Trx 077c65738d3fa14216afe68c74e7f81e843890c8 |
View Raw JSON Data
{
"trx_id": "077c65738d3fa14216afe68c74e7f81e843890c8",
"block": 22982325,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-02T23:05:15",
"op": [
"vote",
{
"voter": "thetroublenotes",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning",
"weight": 70
}
]
}2018/06/02 23:04:09
2018/06/02 23:04:09
| parent author | patb |
| parent permlink | the-really-hard-thing-about-gps-and-the-iot |
| author | fy1000000 |
| permlink | re-patb-the-really-hard-thing-about-gps-and-the-iot-20180602t230411467z |
| title | |
| body | Hi patb, very nicely done blog - good job! I am now following you. I also invite you to take a look at [#BlockchainMyGPS](https://steemit.com/@fy1000000). I will be covering #SnapshotReceiver & #Blockchain technologies for those who are interested in implementing #Wearables and #IoT applications. Hope to see you soon! |
| json metadata | {"tags":["iot","snapshotreceiver","blockchain","wearables"],"links":["https://steemit.com/@fy1000000"],"app":"steemit/0.1"} |
| Transaction Info | Block #22982303/Trx fa547e26904b7be675b2debdb13021f48c36d294 |
View Raw JSON Data
{
"trx_id": "fa547e26904b7be675b2debdb13021f48c36d294",
"block": 22982303,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-02T23:04:09",
"op": [
"comment",
{
"parent_author": "patb",
"parent_permlink": "the-really-hard-thing-about-gps-and-the-iot",
"author": "fy1000000",
"permlink": "re-patb-the-really-hard-thing-about-gps-and-the-iot-20180602t230411467z",
"title": "",
"body": "Hi patb, very nicely done blog - good job! I am now following you. I also invite you to take a look at [#BlockchainMyGPS](https://steemit.com/@fy1000000). I will be covering #SnapshotReceiver & #Blockchain technologies for those who are interested in implementing #Wearables and #IoT applications. Hope to see you soon!",
"json_metadata": "{\"tags\":[\"iot\",\"snapshotreceiver\",\"blockchain\",\"wearables\"],\"links\":[\"https://steemit.com/@fy1000000\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/06/02 23:03:48
2018/06/02 23:03:48
| parent author | abhishekraj |
| parent permlink | global-nano-gps-chip-market-key-challenges-and-opportunities-2025 |
| author | fy1000000 |
| permlink | re-abhishekraj-global-nano-gps-chip-market-key-challenges-and-opportunities-2025-20180602t230349993z |
| title | |
| body | Hi abhishekraj, very nicely done blog - good job! I am now following you. I also invite you to take a look at [#BlockchainMyGPS](https://steemit.com/@fy1000000). I will be covering #SnapshotReceiver & #Blockchain technologies for those who are interested in implementing #Wearables and #IoT applications. Hope to see you soon! |
| json metadata | {"tags":["nano","snapshotreceiver","blockchain","wearables","iot"],"links":["https://steemit.com/@fy1000000"],"app":"steemit/0.1"} |
| Transaction Info | Block #22982296/Trx b47eccbc4211269a2469493acc6c9da57f657f5b |
View Raw JSON Data
{
"trx_id": "b47eccbc4211269a2469493acc6c9da57f657f5b",
"block": 22982296,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-02T23:03:48",
"op": [
"comment",
{
"parent_author": "abhishekraj",
"parent_permlink": "global-nano-gps-chip-market-key-challenges-and-opportunities-2025",
"author": "fy1000000",
"permlink": "re-abhishekraj-global-nano-gps-chip-market-key-challenges-and-opportunities-2025-20180602t230349993z",
"title": "",
"body": "Hi abhishekraj, very nicely done blog - good job! I am now following you. I also invite you to take a look at [#BlockchainMyGPS](https://steemit.com/@fy1000000). I will be covering #SnapshotReceiver & #Blockchain technologies for those who are interested in implementing #Wearables and #IoT applications. Hope to see you soon!",
"json_metadata": "{\"tags\":[\"nano\",\"snapshotreceiver\",\"blockchain\",\"wearables\",\"iot\"],\"links\":[\"https://steemit.com/@fy1000000\"],\"app\":\"steemit/0.1\"}"
}
]
}fy1000000followed @abhishekraj2018/06/02 23:03:18
fy1000000followed @abhishekraj
2018/06/02 23:03:18
| required auths | [] |
| required posting auths | ["fy1000000"] |
| id | follow |
| json | ["follow",{"follower":"fy1000000","following":"abhishekraj","what":["blog"]}] |
| Transaction Info | Block #22982286/Trx 4c1e18800c75f08fa0c6e8a81e92d1bafc975113 |
View Raw JSON Data
{
"trx_id": "4c1e18800c75f08fa0c6e8a81e92d1bafc975113",
"block": 22982286,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-02T23:03:18",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"fy1000000"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"fy1000000\",\"following\":\"abhishekraj\",\"what\":[\"blog\"]}]"
}
]
}2018/06/02 23:03:12
2018/06/02 23:03:12
| voter | fy1000000 |
| author | abhishekraj |
| permlink | global-nano-gps-chip-market-key-challenges-and-opportunities-2025 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22982284/Trx e57f9a2dbd6b7bdc333b3bc971ade783aaa73569 |
View Raw JSON Data
{
"trx_id": "e57f9a2dbd6b7bdc333b3bc971ade783aaa73569",
"block": 22982284,
"trx_in_block": 64,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-02T23:03:12",
"op": [
"vote",
{
"voter": "fy1000000",
"author": "abhishekraj",
"permlink": "global-nano-gps-chip-market-key-challenges-and-opportunities-2025",
"weight": 10000
}
]
}fy1000000upvoted (100.00%) @patb / the-really-hard-thing-about-gps-and-the-iot2018/06/02 22:52:33
fy1000000upvoted (100.00%) @patb / the-really-hard-thing-about-gps-and-the-iot
2018/06/02 22:52:33
| voter | fy1000000 |
| author | patb |
| permlink | the-really-hard-thing-about-gps-and-the-iot |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22982072/Trx 16fc95b19c51b928493831e2de7c87464aca4ef9 |
View Raw JSON Data
{
"trx_id": "16fc95b19c51b928493831e2de7c87464aca4ef9",
"block": 22982072,
"trx_in_block": 104,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-02T22:52:33",
"op": [
"vote",
{
"voter": "fy1000000",
"author": "patb",
"permlink": "the-really-hard-thing-about-gps-and-the-iot",
"weight": 10000
}
]
}2018/06/02 22:52:24
2018/06/02 22:52:24
| required auths | [] |
| required posting auths | ["fy1000000"] |
| id | follow |
| json | ["follow",{"follower":"fy1000000","following":"patb","what":["blog"]}] |
| Transaction Info | Block #22982069/Trx 7d8812f86964e24728038778735552e346f8d4a3 |
View Raw JSON Data
{
"trx_id": "7d8812f86964e24728038778735552e346f8d4a3",
"block": 22982069,
"trx_in_block": 36,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-02T22:52:24",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"fy1000000"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"fy1000000\",\"following\":\"patb\",\"what\":[\"blog\"]}]"
}
]
}fy1000000published a new post: what-is-snapshot-positioning2018/06/02 22:41:15
fy1000000published a new post: what-is-snapshot-positioning
2018/06/02 22:41:15
| parent author | |
| parent permlink | technology |
| author | fy1000000 |
| permlink | what-is-snapshot-positioning |
| title | What is Snapshot Positioning? |
| body | # What is Snapshot Positioning? <div class="text-justify"><br>Welcome back to #BlockchainMyGPS!<br></div> <br>If you don’t already know why it takes so long for #GPS to get a position or the difference between #Ephemeris & #ExtendedEphemeris, you should read this blog [here](https://steemit.com/gps/@fy1000000/why-does-gps-take-so-long-to-get-a-position). <div class="pull-right"> <img src="http://basebandtech.com/wp-content/uploads/iStock_000006486432Medium.jpg"> </div> <div class="text-justify">Most people who have experience in designing with GPS know that conventional GPS receivers can take up to a minute before it can output its first position and this is one of the reasons why it consumes so much power. In the next few blogs, I will discuss a different kind of receiver using “Snapshot Positioning” techniques to compute a position that only requires the receiver to be turned ON for a few milliseconds. While older Snapshot Positioning techniques required upwards of hundreds of milliseconds to compute a position, new state of the art #SnapshotReceiver requires only a few to tens of milliseconds to compute a position.</div> ## What is the advantage of snapshot receiver? <div class="text-justify">The most apparent advantage of snapshot receiver is the very short time the receiver takes to output its first position, this is sometime known as the Time-To-First-Fix #TTFF. Another less apparent advantage of a snapshot receiver is its ability to compute a position even when operate in poor conditions where satellite signals could be blocked intermittently, this happen when the receiver is moving through high-rise buildings in downtown areas. The reason for this is because snapshot receiver bypasses the downloading of ephemeris broadcast from the GPS satellites that determines where they are in space. It should be obvious by now that because the TTFF is greatly reduced, snapshot receiver consumes significantly less energy because the electronic components only needs to be turned ON for milliseconds comparing to tens of seconds that is required by conventional receivers.</div> ## What are the differences between the older and state of the art generations of snapshot receiver? <div class="text-justify">Older generations of snapshot receiver have some limiting requirements that made them undesirable for real life use cases. For example:<br></div> 1. Ephemeris was only valid from a few hours to a few days – this mean the receiver would need to frequently download the latest Ephemeris from a remote server which is not always convenient or even possible for some #Wearables and Internet of Things #IoT applications. 2. An approximate initial position accurate to a few kilometers was required to compute a position – this means the receiver would need to know a rough starting position which would require external inputs such as WiFi or Cellular based positioning that increases the overall complexity, energy consumption and cost of material. 3. An approximate initial time accurate to a millisecond or better was required to compute a position – this means the receiver would need to be supplied with an external clock source that is expensive to implement. <div class="text-justify">In contrast, new generation of snapshot receiver combines several innovative and patented techniques to eliminate the older requirements and operational constraints. For example, using extended ephemeris technology, snapshot receiver can now operate autonomously for up to 28 days. Furthermore, by augmenting patented and proprietary techniques, initial position and initial time are no longer a requirement.<br></div> ## What are the differences between the conventional receivers and snapshot receiver? <div class="text-justify">Conceptually, a GPS receiver can be divided into 3 logical blocks:<br></div> 1. Signal Capture Engine: Converts the satellite signals from analog to digital format (“IF data”). 2. Measurement Generation Engine: Using the IF data to acquires satellites that are detectable and output their Code Phase and Doppler information. 3. Position Estimation Engine: Using the Code Phase and Doppler information to compute a position. <center>http://basebandtech.com/wp-content/uploads/Conceptual-GPS-receiver-components.png</center> <div class="text-justify">While most conventional receivers can be purchased conveniently as silicon chips, its system architecture lacks the flexibility for the user to mix-and-match these 3 logic blocks to suit their use cases. State of art snapshot receiver deliberately provide a system architectural to encourage users to freely mix-and-match the 3 logic blocks to provide users with maximum flexibility to optimize energy consumption that suits their unique application.<br></div> ## What are the typical use cases for snapshot receiver? <div class="text-justify">Snapshot receiver is ideally suited for wearables and IoT applications where position fixes are needed but energy consumption must be kept to a minimum.<br><br>In addition to being able to compute a position on device like a conventional receiver, snapshot receiver can also be configured to only capture/store the satellite signal and delay computing the position until the captured signal is offloaded to a remote server for signal processing sometime in the future.<br><br>Depending on the operating environment, new generation snapshot receiver requires as little as 2ms or 4 KB (kilobytes) per signal capture, so for a 1 GB (gigabyte) SDCard memory, it can store enough signal data for over 250,000 position fixes. It is with this capability, designing an #UltraLowPowerGPS receiver should now be easy to achieved. <br></div> ## What is a snapshot receiver made of? <div class="text-justify">The diagram below shows a high-level overview of a typical snapshot receiver. A typical snapshot receiver consists of four discrete modules. A hardware designer may choose to implement some of these modules on a single device and some in separate devices or even eliminate some modules altogether, the possibility is limited only by the designer’s imagination.<br></div> <center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver.png</center> <div class="text-justify">In this blog, we have discussed the basics of snapshot receiver. I hope you have agreed that, when compared with conventional receiver, the flexibility in designing with snapshot receiver is unparalleled and snapshot receiver is ideal for implementing ultra low power GPS products. I will discuss in more detail about each modules in detail in the next few blogs. I hope to see you then!<br></div> <div class="text-justify"><br></div> |
| json metadata | {"tags":["technology","gps","wearable","iot","blockchain"],"image":["http://basebandtech.com/wp-content/uploads/iStock_000006486432Medium.jpg","http://basebandtech.com/wp-content/uploads/Conceptual-GPS-receiver-components.png","http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver.png"],"links":["https://steemit.com/gps/@fy1000000/why-does-gps-take-so-long-to-get-a-position"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22981846/Trx 38014573167556342bcbd3982977c2737ef66706 |
View Raw JSON Data
{
"trx_id": "38014573167556342bcbd3982977c2737ef66706",
"block": 22981846,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-02T22:41:15",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "technology",
"author": "fy1000000",
"permlink": "what-is-snapshot-positioning",
"title": "What is Snapshot Positioning?",
"body": "# What is Snapshot Positioning?\n\n<div class=\"text-justify\"><br>Welcome back to #BlockchainMyGPS!<br></div>\n\n<br>If you don’t already know why it takes so long for #GPS to get a position or the difference between #Ephemeris & #ExtendedEphemeris, you should read this blog [here](https://steemit.com/gps/@fy1000000/why-does-gps-take-so-long-to-get-a-position).\n\n<div class=\"pull-right\">\n<img src=\"http://basebandtech.com/wp-content/uploads/iStock_000006486432Medium.jpg\">\n</div>\n<div class=\"text-justify\">Most people who have experience in designing with GPS know that conventional GPS receivers can take up to a minute before it can output its first position and this is one of the reasons why it consumes so much power. In the next few blogs, I will discuss a different kind of receiver using “Snapshot Positioning” techniques to compute a position that only requires the receiver to be turned ON for a few milliseconds. While older Snapshot Positioning techniques required upwards of hundreds of milliseconds to compute a position, new state of the art #SnapshotReceiver requires only a few to tens of milliseconds to compute a position.</div>\n\n\n## What is the advantage of snapshot receiver?\n<div class=\"text-justify\">The most apparent advantage of snapshot receiver is the very short time the receiver takes to output its first position, this is sometime known as the Time-To-First-Fix #TTFF. Another less apparent advantage of a snapshot receiver is its ability to compute a position even when operate in poor conditions where satellite signals could be blocked intermittently, this happen when the receiver is moving through high-rise buildings in downtown areas. The reason for this is because snapshot receiver bypasses the downloading of ephemeris broadcast from the GPS satellites that determines where they are in space. It should be obvious by now that because the TTFF is greatly reduced, snapshot receiver consumes significantly less energy because the electronic components only needs to be turned ON for milliseconds comparing to tens of seconds that is required by conventional receivers.</div>\n\n\n## What are the differences between the older and state of the art generations of snapshot receiver?\n<div class=\"text-justify\">Older generations of snapshot receiver have some limiting requirements that made them undesirable for real life use cases. For example:<br></div>\n\n1. Ephemeris was only valid from a few hours to a few days – this mean the receiver would need to frequently download the latest Ephemeris from a remote server which is not always convenient or even possible for some #Wearables and Internet of Things #IoT applications.\n2. An approximate initial position accurate to a few kilometers was required to compute a position – this means the receiver would need to know a rough starting position which would require external inputs such as WiFi or Cellular based positioning that increases the overall complexity, energy consumption and cost of material.\n3. An approximate initial time accurate to a millisecond or better was required to compute a position – this means the receiver would need to be supplied with an external clock source that is expensive to implement.\n\n<div class=\"text-justify\">In contrast, new generation of snapshot receiver combines several innovative and patented techniques to eliminate the older requirements and operational constraints. For example, using extended ephemeris technology, snapshot receiver can now operate autonomously for up to 28 days. Furthermore, by augmenting patented and proprietary techniques, initial position and initial time are no longer a requirement.<br></div>\n\n\n## What are the differences between the conventional receivers and snapshot receiver?\n<div class=\"text-justify\">Conceptually, a GPS receiver can be divided into 3 logical blocks:<br></div>\n\n1. Signal Capture Engine: Converts the satellite signals from analog to digital format (“IF data”).\n2. Measurement Generation Engine: Using the IF data to acquires satellites that are detectable and output their Code Phase and Doppler information.\n3. Position Estimation Engine: Using the Code Phase and Doppler information to compute a position.\n\n<center>http://basebandtech.com/wp-content/uploads/Conceptual-GPS-receiver-components.png</center>\n\n<div class=\"text-justify\">While most conventional receivers can be purchased conveniently as silicon chips, its system architecture lacks the flexibility for the user to mix-and-match these 3 logic blocks to suit their use cases. State of art snapshot receiver deliberately provide a system architectural to encourage users to freely mix-and-match the 3 logic blocks to provide users with maximum flexibility to optimize energy consumption that suits their unique application.<br></div> \n\n\n## What are the typical use cases for snapshot receiver?\n<div class=\"text-justify\">Snapshot receiver is ideally suited for wearables and IoT applications where position fixes are needed but energy consumption must be kept to a minimum.<br><br>In addition to being able to compute a position on device like a conventional receiver, snapshot receiver can also be configured to only capture/store the satellite signal and delay computing the position until the captured signal is offloaded to a remote server for signal processing sometime in the future.<br><br>Depending on the operating environment, new generation snapshot receiver requires as little as 2ms or 4 KB (kilobytes) per signal capture, so for a 1 GB (gigabyte) SDCard memory, it can store enough signal data for over 250,000 position fixes. It is with this capability, designing an #UltraLowPowerGPS receiver should now be easy to achieved.\n<br></div> \n\n\n## What is a snapshot receiver made of?\n<div class=\"text-justify\">The diagram below shows a high-level overview of a typical snapshot receiver. A typical snapshot receiver consists of four discrete modules. A hardware designer may choose to implement some of these modules on a single device and some in separate devices or even eliminate some modules altogether, the possibility is limited only by the designer’s imagination.<br></div> \n\n<center>http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver.png</center>\n\n<div class=\"text-justify\">In this blog, we have discussed the basics of snapshot receiver. I hope you have agreed that, when compared with conventional receiver, the flexibility in designing with snapshot receiver is unparalleled and snapshot receiver is ideal for implementing ultra low power GPS products. I will discuss in more detail about each modules in detail in the next few blogs. I hope to see you then!<br></div> \n \n<div class=\"text-justify\"><br></div>",
"json_metadata": "{\"tags\":[\"technology\",\"gps\",\"wearable\",\"iot\",\"blockchain\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/iStock_000006486432Medium.jpg\",\"http://basebandtech.com/wp-content/uploads/Conceptual-GPS-receiver-components.png\",\"http://basebandtech.com/wp-content/uploads/Conceptual-Snapshot-Receiver.png\"],\"links\":[\"https://steemit.com/gps/@fy1000000/why-does-gps-take-so-long-to-get-a-position\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}fy1000000published a new post: the-starting-point-gps-my-discovery-of-steemit-and-block-chain2018/05/23 20:53:51
fy1000000published a new post: the-starting-point-gps-my-discovery-of-steemit-and-block-chain
2018/05/23 20:53:51
| parent author | |
| parent permlink | introduceyourself |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| title | The Starting Point – GPS, my discovery of Steemit and Block Chain. |
| body | # The Starting Point – GPS, my discovery of Steemit and Block Chain. <div class="pull-right"> <br> <img src="http://basebandtech.com/wp-content/uploads/2014/05/iStock_000006503946Large-250x333.png"> </div> <div class="text-justify"><br>The fact that you’re reading this #introduceyourself post on Steemit tells me that you must be quite tech-savvy and chances are that you also own one or more GPS-enabled devices. Have you ever thought about why you can’t leave the #GPS on your mobile ON all day long? Have you ever thought about why there aren’t many #GPS equipped watches in the market? Have you ever thought about why it’s so difficult to use GPS to track tiny objects like bees and birds? Some of you probably know the answer already – #GPS receivers are too power-hungry for small electronics using only small batteries. If your work, your research or your hobby demands an ultra low-power GPS #ultralowpowergps solution, you’re definitely at the right place.</div> <div class="text-justify"><br>Before I say too much about #GPS, I would like to let you know how I got involved with Steemit. It all began when I started researching on how #blockchain, #cryptocurrency, #mining and decentralized application #dapp work. I noticed that a lot of the people I follow on YouTube such as @louisthomas, @theawakenment, @Boxmining, @benperrin117 and @jerrybanfield have, for one reason or the other, created their own Steemit channels. What intrigued me the most was not only that Dan Larimer, @dantheman, singlehandedly created the $700B+ Steem Economy that attracted so many of these YouTube superstars, but also the fact that Steemit is powered entirely on a block chain. This made me realize that block chain technology is something that I can no longer ignore.</div> <div class="text-justify"><br>Let me #introducemyself, my name is Francis Yuen, I have been working in the #GPS industry for over 25 years. I have spoken at numerous industry forums and co-invented a patented technique to make #instantpositionforanythingthatmoves possible. I obtained my Bachelor and Master degrees in Microelectronics in the UK and an MBA in Canada. You can find me at http://www.linkedin.com/in/basebandtechnologies.</div> <div class="text-justify"><br>Prior to founding my own company, I was fortunate enough to have worked for two large #GPS companies in a variety of leadership positions as well as consulting in sales and marketing, and technology development areas. While these companies specialize in high precision and high accuracy #GPS solutions, my current focus is mainly on #ultralowpowergps solutions that can last for months or years using only coin cell batteries.</div> <div class="pull-left"> <br> <img src="http://basebandtech.com/wp-content/uploads/The-Starting-Point.jpg"> </div> <div class="text-justify"><br>My research on block chain technology has led me to understand that it is now so mainstream, even Wall Street and World Governments can no longer stand in denial of its power and legitimacy. With my experience in #GPS, it is my hope to explore with you these two fundamental technologies in my “Block chain my GPS” #blockchainmygps blog. Here, we’ll be covering topics such as tips and tricks of #ultralowpowergps solutions, links to smart ideas and the latest news on the latest ideas. From time to time, we’ll be inviting guests to share their insights. Hopefully, we will share broader and wider perspectives through our posts over time. Our goal for this blog is to be a platform of information, communication and learning as well as being an inspiration for those who are interested in implementing #ultralowpowergps and #blockchain. While some #GPS and #blockchain concepts are not always easy to understand, I will endeavour to limit each blog to take a fifteen-minute read or less. Why? Because chances are that you don’t need to know every little detail and the math to understand the important things you need to know. If I can’t explain something in 15 minutes or less, then, I should probably go back to study the basics myself!</div> <div class="text-justify"><br>If there are topics or areas of interest that you would like discussed or if you’re interested in sharing your view with the world, you are most welcome and encouraged to let me know.</div> <div class="text-justify"><br>I look forward to sharing this journey with you. Enjoy!</div> <div class="text-justify"><br></div> |
| json metadata | {"tags":["introduceyourself","blockchain","cryptocurrency","mining","technology"],"users":["louisthomas","theawakenment","boxmining","benperrin117","jerrybanfield","dantheman"],"image":["http://basebandtech.com/wp-content/uploads/2014/05/iStock_000006503946Large-250x333.png","http://basebandtech.com/wp-content/uploads/The-Starting-Point.jpg"],"links":["http://www.linkedin.com/in/basebandtechnologies"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22692130/Trx 77b80e1a8202a6524654da0bfc54972251b221b3 |
View Raw JSON Data
{
"trx_id": "77b80e1a8202a6524654da0bfc54972251b221b3",
"block": 22692130,
"trx_in_block": 125,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T20:53:51",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "introduceyourself",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"title": "The Starting Point – GPS, my discovery of Steemit and Block Chain.",
"body": "# The Starting Point – GPS, my discovery of Steemit and Block Chain.\n\n<div class=\"pull-right\">\n<br>\n<img src=\"http://basebandtech.com/wp-content/uploads/2014/05/iStock_000006503946Large-250x333.png\">\n</div>\n<div class=\"text-justify\"><br>The fact that you’re reading this #introduceyourself post on Steemit tells me that you must be quite tech-savvy and chances are that you also own one or more GPS-enabled devices. Have you ever thought about why you can’t leave the #GPS on your mobile ON all day long? Have you ever thought about why there aren’t many #GPS equipped watches in the market? Have you ever thought about why it’s so difficult to use GPS to track tiny objects like bees and birds? Some of you probably know the answer already – #GPS receivers are too power-hungry for small electronics using only small batteries. If your work, your research or your hobby demands an ultra low-power GPS #ultralowpowergps solution, you’re definitely at the right place.</div>\n\n<div class=\"text-justify\"><br>Before I say too much about #GPS, I would like to let you know how I got involved with Steemit. It all began when I started researching on how #blockchain, #cryptocurrency, #mining and decentralized application #dapp work. I noticed that a lot of the people I follow on YouTube such as @louisthomas, @theawakenment, @Boxmining, @benperrin117 and @jerrybanfield have, for one reason or the other, created their own Steemit channels. What intrigued me the most was not only that Dan Larimer, @dantheman, singlehandedly created the $700B+ Steem Economy that attracted so many of these YouTube superstars, but also the fact that Steemit is powered entirely on a block chain. This made me realize that block chain technology is something that I can no longer ignore.</div>\n\n<div class=\"text-justify\"><br>Let me #introducemyself, my name is Francis Yuen, I have been working in the #GPS industry for over 25 years. I have spoken at numerous industry forums and co-invented a patented technique to make #instantpositionforanythingthatmoves possible. I obtained my Bachelor and Master degrees in Microelectronics in the UK and an MBA in Canada. You can find me at http://www.linkedin.com/in/basebandtechnologies.</div>\n\n<div class=\"text-justify\"><br>Prior to founding my own company, I was fortunate enough to have worked for two large #GPS companies in a variety of leadership positions as well as consulting in sales and marketing, and technology development areas. While these companies specialize in high precision and high accuracy #GPS solutions, my current focus is mainly on #ultralowpowergps solutions that can last for months or years using only coin cell batteries.</div>\n\n<div class=\"pull-left\">\n<br>\n<img src=\"http://basebandtech.com/wp-content/uploads/The-Starting-Point.jpg\">\n</div>\n<div class=\"text-justify\"><br>My research on block chain technology has led me to understand that it is now so mainstream, even Wall Street and World Governments can no longer stand in denial of its power and legitimacy. With my experience in #GPS, it is my hope to explore with you these two fundamental technologies in my “Block chain my GPS” #blockchainmygps blog. Here, we’ll be covering topics such as tips and tricks of #ultralowpowergps solutions, links to smart ideas and the latest news on the latest ideas. From time to time, we’ll be inviting guests to share their insights. Hopefully, we will share broader and wider perspectives through our posts over time. Our goal for this blog is to be a platform of information, communication and learning as well as being an inspiration for those who are interested in implementing #ultralowpowergps and #blockchain. While some #GPS and #blockchain concepts are not always easy to understand, I will endeavour to limit each blog to take a fifteen-minute read or less. Why? Because chances are that you don’t need to know every little detail and the math to understand the important things you need to know. If I can’t explain something in 15 minutes or less, then, I should probably go back to study the basics myself!</div>\n\n<div class=\"text-justify\"><br>If there are topics or areas of interest that you would like discussed or if you’re interested in sharing your view with the world, you are most welcome and encouraged to let me know.</div>\n\n<div class=\"text-justify\"><br>I look forward to sharing this journey with you. Enjoy!</div>\n\n<div class=\"text-justify\"><br></div>",
"json_metadata": "{\"tags\":[\"introduceyourself\",\"blockchain\",\"cryptocurrency\",\"mining\",\"technology\"],\"users\":[\"louisthomas\",\"theawakenment\",\"boxmining\",\"benperrin117\",\"jerrybanfield\",\"dantheman\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/2014/05/iStock_000006503946Large-250x333.png\",\"http://basebandtech.com/wp-content/uploads/The-Starting-Point.jpg\"],\"links\":[\"http://www.linkedin.com/in/basebandtechnologies\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}fy1000000published a new post: why-does-gps-take-so-long-to-get-a-position2018/05/23 20:53:21
fy1000000published a new post: why-does-gps-take-so-long-to-get-a-position
2018/05/23 20:53:21
| parent author | |
| parent permlink | gps |
| author | fy1000000 |
| permlink | why-does-gps-take-so-long-to-get-a-position |
| title | Why does #gps take so long to get a position? |
| body | # Why does #gps take so long to get a position? <div class="pull-right"> <br> <img src="http://basebandtech.com/wp-content/uploads/iStock_000000488421Small.jpg"> </div> <div class="text-justify"><br>Welcome back to #blockchainmygps!<br><br>One of the more prominent FAQs I hear is “Why does my #gps take so long to get a position”? <br><br>Anyone who has used a #gps receiver knows that when it’s turned on, it could take from 30 to 60 seconds to calculate a position. In this “instant everything” world of ours, who has the patience to wait that long? In this blog post, I will be explaining the reasons why and what can be done about it.</div> ## What is an Ephemeris? <div class="text-justify">In order for a #gps receiver to calculate a position, it needs to know exactly where the satellites are in space. A #gps receiver knows exactly where the satellites are by downloading a fairly complicated message broadcast from each satellite in view. Each of these messages contain something called an #ephemeris which is a fancy way of saying “I am satellite A, here is where I am at time X”. Unfortunately, these messages are broadcast at a very slow rate of 50 bps (bit per second), this translates to about 30 seconds or more for the #gps receiver to receive these signals.</div> <div class="text-justify"><br>To make it worse, for a #gps receiver to calculate a position, it needs #ephemeris data from 4 different satellites. Hence, depending on the environment, the total time to receive all 4 #ephemeris can take much longer than 30 seconds, if at all.</div> ## What is an Extended Ephemeris?? <div class="text-justify">Since downloading broadcast #ephemeris takes so long, is there a way to get around it? Luckily, the answer is “Yes”.</div> <div class="text-justify"><br>#extendedephemeris technology is a way of predicting the location of the satellites for the near future, hence, the word “extended”. By comparison, broadcast #ephemeris is typically valid for 2 to 4 hours, whereas the state-of-the-art #extendedephemeris technology can be used for up to 28 days. By knowing the exact location of the satellites for the next 28 days, a #gps receiver can totally skip downloading the broadcast #ephemeris and progress directly to calculating the position as soon as the receiver is turned on. The net result of using #extendedephemeris is that instead of taking 30 to 60 seconds to get a position, a typical receiver will now take 1 to 2 seconds to get the job done.</div> <div class="text-justify"><br>Now you know why #gps takes so long to get a position and what #ephemeris / #extendedephemeris are, my next blog post will talk about how #ultralowpowergps receiver technology can get around these problems.</div> <div class="text-justify"><br></div> |
| json metadata | {"tags":["technology","gps","ephemeris","extendedephemeris","ultralowpowergps"],"image":["http://basebandtech.com/wp-content/uploads/iStock_000000488421Small.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22692120/Trx d606c095af88436039325cec5db1d9689616652b |
View Raw JSON Data
{
"trx_id": "d606c095af88436039325cec5db1d9689616652b",
"block": 22692120,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T20:53:21",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "gps",
"author": "fy1000000",
"permlink": "why-does-gps-take-so-long-to-get-a-position",
"title": "Why does #gps take so long to get a position?",
"body": "# Why does #gps take so long to get a position?\n\n<div class=\"pull-right\">\n<br>\n<img src=\"http://basebandtech.com/wp-content/uploads/iStock_000000488421Small.jpg\">\n</div>\n<div class=\"text-justify\"><br>Welcome back to #blockchainmygps!<br><br>One of the more prominent FAQs I hear is “Why does my #gps take so long to get a position”? <br><br>Anyone who has used a #gps receiver knows that when it’s turned on, it could take from 30 to 60 seconds to calculate a position. In this “instant everything” world of ours, who has the patience to wait that long? In this blog post, I will be explaining the reasons why and what can be done about it.</div>\n\n## What is an Ephemeris?\n\n<div class=\"text-justify\">In order for a #gps receiver to calculate a position, it needs to know exactly where the satellites are in space. A #gps receiver knows exactly where the satellites are by downloading a fairly complicated message broadcast from each satellite in view. Each of these messages contain something called an #ephemeris which is a fancy way of saying “I am satellite A, here is where I am at time X”. Unfortunately, these messages are broadcast at a very slow rate of 50 bps (bit per second), this translates to about 30 seconds or more for the #gps receiver to receive these signals.</div>\n\n<div class=\"text-justify\"><br>To make it worse, for a #gps receiver to calculate a position, it needs #ephemeris data from 4 different satellites. Hence, depending on the environment, the total time to receive all 4 #ephemeris can take much longer than 30 seconds, if at all.</div>\n\n## What is an Extended Ephemeris??\n\n<div class=\"text-justify\">Since downloading broadcast #ephemeris takes so long, is there a way to get around it? Luckily, the answer is “Yes”.</div>\n\n<div class=\"text-justify\"><br>#extendedephemeris technology is a way of predicting the location of the satellites for the near future, hence, the word “extended”. By comparison, broadcast #ephemeris is typically valid for 2 to 4 hours, whereas the state-of-the-art #extendedephemeris technology can be used for up to 28 days. By knowing the exact location of the satellites for the next 28 days, a #gps receiver can totally skip downloading the broadcast #ephemeris and progress directly to calculating the position as soon as the receiver is turned on. The net result of using #extendedephemeris is that instead of taking 30 to 60 seconds to get a position, a typical receiver will now take 1 to 2 seconds to get the job done.</div>\n\n<div class=\"text-justify\"><br>Now you know why #gps takes so long to get a position and what #ephemeris / #extendedephemeris are, my next blog post will talk about how #ultralowpowergps receiver technology can get around these problems.</div>\n\n<div class=\"text-justify\"><br></div>",
"json_metadata": "{\"tags\":[\"technology\",\"gps\",\"ephemeris\",\"extendedephemeris\",\"ultralowpowergps\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/iStock_000000488421Small.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/05/22 04:55:33
2018/05/22 04:55:33
| parent author | cheetah |
| parent permlink | cheetah-re-fy1000000why-does-gps-take-so-long-to-get-a-position |
| author | fy1000000 |
| permlink | re-cheetah-cheetah-re-fy1000000why-does-gps-take-so-long-to-get-a-position-20180522t045534325z |
| title | |
| body | Hi cheetah, you are an amazing bot! Although you are not quite my kind, I am still very thankful that you reached out to me. :-) |
| json metadata | {"tags":["gps"],"app":"steemit/0.1"} |
| Transaction Info | Block #22644188/Trx 3115abc1728a15b2128bed10bdd7030d8dab6d07 |
View Raw JSON Data
{
"trx_id": "3115abc1728a15b2128bed10bdd7030d8dab6d07",
"block": 22644188,
"trx_in_block": 51,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-22T04:55:33",
"op": [
"comment",
{
"parent_author": "cheetah",
"parent_permlink": "cheetah-re-fy1000000why-does-gps-take-so-long-to-get-a-position",
"author": "fy1000000",
"permlink": "re-cheetah-cheetah-re-fy1000000why-does-gps-take-so-long-to-get-a-position-20180522t045534325z",
"title": "",
"body": "Hi cheetah, you are an amazing bot! Although you are not quite my kind, I am still very thankful that you reached out to me. :-)",
"json_metadata": "{\"tags\":[\"gps\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/22 04:52:42
2018/05/22 04:52:42
| parent author | fy1000000 |
| parent permlink | why-does-gps-take-so-long-to-get-a-position |
| author | cheetah |
| permlink | cheetah-re-fy1000000why-does-gps-take-so-long-to-get-a-position |
| title | |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: http://basebandtech.com/blog/why-does-gps-take-so-long-to-get-a-position-and-how-extended-ephemeris-can-help/ |
| json metadata | |
| Transaction Info | Block #22644131/Trx d2a8a2641dc3c80ce13603eb7012cc90b32b94f9 |
View Raw JSON Data
{
"trx_id": "d2a8a2641dc3c80ce13603eb7012cc90b32b94f9",
"block": 22644131,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-22T04:52:42",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "why-does-gps-take-so-long-to-get-a-position",
"author": "cheetah",
"permlink": "cheetah-re-fy1000000why-does-gps-take-so-long-to-get-a-position",
"title": "",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttp://basebandtech.com/blog/why-does-gps-take-so-long-to-get-a-position-and-how-extended-ephemeris-can-help/",
"json_metadata": ""
}
]
}cheetahupvoted (0.08%) @fy1000000 / why-does-gps-take-so-long-to-get-a-position2018/05/22 04:52:36
cheetahupvoted (0.08%) @fy1000000 / why-does-gps-take-so-long-to-get-a-position
2018/05/22 04:52:36
| voter | cheetah |
| author | fy1000000 |
| permlink | why-does-gps-take-so-long-to-get-a-position |
| weight | 8 (0.08%) |
| Transaction Info | Block #22644129/Trx 03456592711b08771573fc397b4073da2df26049 |
View Raw JSON Data
{
"trx_id": "03456592711b08771573fc397b4073da2df26049",
"block": 22644129,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-22T04:52:36",
"op": [
"vote",
{
"voter": "cheetah",
"author": "fy1000000",
"permlink": "why-does-gps-take-so-long-to-get-a-position",
"weight": 8
}
]
}fy1000000published a new post: why-does-gps-take-so-long-to-get-a-position2018/05/22 04:52:27
fy1000000published a new post: why-does-gps-take-so-long-to-get-a-position
2018/05/22 04:52:27
| parent author | |
| parent permlink | gps |
| author | fy1000000 |
| permlink | why-does-gps-take-so-long-to-get-a-position |
| title | Why does #gps take so long to get a position? |
| body | # Why does #gps take so long to get a position? <div class="pull-right"> <br> <img src="http://basebandtech.com/wp-content/uploads/iStock_000000488421Small.jpg"> </div> <div class="text-justify"><br>Welcome back to #blockchainmygps!<br><br>One of the more prominent FAQs I hear is “Why does my #gps take so long to get a position”? <br><br>Anyone who has used a #gps receiver knows that when it’s turned on, it could take from 30 to 60 seconds to calculate a position. In this “instant everything” world of ours, who has the patience to wait that long? In this blog post, I will be explaining the reasons why and what can be done about it.</div> ## What is an Ephemeris? <div class="text-justify">In order for a #gps receiver to calculate a position, it needs to know exactly where the satellites are in space. A #gps receiver knows exactly where the satellites are by downloading a fairly complicated message broadcast from each satellite in view. Each of these messages contain something called an #ephemeris which is a fancy way of saying “I am satellite A, here is where I am at time X”. Unfortunately, these messages are broadcast at a very slow rate of 50 bps (bit per second), this translates to about 30 seconds or more for the #gps receiver to receive these signals.</div> <div class="text-justify"><br>To make it worse, for a #gps receiver to calculate a position, it needs #ephemeris data from 4 different satellites. Hence, depending on the environment, the total time to receive all 4 #ephemeris can take much longer than 30 seconds, if at all.</div> ## What is an Extended Ephemeris?? <div class="text-justify">Since downloading broadcast #ephemeris takes so long, is there a way to get around it? Luckily, the answer is “Yes”.</div> <div class="text-justify"><br>#extendedephemeris technology is a way of predicting the location of the satellites for the near future, hence, the word “extended”. By comparison, broadcast #ephemeris is typically valid for 2 to 4 hours, whereas the state-of-the-art #extendedephemeris technology can be used for up to 28 days. By knowing the exact location of the satellites for the next 28 days, a #gps receiver can totally skip downloading the broadcast #ephemeris and progress directly to calculating the position as soon as the receiver is turned on. The net result of using #extendedephemeris is that instead of taking 30 to 60 seconds to get a position, a typical receiver will now take 1 to 2 seconds to get the job done.</div> <div class="text-justify"><br>Now you know why #gps takes so long to get a position and what #ephemeris / #extendedephemeris are, my next blog post will talk about how #ultralowpowergps receiver technology can get around these problems.</div> <div class="text-justify"><br></div> |
| json metadata | {"tags":["gps","ephemeris","extendedephemeris","ultralowpowergps","blockchainmygps"],"image":["http://basebandtech.com/wp-content/uploads/iStock_000000488421Small.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22644126/Trx 50409d2e012662316fea465eb75eec47cd85e8aa |
View Raw JSON Data
{
"trx_id": "50409d2e012662316fea465eb75eec47cd85e8aa",
"block": 22644126,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-22T04:52:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "gps",
"author": "fy1000000",
"permlink": "why-does-gps-take-so-long-to-get-a-position",
"title": "Why does #gps take so long to get a position?",
"body": "# Why does #gps take so long to get a position?\n\n<div class=\"pull-right\">\n<br>\n<img src=\"http://basebandtech.com/wp-content/uploads/iStock_000000488421Small.jpg\">\n</div>\n<div class=\"text-justify\"><br>Welcome back to #blockchainmygps!<br><br>One of the more prominent FAQs I hear is “Why does my #gps take so long to get a position”? <br><br>Anyone who has used a #gps receiver knows that when it’s turned on, it could take from 30 to 60 seconds to calculate a position. In this “instant everything” world of ours, who has the patience to wait that long? In this blog post, I will be explaining the reasons why and what can be done about it.</div>\n\n## What is an Ephemeris?\n\n<div class=\"text-justify\">In order for a #gps receiver to calculate a position, it needs to know exactly where the satellites are in space. A #gps receiver knows exactly where the satellites are by downloading a fairly complicated message broadcast from each satellite in view. Each of these messages contain something called an #ephemeris which is a fancy way of saying “I am satellite A, here is where I am at time X”. Unfortunately, these messages are broadcast at a very slow rate of 50 bps (bit per second), this translates to about 30 seconds or more for the #gps receiver to receive these signals.</div>\n\n<div class=\"text-justify\"><br>To make it worse, for a #gps receiver to calculate a position, it needs #ephemeris data from 4 different satellites. Hence, depending on the environment, the total time to receive all 4 #ephemeris can take much longer than 30 seconds, if at all.</div>\n\n## What is an Extended Ephemeris??\n\n<div class=\"text-justify\">Since downloading broadcast #ephemeris takes so long, is there a way to get around it? Luckily, the answer is “Yes”.</div>\n\n<div class=\"text-justify\"><br>#extendedephemeris technology is a way of predicting the location of the satellites for the near future, hence, the word “extended”. By comparison, broadcast #ephemeris is typically valid for 2 to 4 hours, whereas the state-of-the-art #extendedephemeris technology can be used for up to 28 days. By knowing the exact location of the satellites for the next 28 days, a #gps receiver can totally skip downloading the broadcast #ephemeris and progress directly to calculating the position as soon as the receiver is turned on. The net result of using #extendedephemeris is that instead of taking 30 to 60 seconds to get a position, a typical receiver will now take 1 to 2 seconds to get the job done.</div>\n\n<div class=\"text-justify\"><br>Now you know why #gps takes so long to get a position and what #ephemeris / #extendedephemeris are, my next blog post will talk about how #ultralowpowergps receiver technology can get around these problems.</div>\n\n<div class=\"text-justify\"><br></div>",
"json_metadata": "{\"tags\":[\"gps\",\"ephemeris\",\"extendedephemeris\",\"ultralowpowergps\",\"blockchainmygps\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/iStock_000000488421Small.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/05/21 15:57:27
2018/05/21 15:57:27
| parent author | newsteemians |
| parent permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain-newsteemians-05212018 |
| author | fy1000000 |
| permlink | re-newsteemians-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-newsteemians-05212018-20180521t155725148z |
| title | |
| body | Thank you newsteemians! |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22628627/Trx ce2d70853754baab03c00b2f15fe2ae6eaaf21ca |
View Raw JSON Data
{
"trx_id": "ce2d70853754baab03c00b2f15fe2ae6eaaf21ca",
"block": 22628627,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-21T15:57:27",
"op": [
"comment",
{
"parent_author": "newsteemians",
"parent_permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain-newsteemians-05212018",
"author": "fy1000000",
"permlink": "re-newsteemians-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-newsteemians-05212018-20180521t155725148z",
"title": "",
"body": "Thank you newsteemians!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/21 15:56:21
2018/05/21 15:56:21
| parent author | free.sbd.bot |
| parent permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180521t093638547z |
| author | fy1000000 |
| permlink | re-freesbdbot-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180521t155619609z |
| title | |
| body | Thank you free.sdb.bot! |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22628605/Trx 3adc787a5b4a02a1da566a7471c638ac5a4a5c03 |
View Raw JSON Data
{
"trx_id": "3adc787a5b4a02a1da566a7471c638ac5a4a5c03",
"block": 22628605,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-21T15:56:21",
"op": [
"comment",
{
"parent_author": "free.sbd.bot",
"parent_permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180521t093638547z",
"author": "fy1000000",
"permlink": "re-freesbdbot-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180521t155619609z",
"title": "",
"body": "Thank you free.sdb.bot!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/21 15:00:03
2018/05/21 15:00:03
| voter | newsteemians |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| weight | 1000 (10.00%) |
| Transaction Info | Block #22627479/Trx f3ebce9021fc2f5a087b6fc249be8d48174bb3d8 |
View Raw JSON Data
{
"trx_id": "f3ebce9021fc2f5a087b6fc249be8d48174bb3d8",
"block": 22627479,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-21T15:00:03",
"op": [
"vote",
{
"voter": "newsteemians",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"weight": 1000
}
]
}2018/05/21 14:59:57
2018/05/21 14:59:57
| parent author | fy1000000 |
| parent permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| author | newsteemians |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain-newsteemians-05212018 |
| title | |
| body | Welcome to Steem Community @fy1000000! As a gentle reminder, please keep your master password safe. The best practise is to use your private posting key to login to Steemit when posting; and the private active key for wallet related transactions. In the New Steemians project, we help new members of steem by education and resteeeming their articles. Get your articles resteemed too for maximum exposure. You can learn more about it here: https://steemit.com/introduceyourself/@gaman/new-steemians-project-launch |
| json metadata | {"app": "pysteem/0.5.4"} |
| Transaction Info | Block #22627477/Trx 756bb917a779915c77bd78b8c5a72fa6bd80d486 |
View Raw JSON Data
{
"trx_id": "756bb917a779915c77bd78b8c5a72fa6bd80d486",
"block": 22627477,
"trx_in_block": 53,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-21T14:59:57",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"author": "newsteemians",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain-newsteemians-05212018",
"title": " ",
"body": "Welcome to Steem Community @fy1000000! As a gentle reminder, please keep your master password safe. The best practise is to use your private posting key to login to Steemit when posting; and the private active key for wallet related transactions. \n\n In the New Steemians project, we help new members of steem by education and resteeeming their articles. Get your articles resteemed too for maximum exposure. You can learn more about it here: https://steemit.com/introduceyourself/@gaman/new-steemians-project-launch ",
"json_metadata": "{\"app\": \"pysteem/0.5.4\"}"
}
]
}2018/05/21 09:36:36
2018/05/21 09:36:36
| parent author | fy1000000 |
| parent permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| author | free.sbd.bot |
| permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180521t093638547z |
| title | |
| body | Hi @fy1000000. Welcome to Steemit and good luck!!! |
| json metadata | {"tags":["introduceyourself"],"users":["fy1000000"],"app":"steemit/0.1"} |
| Transaction Info | Block #22621011/Trx aa985449caa6e7ad8ff4e1af175e7dffb769189b |
View Raw JSON Data
{
"trx_id": "aa985449caa6e7ad8ff4e1af175e7dffb769189b",
"block": 22621011,
"trx_in_block": 50,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-21T09:36:36",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"author": "free.sbd.bot",
"permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180521t093638547z",
"title": "",
"body": "Hi @fy1000000. Welcome to Steemit and good luck!!!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"users\":[\"fy1000000\"],\"app\":\"steemit/0.1\"}"
}
]
}free.sbd.botupvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain2018/05/21 09:36:33
free.sbd.botupvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain
2018/05/21 09:36:33
| voter | free.sbd.bot |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22621010/Trx ea32cd32afcb5c72cdcc95b607d6bc0fdf5e4114 |
View Raw JSON Data
{
"trx_id": "ea32cd32afcb5c72cdcc95b607d6bc0fdf5e4114",
"block": 22621010,
"trx_in_block": 42,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-21T09:36:33",
"op": [
"vote",
{
"voter": "free.sbd.bot",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"weight": 10000
}
]
}carfaceupvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain2018/05/21 01:00:33
carfaceupvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain
2018/05/21 01:00:33
| voter | carface |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22610691/Trx b0c86e7d36bdd7f56178f47c7e146a4d463a2957 |
View Raw JSON Data
{
"trx_id": "b0c86e7d36bdd7f56178f47c7e146a4d463a2957",
"block": 22610691,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-21T01:00:33",
"op": [
"vote",
{
"voter": "carface",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"weight": 10000
}
]
}2018/05/20 23:26:24
2018/05/20 23:26:24
| parent author | tatyanablog |
| parent permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t210655844z |
| author | fy1000000 |
| permlink | re-tatyanablog-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t232623155z |
| title | |
| body | Yes, I am following you now! Cheers! |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22608808/Trx 53c18c6db4207d0d25bac8e9fe2813c9c801fbd0 |
View Raw JSON Data
{
"trx_id": "53c18c6db4207d0d25bac8e9fe2813c9c801fbd0",
"block": 22608808,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T23:26:24",
"op": [
"comment",
{
"parent_author": "tatyanablog",
"parent_permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t210655844z",
"author": "fy1000000",
"permlink": "re-tatyanablog-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t232623155z",
"title": "",
"body": "Yes, I am following you now! Cheers!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}fy1000000followed @tatyanablog2018/05/20 23:26:03
fy1000000followed @tatyanablog
2018/05/20 23:26:03
| required auths | [] |
| required posting auths | ["fy1000000"] |
| id | follow |
| json | ["follow",{"follower":"fy1000000","following":"tatyanablog","what":["blog"]}] |
| Transaction Info | Block #22608801/Trx 30457fd2ef67db07ddf326a499afe6bf39724687 |
View Raw JSON Data
{
"trx_id": "30457fd2ef67db07ddf326a499afe6bf39724687",
"block": 22608801,
"trx_in_block": 68,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T23:26:03",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"fy1000000"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"fy1000000\",\"following\":\"tatyanablog\",\"what\":[\"blog\"]}]"
}
]
}2018/05/20 23:23:54
2018/05/20 23:23:54
| parent author | tatyanablog |
| parent permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t210723639z |
| author | fy1000000 |
| permlink | re-tatyanablog-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t232354392z |
| title | |
| body | Hi tatyanablog! Many thanks for your kind words! Please keep in touch and read my blogs. I want to publish a few blogs to explain how to turn #ultralowpowergps and #blockchain into #cryptocurrency. Please stay tuned! |
| json metadata | {"tags":["introduceyourself","ultralowpowergps","blockchain","cryptocurrency"],"app":"steemit/0.1"} |
| Transaction Info | Block #22608758/Trx 69318e12250e1d6a374f60464e4eef11fe95f172 |
View Raw JSON Data
{
"trx_id": "69318e12250e1d6a374f60464e4eef11fe95f172",
"block": 22608758,
"trx_in_block": 90,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T23:23:54",
"op": [
"comment",
{
"parent_author": "tatyanablog",
"parent_permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t210723639z",
"author": "fy1000000",
"permlink": "re-tatyanablog-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t232354392z",
"title": "",
"body": "Hi tatyanablog! Many thanks for your kind words! Please keep in touch and read my blogs. I want to publish a few blogs to explain how to turn #ultralowpowergps and #blockchain into #cryptocurrency. Please stay tuned!",
"json_metadata": "{\"tags\":[\"introduceyourself\",\"ultralowpowergps\",\"blockchain\",\"cryptocurrency\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/20 21:38:33
2018/05/20 21:38:33
| parent author | steemsociety |
| parent permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t211659072z |
| author | fy1000000 |
| permlink | re-steemsociety-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t213830616z |
| title | |
| body | Hi steemsociety! Thanks for the tips - I am so enjoying Steemit, I think this is the best blogging platform! BIG hands to the Steemit team and community! |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22606651/Trx 6313b52e564f07eb78208322276653ac6b0f3b3f |
View Raw JSON Data
{
"trx_id": "6313b52e564f07eb78208322276653ac6b0f3b3f",
"block": 22606651,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T21:38:33",
"op": [
"comment",
{
"parent_author": "steemsociety",
"parent_permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t211659072z",
"author": "fy1000000",
"permlink": "re-steemsociety-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t213830616z",
"title": "",
"body": "Hi steemsociety! Thanks for the tips - I am so enjoying Steemit, I think this is the best blogging platform! BIG hands to the Steemit team and community!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/20 21:17:57
2018/05/20 21:17:57
| voter | steemsociety |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| weight | 2500 (25.00%) |
| Transaction Info | Block #22606239/Trx d9cac0d878f3ac85db77f75b87be7e0b1850f7bc |
View Raw JSON Data
{
"trx_id": "d9cac0d878f3ac85db77f75b87be7e0b1850f7bc",
"block": 22606239,
"trx_in_block": 41,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T21:17:57",
"op": [
"vote",
{
"voter": "steemsociety",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"weight": 2500
}
]
}2018/05/20 21:16:57
2018/05/20 21:16:57
| parent author | fy1000000 |
| parent permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| author | steemsociety |
| permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t211659072z |
| title | |
| body | Hello fy1000000! Welcome to Steemit! Hope you'll like the community here. As a start, here are 5 tips that we believe will be helpful to you: 1. **Keep your passwords safe:** Unlike conventional sites, Steemit has 4 types of passwords. Each offers varying degrees of access to your account, so know where and when to use each of them. Also, make sure to keep them all safe and secure. 2. **Get Steem rewards:** When writing a post, you'll have the option to choose how to receive your reward: "Default 50%/50%" or "Power Up 100%". As of this moment, choosing Default 50%/50% is the better option. But this can change over time. Check our post to know more. 3. **Upvote wisely:** When upvoting, wait at least 30 minutes after the post is published to maximize your curation reward. Also, make sure not to upvote too much too fast so as not to drain your voting power. 4. **Know your Steem, Steem Dollars and Steem Power:** Steem and Steem Dollars are the 2 main currencies here. Convert and power up more Steem into Steem Power so you can have higher values on your upvotes. 5. **Have Fun and Enjoy!** _For a detailed writeup, check our post [Getting Started: 5 Essential Tips for New Users](https://steemit.com/@steemsociety/getting-started-5-essential-tips-for-new-users)._ Good luck on your Steem journey! Follow us if you like to receive more helpful tips and maximize your Steemit experience. |
| json metadata | {"community":"busy","app":"busy/2.4.0","links":["https://steemit.com/@steemsociety/getting-started-5-essential-tips-for-new-users"],"tags":["introduceyourself"]} |
| Transaction Info | Block #22606219/Trx 72a456994e1d184f5808f0aa741f450e418a5b50 |
View Raw JSON Data
{
"trx_id": "72a456994e1d184f5808f0aa741f450e418a5b50",
"block": 22606219,
"trx_in_block": 80,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T21:16:57",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"author": "steemsociety",
"permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t211659072z",
"title": "",
"body": "Hello fy1000000! Welcome to Steemit! Hope you'll like the community here. As a start, here are 5 tips that we believe will be helpful to you:\n1. **Keep your passwords safe:** Unlike conventional sites, Steemit has 4 types of passwords. Each offers varying degrees of access to your account, so know where and when to use each of them. Also, make sure to keep them all safe and secure.\n2. **Get Steem rewards:** When writing a post, you'll have the option to choose how to receive your reward: \"Default 50%/50%\" or \"Power Up 100%\". As of this moment, choosing Default 50%/50% is the better option. But this can change over time. Check our post to know more.\n3. **Upvote wisely:** When upvoting, wait at least 30 minutes after the post is published to maximize your curation reward. Also, make sure not to upvote too much too fast so as not to drain your voting power.\n4. **Know your Steem, Steem Dollars and Steem Power:** Steem and Steem Dollars are the 2 main currencies here. Convert and power up more Steem into Steem Power so you can have higher values on your upvotes.\n5. **Have Fun and Enjoy!**\n\n_For a detailed writeup, check our post [Getting Started: 5 Essential Tips for New Users](https://steemit.com/@steemsociety/getting-started-5-essential-tips-for-new-users)._\n\nGood luck on your Steem journey! Follow us if you like to receive more helpful tips and maximize your Steemit experience.\n",
"json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.4.0\",\"links\":[\"https://steemit.com/@steemsociety/getting-started-5-essential-tips-for-new-users\"],\"tags\":[\"introduceyourself\"]}"
}
]
}2018/05/20 21:07:21
2018/05/20 21:07:21
| parent author | fy1000000 |
| parent permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| author | tatyanablog |
| permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t210723639z |
| title | |
| body | Hello! The company has great prospects and I want to become a friend to do more ; |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22606027/Trx 75496686c7358c1f53d54acba1f078b802f5b3b9 |
View Raw JSON Data
{
"trx_id": "75496686c7358c1f53d54acba1f078b802f5b3b9",
"block": 22606027,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T21:07:21",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"author": "tatyanablog",
"permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t210723639z",
"title": "",
"body": "Hello! The company has great prospects and I want to become a friend to do more ;",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/20 21:06:54
2018/05/20 21:06:54
| parent author | fy1000000 |
| parent permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| author | tatyanablog |
| permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t210655844z |
| title | |
| body | Hello interesting article! I follow you, and you follow me. Let's develop the power of Steemit together, so we can achieve more! Upvoted your post! |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22606018/Trx 7a824d17d10236209732f7384cd0e53c17686728 |
View Raw JSON Data
{
"trx_id": "7a824d17d10236209732f7384cd0e53c17686728",
"block": 22606018,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T21:06:54",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"author": "tatyanablog",
"permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t210655844z",
"title": "",
"body": "Hello interesting article! I follow you, and you follow me. Let's develop the power of Steemit together, so we can achieve more! Upvoted your post!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}tatyanablogupvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain2018/05/20 21:06:36
tatyanablogupvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain
2018/05/20 21:06:36
| voter | tatyanablog |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22606012/Trx df02a5120ed862e5492aa0ae4c45651de4702b35 |
View Raw JSON Data
{
"trx_id": "df02a5120ed862e5492aa0ae4c45651de4702b35",
"block": 22606012,
"trx_in_block": 36,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T21:06:36",
"op": [
"vote",
{
"voter": "tatyanablog",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"weight": 10000
}
]
}2018/05/20 20:25:42
2018/05/20 20:25:42
| parent author | cheneats |
| parent permlink | re-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t172209 |
| author | fy1000000 |
| permlink | re-cheneats-re-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t172209-20180520t202539484z |
| title | |
| body | Hi cheneats, thanks for the kind words & the very useful links. May the force be also with you my friend! Cheers! |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22605194/Trx 938e5add69bbb8724db46de074961aa89b52986d |
View Raw JSON Data
{
"trx_id": "938e5add69bbb8724db46de074961aa89b52986d",
"block": 22605194,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T20:25:42",
"op": [
"comment",
{
"parent_author": "cheneats",
"parent_permlink": "re-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t172209",
"author": "fy1000000",
"permlink": "re-cheneats-re-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t172209-20180520t202539484z",
"title": "",
"body": "Hi cheneats, thanks for the kind words & the very useful links. May the force be also with you my friend! Cheers!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}fy1000000published a new post: the-starting-point-gps-my-discovery-of-steemit-and-block-chain2018/05/20 17:25:18
fy1000000published a new post: the-starting-point-gps-my-discovery-of-steemit-and-block-chain
2018/05/20 17:25:18
| parent author | |
| parent permlink | introduceyourself |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| title | The Starting Point – GPS, my discovery of Steemit and Block Chain. |
| body | @@ -3677,22 +3677,22 @@ GPS and +# block - chain co |
| json metadata | {"tags":["introduceyourself","blockchain","cryptocurrency","mining","dapp"],"users":["louisthomas","theawakenment","boxmining","benperrin117","jerrybanfield","dantheman"],"image":["http://basebandtech.com/wp-content/uploads/2014/05/iStock_000006503946Large-250x333.png","http://basebandtech.com/wp-content/uploads/The-Starting-Point.jpg"],"links":["http://www.linkedin.com/in/basebandtechnologies"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22601586/Trx 1f3c98a9298c83ccfe531d55d08e3215052a9f02 |
View Raw JSON Data
{
"trx_id": "1f3c98a9298c83ccfe531d55d08e3215052a9f02",
"block": 22601586,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T17:25:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "introduceyourself",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"title": "The Starting Point – GPS, my discovery of Steemit and Block Chain.",
"body": "@@ -3677,22 +3677,22 @@\n GPS and \n+#\n block\n- \n chain co\n",
"json_metadata": "{\"tags\":[\"introduceyourself\",\"blockchain\",\"cryptocurrency\",\"mining\",\"dapp\"],\"users\":[\"louisthomas\",\"theawakenment\",\"boxmining\",\"benperrin117\",\"jerrybanfield\",\"dantheman\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/2014/05/iStock_000006503946Large-250x333.png\",\"http://basebandtech.com/wp-content/uploads/The-Starting-Point.jpg\"],\"links\":[\"http://www.linkedin.com/in/basebandtechnologies\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ayerzupvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain2018/05/20 17:22:33
ayerzupvoted (100.00%) @fy1000000 / the-starting-point-gps-my-discovery-of-steemit-and-block-chain
2018/05/20 17:22:33
| voter | ayerz |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22601531/Trx 1085b34b6447b6386a0abe29baba5abd07595131 |
View Raw JSON Data
{
"trx_id": "1085b34b6447b6386a0abe29baba5abd07595131",
"block": 22601531,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T17:22:33",
"op": [
"vote",
{
"voter": "ayerz",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"weight": 10000
}
]
}2018/05/20 17:22:12
2018/05/20 17:22:12
| voter | cheneats |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| weight | 100 (1.00%) |
| Transaction Info | Block #22601524/Trx 281eca3b9b9ceb571af546c85498abee36cf01c0 |
View Raw JSON Data
{
"trx_id": "281eca3b9b9ceb571af546c85498abee36cf01c0",
"block": 22601524,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T17:22:12",
"op": [
"vote",
{
"voter": "cheneats",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"weight": 100
}
]
}2018/05/20 17:22:09
2018/05/20 17:22:09
| parent author | fy1000000 |
| parent permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| author | cheneats |
| permlink | re-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t172209 |
| title | |
| body | Greetings, fy1000000! I wish you make many new friends here in this awesome community :) May the force be with you ;) By the way, there are several groups you as a newcomer can join. They will stay with you for your journey, helping and mentoring along the way. @greetersguild invite link https://discord.gg/AkzNSKx @newbieresteemday invite link https://discord.gg/2ZcAxsU |
| json metadata | |
| Transaction Info | Block #22601523/Trx 03ce24ddd03a4e763a799ef6415dac907eeb8ac3 |
View Raw JSON Data
{
"trx_id": "03ce24ddd03a4e763a799ef6415dac907eeb8ac3",
"block": 22601523,
"trx_in_block": 52,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T17:22:09",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"author": "cheneats",
"permlink": "re-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t172209",
"title": "",
"body": "Greetings, fy1000000! I wish you make many new friends here in this awesome community :) May the force be with you ;)\n\nBy the way, there are several groups you as a newcomer can join. They will stay with you for your journey, helping and mentoring along the way.\n\n@greetersguild invite link https://discord.gg/AkzNSKx\n@newbieresteemday invite link https://discord.gg/2ZcAxsU",
"json_metadata": ""
}
]
}fy1000000published a new post: the-starting-point-gps-my-discovery-of-steemit-and-block-chain2018/05/20 17:21:18
fy1000000published a new post: the-starting-point-gps-my-discovery-of-steemit-and-block-chain
2018/05/20 17:21:18
| parent author | |
| parent permlink | introduceyourself |
| author | fy1000000 |
| permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| title | The Starting Point – GPS, my discovery of Steemit and Block Chain. |
| body | @@ -891,17 +891,16 @@ w-power -# GPS #ult |
| json metadata | {"tags":["introduceyourself","blockchain","cryptocurrency","mining","dapp"],"users":["louisthomas","theawakenment","boxmining","benperrin117","jerrybanfield","dantheman"],"image":["http://basebandtech.com/wp-content/uploads/2014/05/iStock_000006503946Large-250x333.png","http://basebandtech.com/wp-content/uploads/The-Starting-Point.jpg"],"links":["http://www.linkedin.com/in/basebandtechnologies"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22601506/Trx ba44ef17f63a1549f3b3913fc4e1a6ef4b3cac5e |
View Raw JSON Data
{
"trx_id": "ba44ef17f63a1549f3b3913fc4e1a6ef4b3cac5e",
"block": 22601506,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T17:21:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "introduceyourself",
"author": "fy1000000",
"permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"title": "The Starting Point – GPS, my discovery of Steemit and Block Chain.",
"body": "@@ -891,17 +891,16 @@\n w-power \n-#\n GPS #ult\n",
"json_metadata": "{\"tags\":[\"introduceyourself\",\"blockchain\",\"cryptocurrency\",\"mining\",\"dapp\"],\"users\":[\"louisthomas\",\"theawakenment\",\"boxmining\",\"benperrin117\",\"jerrybanfield\",\"dantheman\"],\"image\":[\"http://basebandtech.com/wp-content/uploads/2014/05/iStock_000006503946Large-250x333.png\",\"http://basebandtech.com/wp-content/uploads/The-Starting-Point.jpg\"],\"links\":[\"http://www.linkedin.com/in/basebandtechnologies\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/05/20 15:45:54
2018/05/20 15:45:54
| parent author | fy1000000 |
| parent permlink | re-mepatriot-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t153615723z |
| author | mepatriot |
| permlink | re-fy1000000-re-mepatriot-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t154557880z |
| title | |
| body | Cheers! |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22599599/Trx 1767488dc0ec7066fc47d78aba2a5abb0c56fca9 |
View Raw JSON Data
{
"trx_id": "1767488dc0ec7066fc47d78aba2a5abb0c56fca9",
"block": 22599599,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T15:45:54",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "re-mepatriot-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t153615723z",
"author": "mepatriot",
"permlink": "re-fy1000000-re-mepatriot-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t154557880z",
"title": "",
"body": "Cheers!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/20 15:36:15
2018/05/20 15:36:15
| parent author | mepatriot |
| parent permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t152729802z |
| author | fy1000000 |
| permlink | re-mepatriot-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t153615723z |
| title | |
| body | Will do & Thanks mepatriot! Cheers! |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22599406/Trx 14aefb42f6c7a0bf6a8c089a1cf706ec114ee7f7 |
View Raw JSON Data
{
"trx_id": "14aefb42f6c7a0bf6a8c089a1cf706ec114ee7f7",
"block": 22599406,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T15:36:15",
"op": [
"comment",
{
"parent_author": "mepatriot",
"parent_permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t152729802z",
"author": "fy1000000",
"permlink": "re-mepatriot-re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t153615723z",
"title": "",
"body": "Will do & Thanks mepatriot! Cheers!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/20 15:33:30
2018/05/20 15:33:30
| parent author | fy1000000 |
| parent permlink | re-holoz0r-how-to-use-div-tags-in-steemit-post-layouts-pull-right-and-left-20180517t044934001z |
| author | fy1000000 |
| permlink | re-fy1000000-re-holoz0r-how-to-use-div-tags-in-steemit-post-layouts-pull-right-and-left-20180520t151038849z |
| title | |
| body | I found a roundabout way to do this ---every time you cascade the `<div>` tag, the image gets resized by 50%. For example: `<div class="pull-left">` `<div class="pull-left"> ` `http://basebandtech.com/wp-content/uploads/admin.png` `</div>` `</div>` |
| json metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
| Transaction Info | Block #22599351/Trx f36087bd717267765c502ea6d12d2c858813cf34 |
View Raw JSON Data
{
"trx_id": "f36087bd717267765c502ea6d12d2c858813cf34",
"block": 22599351,
"trx_in_block": 61,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T15:33:30",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "re-holoz0r-how-to-use-div-tags-in-steemit-post-layouts-pull-right-and-left-20180517t044934001z",
"author": "fy1000000",
"permlink": "re-fy1000000-re-holoz0r-how-to-use-div-tags-in-steemit-post-layouts-pull-right-and-left-20180520t151038849z",
"title": "",
"body": "I found a roundabout way to do this ---every time you cascade the `<div>` tag, the image gets resized by 50%. \n\nFor example:\n`<div class=\"pull-left\">`\n`<div class=\"pull-left\"> `\n`http://basebandtech.com/wp-content/uploads/admin.png`\n`</div>`\n`</div>`",
"json_metadata": "{\"tags\":[\"tutorial\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/20 15:33:18
2018/05/20 15:33:18
| parent author | fy1000000 |
| parent permlink | re-primus-how-to-use-new-hidden-steemit-features-for-custom-formatting-within-post-content-floating-right-left-and-justifying-20180517t045334179z |
| author | fy1000000 |
| permlink | re-fy1000000-re-primus-how-to-use-new-hidden-steemit-features-for-custom-formatting-within-post-content-floating-right-left-and-justifying-20180520t150956698z |
| title | |
| body | I found a roundabout way to do this ---every time you cascade the `<div>` tag, the image gets resized by 50%. For example: `<div class="pull-left">` `<div class="pull-left"> ` `http://basebandtech.com/wp-content/uploads/admin.png` `</div>` `</div>` |
| json metadata | {"tags":["steemit"],"app":"steemit/0.1"} |
| Transaction Info | Block #22599347/Trx 1ed48d3a38b5506ed1da8fe3b14444c51e5bda92 |
View Raw JSON Data
{
"trx_id": "1ed48d3a38b5506ed1da8fe3b14444c51e5bda92",
"block": 22599347,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T15:33:18",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "re-primus-how-to-use-new-hidden-steemit-features-for-custom-formatting-within-post-content-floating-right-left-and-justifying-20180517t045334179z",
"author": "fy1000000",
"permlink": "re-fy1000000-re-primus-how-to-use-new-hidden-steemit-features-for-custom-formatting-within-post-content-floating-right-left-and-justifying-20180520t150956698z",
"title": "",
"body": "I found a roundabout way to do this ---every time you cascade the `<div>` tag, the image gets resized by 50%. \n\nFor example:\n`<div class=\"pull-left\">`\n`<div class=\"pull-left\"> `\n`http://basebandtech.com/wp-content/uploads/admin.png`\n`</div>`\n`</div>`",
"json_metadata": "{\"tags\":[\"steemit\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/20 15:32:18
2018/05/20 15:32:18
| parent author | fy1000000 |
| parent permlink | re-grocko-formatting-help-how-to-make-your-blogs-stand-out-20180520t002054063z |
| author | fy1000000 |
| permlink | re-fy1000000-re-grocko-formatting-help-how-to-make-your-blogs-stand-out-20180520t151406818z |
| title | |
| body | I found a roundabout way to do this ---every time you cascade the `<div>` tag, the image gets resized by 50%. For example: `<div class="pull-left">` `<div class="pull-left"> ` `http://basebandtech.com/wp-content/uploads/admin.png` `</div>` `</div>` |
| json metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
| Transaction Info | Block #22599327/Trx a36187ae3c5dd081ff708bc838da51d9828f9c4f |
View Raw JSON Data
{
"trx_id": "a36187ae3c5dd081ff708bc838da51d9828f9c4f",
"block": 22599327,
"trx_in_block": 36,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T15:32:18",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "re-grocko-formatting-help-how-to-make-your-blogs-stand-out-20180520t002054063z",
"author": "fy1000000",
"permlink": "re-fy1000000-re-grocko-formatting-help-how-to-make-your-blogs-stand-out-20180520t151406818z",
"title": "",
"body": "I found a roundabout way to do this ---every time you cascade the `<div>` tag, the image gets resized by 50%. \n\nFor example:\n`<div class=\"pull-left\">`\n`<div class=\"pull-left\"> `\n`http://basebandtech.com/wp-content/uploads/admin.png`\n`</div>`\n`</div>`",
"json_metadata": "{\"tags\":[\"tutorial\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/20 15:27:27
2018/05/20 15:27:27
| parent author | fy1000000 |
| parent permlink | the-starting-point-gps-my-discovery-of-steemit-and-block-chain |
| author | mepatriot |
| permlink | re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t152729802z |
| title | |
| body | Welcome! It is so nice to have you here with us. Please let me know if you have any questions, and I will be glad to try to help out if I can. Good luck! |
| json metadata | {"tags":["introduceyourself"],"app":"steemit/0.1"} |
| Transaction Info | Block #22599230/Trx 9db91cd5c8cc096c8f18f19f25aaf5ccb9557f04 |
View Raw JSON Data
{
"trx_id": "9db91cd5c8cc096c8f18f19f25aaf5ccb9557f04",
"block": 22599230,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-20T15:27:27",
"op": [
"comment",
{
"parent_author": "fy1000000",
"parent_permlink": "the-starting-point-gps-my-discovery-of-steemit-and-block-chain",
"author": "mepatriot",
"permlink": "re-fy1000000-the-starting-point-gps-my-discovery-of-steemit-and-block-chain-20180520t152729802z",
"title": "",
"body": "Welcome! It is so nice to have you here with us. Please let me know if you have any questions, and I will be glad to try to help out if I can. Good luck!",
"json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779064230
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779064230
},
"rc_account": {
"account": "fy1000000",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779064230
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://steemitimages.com/DQmVaqSwy7WszGohG7X6VqSTdtCnEA3TqoWwc5RqrZ95uzT/2015-9-29-22-2-58-42.jpg","name":"fy1000000","cover_image":"https://steemitimages.com/DQmZuEDSwpS7FdCs1jMHbXMzyMXC7CYnrpjHBCtGMd3d8pM/Untitled%20design.png","location":"Calgary, Canada","website":"http://www.basebandtech.com","about":"My goal for this blog is to be a platform of information, learning & inspiration for those who are interested in lower power GPS & block chain technologies."} |
| JSON METADATA | |
| profile | {"profile_image":"https://steemitimages.com/DQmVaqSwy7WszGohG7X6VqSTdtCnEA3TqoWwc5RqrZ95uzT/2015-9-29-22-2-58-42.jpg","name":"fy1000000","cover_image":"https://steemitimages.com/DQmZuEDSwpS7FdCs1jMHbXMzyMXC7CYnrpjHBCtGMd3d8pM/Untitled%20design.png","location":"Calgary, Canada","website":"http://www.basebandtech.com","about":"My goal for this blog is to be a platform of information, learning & inspiration for those who are interested in lower power GPS & block chain technologies."} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://steemitimages.com/DQmVaqSwy7WszGohG7X6VqSTdtCnEA3TqoWwc5RqrZ95uzT/2015-9-29-22-2-58-42.jpg",
"name": "fy1000000",
"cover_image": "https://steemitimages.com/DQmZuEDSwpS7FdCs1jMHbXMzyMXC7CYnrpjHBCtGMd3d8pM/Untitled%20design.png",
"location": "Calgary, Canada",
"website": "http://www.basebandtech.com",
"about": "My goal for this blog is to be a platform of information, learning & inspiration for those who are interested in lower power GPS & block chain technologies."
}
},
"json_metadata": {
"profile": {
"profile_image": "https://steemitimages.com/DQmVaqSwy7WszGohG7X6VqSTdtCnEA3TqoWwc5RqrZ95uzT/2015-9-29-22-2-58-42.jpg",
"name": "fy1000000",
"cover_image": "https://steemitimages.com/DQmZuEDSwpS7FdCs1jMHbXMzyMXC7CYnrpjHBCtGMd3d8pM/Untitled%20design.png",
"location": "Calgary, Canada",
"website": "http://www.basebandtech.com",
"about": "My goal for this blog is to be a platform of information, learning & inspiration for those who are interested in lower power GPS & block chain technologies."
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM73sGX2JhTvia792treeyyoh3TCUnnZaRgwcDmyc8PbLMHhB1BQ1/1
Active
Single Signature
Public Keys
STM5CuL3JcdeE78YxxNAcB8FaTsw1uq6Qgcz4rAscHE7NtKahey1i1/1
Posting
Single Signature
Public Keys
STM6T8d8AncrKqPiRJn3JbNR8RTMUebuEd46btVQaQadqHmYyS8CZ1/1
Memo
STM6b8bAgoAp8DwecvzchNJm1sD8FonVon7eAHNfkxpSwYB6HK5ij
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM73sGX2JhTvia792treeyyoh3TCUnnZaRgwcDmyc8PbLMHhB1BQ",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5CuL3JcdeE78YxxNAcB8FaTsw1uq6Qgcz4rAscHE7NtKahey1i",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6T8d8AncrKqPiRJn3JbNR8RTMUebuEd46btVQaQadqHmYyS8CZ",
1
]
]
},
"memo": "STM6b8bAgoAp8DwecvzchNJm1sD8FonVon7eAHNfkxpSwYB6HK5ij"
}Witness Votes
0 / 30
No active witness votes.
[]