Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/50 hall speed sensor #118

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Conversation

sarfata
Copy link
Owner

@sarfata sarfata commented Jan 9, 2018

Allows a user to connect a good-old paddle wheel to KBox and get a 10Hz speed sensor that speaks NMEA and NMEA2000.

Work in progress. @ronzeiller you might be interested in this too.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 68.142% when pulling 33ec3dd on feature/50-hall-speed-sensor into 9910db5 on master.

@ronzeiller
Copy link
Contributor

ronzeiller commented Jan 9, 2018

@sarfata
Yes I am interested, in deed.

Just a few thoughts:

  • I would recommend to name Services less generic, as they are very special for a dedicated design.
  • Another question is, how to connect the sensor? (new cable from KBox to bow?)
  • Wouldn't it make sense to build an own box for translation of ticks and conversion to N2k or NMEA0183 and send the signal over already existing cables, (similar to this: http://www.airmartechnology.com/productdescription.html?id=199), or take the 12V from somewhere and send the signal over Bluetooth?
  • Nice to have: the correction table mechanism (reading, interpolationg...) needed to correct for non linearity of the ST650 ticks could nicely also be used for correction of common speed transducers.
  • Lot of work to get a rather old sensor calibrated, converted, filtered,...... just for a hand full users?
  • I like the idea of connecting special devices directly to I2C or Analog Input of Teensy, even if it will be quite proprietary.

@sarfata
Copy link
Owner Author

sarfata commented Jan 11, 2018

Yes you need a separate cable and probably I will make a small PCB with an optocoupler for this use-case. Why make a new product when KBox can do it? It's easier to have only one design. With config, you could have a KBox doing just this conversion in the bow. It's still much cheaper than any of the commercial options.

This is very interesting to people who have an old sensor and want to send the data on NMEA2000 bus. I had that on my boat and hauling the boat to drill a new hole of a different size for the new sensor was not a simple operation.

The other very interesting thing for racers is that we can send speed at 10Hz instead of the 1Hz of the DST800. So it is much cheaper, and actually much better too.

I agree that other work on calibration/correction should apply to any sensor.

How would you name it?

@ronzeiller
Copy link
Contributor

Yes you need a separate cable and probably I will make a small PCB with an optocoupler for this use-case. Why make a new product when KBox can do it? It's easier to have only one design. With config, you could have a KBox doing just this conversion in the bow. It's still much cheaper than any of the commercial options.

I agree, that this is a great solution.
And this is exactly what I meant, that the KBox Software could easily manage such sensors.
(It´s only a small step from a PCB with optocoupler to a PCB with a readymade Teensy.....,
may be with additional Bluetooth function in the future - thinking also of external, solar powered displays, like Tacktick/Raymarine has made them.....)

The other very interesting thing for racers is that we can send speed at 10Hz instead of the 1Hz of the DST800. So it is much cheaper, and actually much better too.

💯

How would you name it?

Something like PaddleWheelService, or ST650Service (depending of how many other similar paddlewheel sensors are out there), BSTransducerService for Boat Speed Transducer....?

BTW: I plan to go for an external IMU-Sensor based on the NXP, which could also be directly connected to KBox (I2C)....

And improve calculation of speed by using all pulses instead of just the
duration of the last one received.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants