Hi all,
I ran some tests on LORA modulation schemes to get the best results I could
on a 100mW TX power budget.
I nearly ran out of gas during this latest test, and unfortunately I
managed to screw up my data logging, so I don't have RSSI or SNR data, but
this map contains all the places I stopped and got a two way signal on my
jet ski.
The transmitter was in my hand, the receiver was at pier 50, SF.
DIY half wave dipoles were used, with a center freq of 900MHz with a +/-
100MHz 3db roll off.
https://www.google.com/maps/d/u/0/edit?mid=1dE2QZS9cgX_oHLWyzmUNAYrjlbX0wJp…
I found that quarter wave antennas are no good (see the red markers). The
blue markers are today's test, using RFM95's from HopeRF.
To get the very long range, I used the following modulation scheme using
the RadioHead library.
RH_RF95::ModemConfig modem_config =
{
/*Reg 0x1D: BW=125kHz, Coding=4/8, Header=explicit*/
(7 << 4) | (4 << 1) | (0),
/*Reg 0x1E: Spread=4096chips/symbol, CRC=enable*/
(12 << 4) | (1 << 2),
/*Reg 0x26: LowDataRate=On, Agc=On*/
(1 << 3) | (1 << 2)
};
RF95.setModemRegisters(&modem_config);
In other news, you can still jet ski if your core body temp is 88F. Little
unpleasant though.
- - - - Begin automatically generated footer - - - -
I seek to understand, and aim to create.
Weblog: http://adammunich.com
PGP Public Key: https://pgp.mit.edu/pks/lookup?search=adam+munich
Hey Sudoers,
Jose and Abad who are proposing the cafe in the Omni Entrance Hall would
like to come to the Sudo meeting on 4/25 to meet you and talk to you all
about their proposal. This is a chance for you to clarify the lease
proposal terms and express any concerns you may have. If this would not
be a good time for them to come to the meeting, please let me know.
I have just sent the latest version of the lease to Jesse, our lawyer,
for his review. Once he gets back to me I will send the link so you can
review it before the meeting.
Laura
---------- Forwarded message ----------
From: Sameer Verma <sverma(a)sfsu.edu>
Date: Sun, Apr 22, 2018 at 12:33 PM
Subject: [OLPC-SF] Community Summit = OpenHack 2018
To: OLPC SF <olpc-sf(a)lists.laptop.org>, "olpc-open(a)lists.laptop.org" <
olpc-open(a)lists.laptop.org>, Sugar Labs Marketing <
marketing(a)lists.sugarlabs.org>, sugar <sugar(a)lists.laptop.org>, "
grassroots(a)lists.laptop.org" <grassroots(a)lists.laptop.org>, iaep <
iaep(a)lists.sugarlabs.org>
Also posted at: https://www.olpcsf.org/node/265
This year's event is a little different. We are joining forces with
some of the other projects in the Commons space at San Francisco State
University. This year's event is called Open Hack 2018.
The event is largely scheduled to run on Saturday (April 28) and
Sunday (April 29). Will have a meet-and-greet event on Friday evening
(April 27), but the main event will begin on Saturday (April 28).
The format is as follows:
1) What we typically refer to as "projects" are called "Challenges" in
this format. Anybody can Submit a Challenge. When submitting the
Challenge, you have to provide us with information about the Challenge
itself, existing resources, people involved, and the kinds of skills
that you may find helpful in completing this challenge. The goal is
that we would want to complete some degree of the Challenge by the
time we get to Sunday afternoon.
2) The Challenges will be printed and posted up on the wall starting
Friday (April 27). On Saturday morning (April 28), people who come in
will assign themselves to different challenges. It's quite common for
some of the challenges to not have any interested people. That's okay.
3) As we start to see a cluster of people collecting on a given
Challenge, we will allocate a room for them and then that room becomes
their space for the next day and a half. Unlike in the past, where we
had timed sessions (typically 75 minutes), these groups get to work on
their problem for the entire day Saturday and half day Sunday.
4) On Sunday afternoon, they present their progress and future
direction. The work (code, content, etc) will have to be made
available some place (a repo such as github) via a FOSS, or
CreativeCommons, or OpenData license.
5) After the presentations, a panel of judges will determine some form
of ranking. There may also be some token prizes.
This is somewhat different from what we've done in the past, but given
the level of maturity in our projects, and the amount of focus that is
needed to work on fixing bugs and building upon what we already have,
the hackathon approach seems to be more apt than simple presentations.
If you have somebody in mind who cannot be there physically, you can
always bring them in online. The rooms are fairly well equipped, with
whiteboards, projectors and Internet access. We are also in the
process of arranging for other operational logistics.
In the time being, take a look at the information, the code of
conduct, and submit a challenge. http://hackathon.sfsu.edu/
Registration is open. Register at
https://www.eventbrite.com/e/open-hack-sf-2018-san-
francisco-state-university-hackathon-tickets-45329250007
Also, let us know if you plan to attend, so we can look out for other
arrangements as well, as necessary.
Sameer Verma: sverma(a)sfsu.edu
Aaron Borden: adborrden(a)live.com
_______________________________________________
OLPC-SF mailing list
OLPC-SF(a)lists.laptop.org
http://lists.laptop.org/listinfo/olpc-sf
Good afternoon,
last week I was personally attacked inside the Sudo Room Hacker space and
told by Matt that I needed to leave with no context whatsoever.
This offense occurred not 5 minutes from me entering the space while I was
delivering left over bakery snacks to the table where snacks are
occasionally left.
Matt, who has previously vouched for my access to the space as a
prospective member, walked in and demanded I leave with no context
whatsoever. He was verbally hostile in his demeanor and in the content that
he was delivering.
I was told later in the day, that the "safe space" policy was being used
against me and that Matt quickly took to slanderizing me via email and 3rd
parties saying that he did not feel safe around me after he had just very
unapologetically demanded I leave the space for no reason and with no
context to the situation.
I made no verbal threats against him and I feel that he was simply using
illegitimate authoritarian methods to harass me. I can prove this via the
Omni commons and Sudo Room guide lines of which both rules are slightly
different and yet similar. Please keep that in mind at the meeting on
Wednesday.
Myself and another member attempted to discuss with him why he was so upset
with me later in the day to which he became very passionate again for no
good reason and continued to show hostility and an unwillingness to resolve
the conflict.
There needs to be a mediation meeting to have this resolved as I have taken
this offence *VERY* seriously and feel *PERSONAL*LY hurt and attacked by
this.
I will be around Wednesday for the SudoRoom Meeting to address my
grievances in person as I have been told this is the best time to do so. If
we can do it sooner, even better.
Hi All,
This is Matthew from Sudo Room.
The Peoples Open and Omni Commons connections are both down.
I was going to check to see if I could reset the router.
Is that in the Sudo Mesh Cage? Its locked.
Matthew
Hello All,
This is Matthew from Sudo. I have been unsuccessful in communicating
Sudo/Omni policy to the applying(?) member known as 'Blue'. He is
argumentative, disrespectful as witnessed by others on multiple occassions,
he has been caught sleeping in the building after being told that would get
him banned from the building.
I walked into Sudo Room a fifteen minutes ago and he was in there alone
with no other members. I told him for the tenth time that he needed another
member there and things fell apart quickly from there. He threatened me as
he was leaving, I'm done with communication and request/invoke an Omni/Sudo
Ban from the building.
Thanks!
Matthew Stewart
Ph: 510.606.0360
This is Matthew from Sudo.
I asked Caleb from Phat Beets to handle asking 'Blue' to leave.
I didn't want to escalate the situation after 'Blue' refused to leave the
building.
Caleb was unsuccessful, came into Sudo for clarity on building policy and I
explained the ongoing trouble as well as my right to invoke safe space.
Caleb is returning to his duties for Phat Beets and I feel obligated to
leave until this is resolved.
Thanks!
Matthew
Dear Sudo Room,
Here's your invoice! We appreciate your prompt payment.
Thank you for stewarding the commons.
Love and solidarity,
Omni Commons
------------------------ Pledge Summary --------------------------
Invoice # : 1378
Invoice Date: 05/01/2018
Due Date: 05/25/2018
Terms: Net 25
Amount Due: $2,000.00
The complete version has been provided as an attachment to this email.
---------------------------------------------------------------------
