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

Add Support for 2 SX1509B I/O Expanders #379

Open
wants to merge 9 commits into
base: v3.01-dev
Choose a base branch
from

Conversation

ajquick
Copy link
Contributor

@ajquick ajquick commented Apr 11, 2020

These changes add the ability to have an additional I/O expander on the Duet 2.

Pin definitions added:

220-235: SX1509b has also added an alias of '0x71'
236-251: SX1509b2 has been added, also with an alias of '0x3F'.

A bug fix was also included related to build errors that occurred when HAS_LINUX_INTERFACE was set to false.

src/DuetNG/DueXn.cpp Outdated Show resolved Hide resolved
@ajquick
Copy link
Contributor Author

ajquick commented Apr 13, 2020

Currently this is functioning as follows:

Additional IO board is found and correctly identified as having two SX1509B chips. Diagnostics reports back:

  • SX1509B expander (0x71 & 0x3E)

However, it does not appear that any commands sent to the newly assigned pins prefixed with "0x3F." are doing anything. However, using the other name for the same pins ("sx1509b2.") works. Not sure why that is.

Pins must be lowercase.
Fix typo in diagnostic reporting.
@ajquick
Copy link
Contributor Author

ajquick commented Apr 18, 2020

I found that I had a typo (3E vs 3F) and the logical pin names were capitalized. I have fixed that and everything is now working 100% as expected.

@ajquick
Copy link
Contributor Author

ajquick commented Jun 18, 2020

Just following up to see if this will be added in the next release?

abates-dentsu pushed a commit to abates-dentsu/RepRapFirmware that referenced this pull request Oct 1, 2021
…lection

Object selection was not functioning properly
@dc42
Copy link
Collaborator

dc42 commented Mar 29, 2022

Unfortunately there was insufficient free flash memory space to include this change in RRF 3.4.0. I will look at it again in RRF 3.5 if we are successful in freeing up more space.

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.

2 participants