Open Design Engine

It hasn't been a full week since our last stand up, so the reports are a little shorter than usual. Still, we are making progress again and are looking pretty good as we pass the half way mark.

J's Report

• Did
  • DEV-02: Determine if we should use a tone ring vs. existing single magnet design - documented research and getting close to reaching a conclusion (looks very likely that we will want to move to a commercial sensor/tone ring combination)
  • Get newsletter published - worked with Ingrid, expect to publish in the next day or so
  • BIZ-09: Submit books for tax accounting - packaged and sent materials to accountant (our end is basically done, but won't claim done until accountant sends back tax paperwork)
• Will do
  • BIZ-03: Generate required reports and confirm accuracy - will review Bryan's documentation and prepare annual report
  • DEV-02: Determine if we should use a tone ring vs. existing single magnet design - complete research and document results
  • CAMP-03: Review docs for new campaigns on Crowd Supply's website - will locate and review Crowd Supply materials
• Blocked?
  • on travel through Sat, will need some time to recover Sun/Mon, so still not overloading commitments

Bryan's Report

• Did
  • BIZ-05: Create LLC documentation covering regular reporting requirements (what, when, how, where) - done, doc is on Google drive
  • DEV-06: Test Keyboard USB HID over USB-Gadget - read up more on Docker
  • CAMP-01: Review articles/information from Fred Hicks regarding kickstarter campaigns - started reading, taking notes on google drive
  • DEV-03: Fix Bug #276 (Sensors are 5v logic feeding into 3.3v inputs on the controller) - attached pins to put together breadboard for testing
• Will do
  • DEV-06: Test Keyboard USB HID over USB-Gadget - more reading about Docker
  • CAMP-01: Review articles/information from Fred Hicks regarding kickstarter campaigns - more reading and note taking
  • DEV-03: Fix Bug #276 (Sensors are 5v logic feeding into 3.3v inputs on the controller) - look over circuit and figure out how to insert the breadboard in the middle w/ voltage step chip
• Blocked?
  • not sure if there is time to commit to anything else

Both Bryan and I ran into more blocks (business travel and long work hours for J, unplanned family visits and external demands for Bryan) than we expected last week. The results are little progress made last week (but things are starting to move again) and missing our stand up date. So, here is our belated stand up 3 for this sprint.

J's Report

• Did
  • Published Sprint 1 blog post
  • Get newsletter published - sent Ingrid an email about the next newsletter
  • DEV-10: Select BT HID module from CHIP's BT module or an external one / DEV-11: Select BT Host module from CHIP's BT module or an external one - finished [[Bluetooth|documenting research and findings]]
  • DEV-02: Determine if we should use a tone ring vs. existing single magnet design - as part of prep work, did some research on tone rings and discovered there are low cost/high sensitivity commercial sensors/tone rings that report speed and direction; we should seriously consider switching to one of these options in place of our current sensor board as they cost less and offer higher resolution than anything we could build from scratch
  • DEV-15: Port the controller side RJ-45 wiring from the v0.3 controller to the v0.4 controller / DEV-17: Port physical switch wiring from v0.3 to v0.4 - see v0.4 Fritzing Files
• Will do
  • DEV-02: Determine if we should use a tone ring vs. existing single magnet design - continue research and document my findings with the idea of selecting one or more options to consider testing out
  • Get newsletter published - if possible
  • BIZ-09: Submit books for tax accounting - package and send materials to accountant
  • BIZ-03: Generate required reports and confirm accuracy - need to check with Bryan about process
• Blocked?
  • Get newsletter published - waiting for word back from Ingrid about the newsletter
  • BIZ-03: Generate required reports and confirm accuracy - need documentation from Bryan about how/where (BIZ-05)

Bryan's Report

• Did
  • DEV-06: Test Keyboard USB HID over USB-Gadget - got docker installed on laptop
  • BIZ-09: Submit books for tax accounting - Ran the reports for 2016 tax filing
  • BIZ-01: Identify what reports need to be generated - completed
  • BIZ-02: Confirm where the reports should be submitted - completed
• Will do
  • BIZ-05: Create LLC documentation covering regular reporting requirements (what, when, how, where) - will write this up
  • CAMP-01: Review articles/information from Fred Hicks regarding kickstarter campaigns - will post links to articles on Discord
  • DEV-06: Test Keyboard USB HID over USB-Gadget - continue with cross compiling tests in docker environment
• Blocked?
  • DEV-03: Fix Bug #276 (Sensors are 5v logic feeding into 3.3v inputs on the controller) - Realized no longer seem to own a volt meter, need to buy a new one
  • May not be available for stand up 4 due to potential schedule conflict for work
  • BIZ-11: Define schedule for checking and applying updates to website - waiting on license key for last plugin
    • J still waiting for info from Ingrid

J's Report

• Did
  • Drafted Sprint 1 blog post (would like to add image(s) before posting, will check with Ingrid for ideas)
  • DEV-10: Select BT HID module from CHIP's BT module or an external one / DEV-11: Select BT Host module from CHIP's BT module or an external one - read up on BT classic, BLE, and BT support on our target platforms; have decided on suggested path forward and started documenting research and findings on the wiki
• Will do
  • Publish Sprint 1 blog post
  • Get newsletter published
  • DEV-10: Select BT HID module from CHIP's BT module or an external one / DEV-11: Select BT Host module from CHIP's BT module or an external one - finish documenting research and findings so we can claim done
  • DEV-02: Determine if we should use a tone ring vs. existing single magnet design - start setting up test rig for tone ring on my holoseat
• Blocked?
  • Still on business travel the week and will need to rest up when I get home, so operating at reduced capacity

Bryan's Report

• Did
  • BIZ-13: Schedule backups so that they are running - done, backups are running after changing backup plug-ins to UpdraftPlus
  • BIZ-14: Determine frequency of backup/restore tests to confirm backups can be used - proposing once a year do a full restore and spot checks once a sprint to confirm archives are valid... done
    • J - sounds good, let's do annual test soon
    • Bryan - yes
  • BIZ-09: Submit books for tax accounting - still need more work here (found some issues for 2017); good to go for 2016 taxes
  • BIZ-01: Identify what reports need to be generated - almost done: identified the details of the bi-annual report and started looking into DC tax filings (looks like we have none to file this year)
• Will do
  • BIZ-09: Submit books for tax accounting - Run the reports for 2016 tax filing
  • BIZ-01: Identify what reports need to be generated - wrap it up
  • DEV-06: Test Keyboard USB HID over USB-Gadget - check out Docker build environment since other paths have not worked yet
  • BIZ-02: Confirm where the reports should be submitted - will complete
  • BIZ-05: Create LLC documentation covering regular reporting requirements (what, when, how, where) - will write this up
  • CAMP-01: Review articles/information from Fred Hicks regarding kickstarter campaigns - will post links to articles on Discord
• Blocked?
  • BIZ-11: Define schedule for checking and applying updates to website - waiting on license key for last plugin
    • J will talk to Ingrid about this while working on the newsletter
  • DEV-03: Fix Bug #276 (Sensors are 5v logic feeding into 3.3v inputs on the controller) - shipping of parts is taking a long time (will get in Mon or Tue of next week, so will be in the next commitment)

• Did
  • Posted Sprint 1 Announcement on Holoseat News Feed
  • Wrote (and published) 2017 plan blog post
  • DEV-10: Select BT HID module from CHIP's BT module or an external one / DEV-11: Select BT Host module from CHIP's BT module or an external one - spent available free time reading up on Bluetooth and bought Make: Bluetooth ebook
• Will Do
  • Write Sprint 1 blog post
• Blocked?
  • Still on business travel for the next week, so operating at reduced capacity

• Did
  • DEV-03: Fix Bug #276 (Sensors are 5v logic feeding into 3.3v inputs on the controller) - ordered logic voltage adjustment boards from Sparkfun
  • BIZ-11: Define schedule for checking and applying updates to website - discussed in sprint planning meeting and will include update checks in stand ups; updates current except one plugin (purchased and need the license key to update it)
  • BIZ-12: Setup either RSS feed or notification related to wordpress vulernabilities so we know when to check for emergency updates - RSS feeds subbed
  • BIZ-13: Schedule backups so that they are running - found plugin to monitor and backup plugin, but have not installed yet
  • BIZ-14: Determine frequency of backup/restore tests to confirm backups can be used - no significant progress
• Will do
  • BIZ-13: Schedule backups so that they are running
  • BIZ-14: Determine frequency of backup/restore tests to confirm backups can be used
  • BIZ-09: Submit books for tax accounting - go though books
  • BIZ-01: Identify what reports need to be generated - start looking at reporting requirements
• Blocked?
  • BIZ-11: Define schedule for checking and applying updates to website - waiting on license key for last plugin
  • Possible upcoming blocks around business travel

Sprint 1 planning is complete. The focus of the sprint is to address admin tasks related to the maintenance of Model B, LLC, conduct initial research about running a crowd source campaign, and continue the research and development required to lock in on the final hardware design for v0.4. The full details of the sprint are below.

Duration: 8 weeks
Stand Ups: Wednesday nights
Start: Feb 22, 2017
End: Apr 19, 2017

Backlog and Full Sprint Plan (see Backlog and Sprint 1 tabs)

• DEV-02: Determine if we should use a tone ring vs. existing single magnet design
• DEV-03: Fix Bug #276 (Sensors are 5v logic feeding into 3.3v inputs on the controller)
• DEV-06: Test Keyboard USB HID over USB-Gadget
• DEV-10: Select BT HID module from CHIP's BT module or an external one
• DEV-11: Select BT Host module from CHIP's BT module or an external one
• DEV-15: Port the controller side RJ-45 wiring from the v0.3 controller to the v0.4 controller
• DEV-17: Port physical switch wiring from v0.3 to v0.4

• J - content management
  • Post Sprint 1 Announcement on Holoseat News Feed
  • Write 2017 plan blog post
• Bryan - website admin PBIs
  • BIZ-11: Define schedule for checking and applying updates to website.
  • BIZ-12: Setup either RSS feed or notification related to wordpress vulernabilities so we know when to check for emergency updates
  • BIZ-13: Schedule backups so that they are running
  • BIZ-14: Determine frequency of backup/restore tests to confirm backups can be used

Just created our project. Woot!

All parts are in to complete the first batch of production LNAs and we have completed the artwork for the solder mask (template). Tomorrow will be a warm enough day to etch the aluminum to create the template. Once it is verified both visually and with the production of a single unit, a small batch (about five units) will be made. This may happen as early as February 9th (Sunday).

The only part left for the Mk2 unit will be the 3D printed base. I expect this to be completed and delivered to Quelab by the 12th. I may have time this weekend to drive down to Quelab to pick up the base and deliver parts for them to build their own Ground Spheres, verifying the build instructions.

This update is based on a couple of emails from Tim at Southern Stars. The short version of the update is that we have limited access for conducting from orbit testing, so Tim and Scott jumped at a chance this past week to run a from orbit test. Unfortunately, the results are inconclusive at best, and disappointing at worst. They were unable to receive signal from the CubeSat in question. Read on for full details.

The test in question involves attempting to receive signals from AeroCube 4C. This CubeSat only broadcasts on 915 MHz when it is over its mission control center, so we have to make special arrangements to conduct the from orbit tests. Specifically, we need to coordinate with its operators and Southern Stars team members must drive with the Ground Sphere to the LA area in order to be under its footprint.

This past Thursday (Jan 2), a test opportunity was arranged. The operators believe they picked up the CubeSat's signal (they saw what appeared to be the signal on a spectrum analyzer) but were not able to establish a radio lock. The following from Tim details our even less successful results.

We were less successful. We saw a number of "blips" right around the expected 914.7 MHz, but they were all very short. We saw nothing like a continuous signal that dopper-shifted as the satellite approached and receded. I suspect the blips were all local. We recorded about 10 GB worth of raw RF samples from the SDR, and we'll go over these in more detail tomorrow.

I should note: we used Scott's SDR, rather than the SDR that was sent to us. I didn't realize this until after the pass began. Scott's SDR does not have the same built-in preamp and has a smaller gain (a few dB difference? Scott can you put a number on it?) This was a mistake on our part.

We also noticed that the GS antenna did not seem to produce noticeably any different signal levels when the power supply to the preamp was plugged in, vs. when it was not plugged in. I don't know what that means. Something may or may not be broken. Or we're just not interpreting the SDR output correctly (?)

Discussions between Aaron and Scott over email confirm there was a hardware issue with Prototype 1. The preamp's power connection came loose during transport so it was not in use during the test.

It should also be noted that this attempt at a from orbit test, due to the challenges with securing test opportunities, came well out of the established testing order (see [[Testing]] wiki page for more details). Neither the lab tests nor the field tests have been run, and both need to be run to verify and validate the prototype. In all likelihood, even the lab tests would have turned up the problem with the pre-amp.

We will be circling the wagons here shortly to continue the testing. More news as it is available.

I plugged the dongle into my laptop and ran lsusb. The following is the output.

Bus 003 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T

The vendor and PID numbers match up with this entry on the rtl-sdr page:

0x0bda 0x2838 E4000 ezcap USB 2.0 DVB-T/DAB/FM dongle

Aaron mentioned that SDR# has the ability to adjust the dongle's internal preamp gain. It runs on both Windows and Linux (via Mono), so I decided to give that a try using the instructions here.

The installation of the udev rules doesn't seem to work properly in the instructions above, but you can follow these.

The kernel also automatically loads the dvb driver module for the dongle to make it available as a TV tuner. This causes rtl_test -t to complain that something is already using the dongle. You can blacklist the offending module in /etc/modprobe.d/blacklist.conf with the line:

blacklist dvb_usb_rtl28xxu

For a quick kill of the driver you can just do:

rmmod dvb_usb_rtl28xxu

SDRSharp should be able to access your dongle then.

What it looks like is that it's rtl-sdr, not SDR# that adjusts the gain of the internal preamp. From what I see in the repo SeeDeR uses rtl-sdr, so it should be possible to adjust the gain through the library without writing code to directly talk to the dongle. Tim and Scott may already know this. I'll start a thread on the forum to ask.

Just saw the news that the Orbital Cygnus launch SkyCube is manifested on has been postponed until January. This delay is to give the ISS crew time to make repairs to the cooling system.

Mach 30 wishes the ISS crew speedy and safe repairs. And we eagerly await the January launch of SkyCube.