| 18 Sep 2018 |
 sean | In reply to @neutronstar:matrix.org
Realized that my message in the mission room regarding what electronics to use should have been in this room, sorry for that. Feel free to comment my message here instead! Care to repost for context? | 19:06:41 |
 neutronstar | Ok, here is the repost:
Being an embedded developer, I couldn't resist the urge to look on what electronics that we might use. I've read up a bit on how to secure electronics against radiation and what electronics that might be bought off the shelf. After much consideration I've come to the conclusion that we can skip special radiation hardened electronics, except perhaps for some special smaller application. I would instead propose to use a number of smaller cheaper single board computers and use them in a voting and/or load balancing configuration. One suggestion below, costs 5$ each:
https://www.kickstarter.com/projects/onion/omega2-5-iot-computer-with-wi-fi-powered-by-linux
We need some I/O board to interface motors and sensors, and perhaps some voting hardware.
Any thoughts on this? | 19:10:26 |
| sean | There's a MIL spec somewhere (I'll try and look for it) that's often referred to for qualifying space grade hardware. It might be overkill for our applications, but it might give us some set of constraints to work with. | 19:21:59 |
| neutronstar | The problem with electronics adhering to military or space standards is not only costs, but also ITAR. This basically means no development outside USA for an open-source project, and even within USA there might be a bunch of rules to follow. A lot of hassle. Unless I've misunderstood something...
The exception would be if we found hardware from outside USA, but then it could be ITAR classified as soon as it reaches the borders.
So this is the reason I propose to use standard components. But we could of course improve it using good casing etc. | 19:55:13 |
| 21 Sep 2018 |
|  mhpanda joined the room. | 14:32:17 |
| 1 Oct 2018 |
|  danktron joined the room. | 20:04:21 |
| 12 Oct 2018 |
|  greg.g joined the room. | 23:47:28 |
| 19 Oct 2018 |
|  pete.b joined the room. | 22:36:30 |
| 16 Nov 2018 |
|  grouchofractal joined the room. | 20:06:41 |
| 28 Nov 2018 |
|  theobtl joined the room. | 15:31:24 |
| 12 Dec 2018 |
|  @lkngtn:matrix.org left the room. | 14:39:18 |
| 20 Dec 2018 |
| neutronstar | I came across a micro-kernel named seL4. It looks interesting since it has been mathematically proven to be bug-free, and has been used for space applications before. It has some commercial backing while being open source (GPL). I haven't looked too deeply into it but it's implemented in C, and as far as I can see applications are expected to run in C as well. It is communications oriented, which I see as a good thing (I hate mutexes/semaphores etc...).
The drawback I can see so far is that this would limit us to ARM-based technology, which would exclude the Omega2 I proposed above. I don't think this is a big issue, since there is quite a lot to choose from anyway, but I thought I'd mention this since I proposed a MIPS based architecture above.
Here's the link:
https://github.com/seL4/seL4 | 09:13:33 |
| 7 Jan 2019 |
|  mmarc1 joined the room. | 14:59:52 |
| 18 Jan 2019 |
|  Daniell Mesquita joined the room. | 12:25:24 |
| Daniell Mesquita | Hi @room
I have some proposals. First, satelites to bridge the communication between Moon and Earth through an CJDNS/Althea mesh network. These satelites could also provide meshnetworks bridge with clearnet, decentralizing Internet and making it accessible for people who live in poverty | 12:29:05 |
 tmallard | This is the company working with EXA and Irvine's cubesat orbiter from ground, uses laser to moon irrc: http://rbcsignals.com/ | 16:11:40 |
| 19 Jan 2019 |
|  jbperry joined the room. | 19:48:24 |
| 24 Jan 2019 |
| sean | @room I've been contemplating bringing back development meetings as to start tackling the various software development aspects of space decentral. This may include, but not limited to, resolving issues pertaining to the spacedecentral.net platform (in Ruby, soon to be React/Javascript), developing flight software (in C?) for space missions (s.a., Coral), numerical modeling/simulations (in Python?), setting up backend tools/APIs (s.a. for systems engineering), and/or writing software requirements/specifications for any of the aforementioned. Would anyone be interesting, and if so, do you have a general availability schedule? The tentative meeting time is Wednesdays @2pm PST, but we can try and change that if it doesn't fit well into peoples schedules. | 19:29:50 |
| sean | *interested | 19:31:36 |
| 25 Jan 2019 |
| tmallard | I've got boundary equations going to model the dust ... novice at py ... comsol solidworks user | 05:13:59 |
| tmallard | 
Download IMG_20190124_211610.jpg | 05:20:35 |
 kevin | tmallard: what does comsol mean? | 05:27:19 |
| tmallard | It's a multiphysics simulation suite plugin to solidworks, used by Boeing out here the main users. | 05:41:23 |
| tmallard | Here's a study of an induction pipe heater using it: https://www.comsol.com/model/inline-induction-heater-35541 | 05:42:51 |
| neutronstar | @sean I'm interested in the flight computer part, I have no knowledge in web development. For me the only time that works for teleconference is the time used by the other meetings. The day however is flexible as long as it doesn't collide with Coral or Lander meetings. | 06:01:51 |
| sean | neutronstar How would in-riot meetings work for you? Would you possibly also be interested in the spec writing side? It might also be worth getting in touch with the #spacedecentral-coral-lander:matrix.org group, as I believe they've started looking into flight software requirements for Coral | 06:31:02 |
| neutronstar | @sean I was the one initiating flight software/hardware discussion in the lander group. I also tried starting such discussion in this forum by suggesting software, but haven't been able to get much discussion going.
How does Riot-meetings work and how do they differ from Riot discussions or teleconferencing?
If you with spec writing mean software requirements, design specification and test specifications then I could help out with that. I can also help with development environment. | 07:13:58 |
| sean |
How does Riot-meetings work and how do they differ from Riot discussions or teleconferencing?
It'd be no different than a riot discussion. | 07:41:47 |
| sean |
If you with spec writing mean software requirements, design specification and test specifications then I could help out with that. I can also help with development environment.
That'd be great! | 07:42:12 |
| 26 Jan 2019 |
| Daniell Mesquita |
Hi @room
I have some proposals. First, satelites to bridge the communication between Moon and Earth through an CJDNS/Althea mesh network. These satelites could also provide meshnetworks bridge with clearnet, decentralizing Internet and making it accessible for people who live in poverty
Hi?
| 00:15:07 |
