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

IO library updates #5044

Merged
merged 3 commits into from May 4, 2017

Conversation

Projects
None yet
3 participants
@gohai
Contributor

gohai commented May 4, 2017

No description provided.

@benfry benfry merged commit 4bba9f2 into processing:master May 4, 2017

@gohai gohai deleted the gohai:io-fixes branch May 4, 2017

@theseanzo

This comment has been minimized.

Show comment
Hide comment
@theseanzo

theseanzo Dec 8, 2017

I think, since this was changed, i2c communication has stopped working. Not sure, but my raspberry pis with the latest processing no longer communicate over i2c whereas my old pis on an unupdated processing work

theseanzo commented on b5d9fdf Dec 8, 2017

I think, since this was changed, i2c communication has stopped working. Not sure, but my raspberry pis with the latest processing no longer communicate over i2c whereas my old pis on an unupdated processing work

This comment has been minimized.

Show comment
Hide comment
@gohai

gohai Dec 8, 2017

Contributor

@theseanzo This change shouldn't be able to influence the I2C code in any way, since it is not making use of the GPIO class in any way.

What symptoms are you seeing when it doesn't work? Does the code throw exceptions or you just suspect the transmission failed?

When you say "old Pis" - is your working system on a different hardware than the one that doesn't work?

Contributor

gohai replied Dec 8, 2017

@theseanzo This change shouldn't be able to influence the I2C code in any way, since it is not making use of the GPIO class in any way.

What symptoms are you seeing when it doesn't work? Does the code throw exceptions or you just suspect the transmission failed?

When you say "old Pis" - is your working system on a different hardware than the one that doesn't work?

This comment has been minimized.

Show comment
Hide comment
@theseanzo

theseanzo Dec 8, 2017

theseanzo replied Dec 8, 2017

This comment has been minimized.

Show comment
Hide comment
@gohai

gohai Dec 8, 2017

Contributor

@theseanzo What's the symptom when you say "no longer works"? Were your "previous Pis" also Pi 3 models?

Contributor

gohai replied Dec 8, 2017

@theseanzo What's the symptom when you say "no longer works"? Were your "previous Pis" also Pi 3 models?

This comment has been minimized.

Show comment
Hide comment
@theseanzo

theseanzo Dec 8, 2017

theseanzo replied Dec 8, 2017

This comment has been minimized.

Show comment
Hide comment
@gohai

gohai Dec 8, 2017

Contributor

@theseanzo What's the exception message?

Contributor

gohai replied Dec 8, 2017

@theseanzo What's the exception message?

This comment has been minimized.

Show comment
Hide comment
@theseanzo

theseanzo Dec 8, 2017

theseanzo replied Dec 8, 2017

This comment has been minimized.

Show comment
Hide comment
@theseanzo

theseanzo Dec 9, 2017

theseanzo replied Dec 9, 2017

This comment has been minimized.

Show comment
Hide comment
@gohai

gohai Dec 19, 2017

Contributor

@theseanzo Sorry for the late reply. I just tried the I2CScreen example on the latest Processing running on the latest Raspbian, and this worked just fine.

So I am guessing that this is has something to do with your setup... a couple of suggestions:

  • you could try to swap the microSD card between your Raspberry Pi 2 (working) and 3 (not working) and see if this does the trick?
  • you could try to download our Processing Raspbian-remix and test it there

In any case, this should not have anything to do with this particular commit.

Contributor

gohai replied Dec 19, 2017

@theseanzo Sorry for the late reply. I just tried the I2CScreen example on the latest Processing running on the latest Raspbian, and this worked just fine.

So I am guessing that this is has something to do with your setup... a couple of suggestions:

  • you could try to swap the microSD card between your Raspberry Pi 2 (working) and 3 (not working) and see if this does the trick?
  • you could try to download our Processing Raspbian-remix and test it there

In any case, this should not have anything to do with this particular commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment