Joel Kozikowski

> The 0x85 character cannot be sent over socket.io as an argument to > the gcode command because it does not form a valid UTF8 byte > sequence. Add a...

Hey Guys! Long time since I've been here, but I've started poking around again since I'll be starting up another project this weekend, and I've seen I've missed out on...

How about we create a single separate public repo in the SignalK space that holds all the individual sensors/applications - something like "SensESP-projects". Each sub-directory would be a complete project,...

Another idea that may be more simple than a separate repo: create a `sensors` sub-directory underneath the `examples` directory. Underneath `examples/sensors`, create sub-directories for each set of sensor source files...

Good work! Additional output/debugging text could certainly contribute some. I remember early on us being very careful of putting large hunks of text in PROGMEM so it ends up in...

@BjarneBitscrambler I happen to be looking at this right now just to familiarize myself with the code before doing some compiler/linker testing. `SensorNXP_FXOS8700_FXAS21002* sensor_fxos_fxas`, which is in `orientation_9dof_input.cpp` is another...

@BjarneBitscrambler - actually, I see now that the dynamically allocated `sensor_fxos_fxas` is a reference to a different SensESP sensor code object. The question about dynamic allocation still applies. If `filter`...

It should be known that @mairas and I discussed this issue offline several weeks ago. It is important to note that part of the "solution" is to prevent memory from...

Line 13 of heltec.cpp appears to have the wrong signature also. This issue may appear elsewhere. I do not have a wireless stick to test, so I am not making...

Is this related to #137 ?