As you know OpenPlotter 2 has a complete new system. Now there is a main app to install and uninstall multiple apps in charge of the different features. Some existing apps probably will fit some requirements of your board. For the special features of your board a dedicated app could be done. I am going to publish this week a template to make really easy apps development for openplotter without big python skills.
Ok, so let's summarize where we are and what should be done in software side for your board.
- MCP2515 (NMEA 2000): The "openplotter-can" app of openplotter 2 can deal with this out of the box. Since Moitessier HAT is connected to SPI0 and your board to SP1, it should not be problems.
- SC16IS752 (NMEA 0183): This should be added to your app.
- DS2482 (1W temperature sensors ds18b20 by I2C): This should be added to your app.
- MP1593DN (power shutdown): this feature of your board is really interesting. But here we have a problem because you are using GPIO4 (pin 7, aka GCLK) and this is the pin reserved for 1W. We use this pin in the app "openplotter-1w". This would be a duplicate feature but they could coexist. Would it be a problem to change to another free pin? If I am not wrong an script should be done to detect the power down and shutdown the system, no problem.
- MCP23017 (digital GPIO extension): this I2C chip can be added to the list of supported chips in the current "openplotter-12c" app. This app was initially conceived to work just for inputs, so data coming from these inputs are saved into assigned signal k keys. But we could set the first 8 as inputs and the second 8 as outputs and the values of the assigned signal k keys (0/1) could be sent to those outputs. Or even better if you have 2 MCP23017 we can identify them by the address and set one of them as 16 inputs and the other as 16 outputs. Does this make sense?
- MCP3424 (analog GPIO extension): Same than MCP23017 but this would be all inputs. No problem to add this to "openplotter-i2c" app.
- 12C modules of your other boards: This should be added to your app.
- What 8-28V digit. Input means?
Am I missing something else?
I have some questions too:
Do you have plans of making this board open-source and publish schemas? I ask this because long time ago I have the idea of making an open-source board+case for openplotter published in some open-source site like fritzing. That is not the best tool or the most professional to design your board but it is the easiest and the best to change, customize and to have the boards mounted by few euros (is fritzing soldering too?). This way users could adapt their boards to its requirements forking the base project and it could be improved by the community. Your board has some really interesting features that could be added to this Frankenstein open-source openplotter board
Ok, so let's summarize where we are and what should be done in software side for your board.
- MCP2515 (NMEA 2000): The "openplotter-can" app of openplotter 2 can deal with this out of the box. Since Moitessier HAT is connected to SPI0 and your board to SP1, it should not be problems.
- SC16IS752 (NMEA 0183): This should be added to your app.
- DS2482 (1W temperature sensors ds18b20 by I2C): This should be added to your app.
- MP1593DN (power shutdown): this feature of your board is really interesting. But here we have a problem because you are using GPIO4 (pin 7, aka GCLK) and this is the pin reserved for 1W. We use this pin in the app "openplotter-1w". This would be a duplicate feature but they could coexist. Would it be a problem to change to another free pin? If I am not wrong an script should be done to detect the power down and shutdown the system, no problem.
- MCP23017 (digital GPIO extension): this I2C chip can be added to the list of supported chips in the current "openplotter-12c" app. This app was initially conceived to work just for inputs, so data coming from these inputs are saved into assigned signal k keys. But we could set the first 8 as inputs and the second 8 as outputs and the values of the assigned signal k keys (0/1) could be sent to those outputs. Or even better if you have 2 MCP23017 we can identify them by the address and set one of them as 16 inputs and the other as 16 outputs. Does this make sense?
- MCP3424 (analog GPIO extension): Same than MCP23017 but this would be all inputs. No problem to add this to "openplotter-i2c" app.
- 12C modules of your other boards: This should be added to your app.
- What 8-28V digit. Input means?
Am I missing something else?
I have some questions too:
Do you have plans of making this board open-source and publish schemas? I ask this because long time ago I have the idea of making an open-source board+case for openplotter published in some open-source site like fritzing. That is not the best tool or the most professional to design your board but it is the easiest and the best to change, customize and to have the boards mounted by few euros (is fritzing soldering too?). This way users could adapt their boards to its requirements forking the base project and it could be improved by the community. Your board has some really interesting features that could be added to this Frankenstein open-source openplotter board