Questions about code set

Forums:

Hi PiBorg:

Two questions:

1 - could you please check your LinkedIn messages? I've sent you one and included instructions for what I think would be a better way to communicate rather than ping-pong over an open forum.

2 - (assuming you don't read your LinkedIn messages) I'm examining the code "UltraBorg.py", and I see that you have GetWithRetry and SetWithRetry where you've created a couple of functions that make up to five passes then gives up. My question - before I go through the onerous PITA of migrating this code to .NET - is ... why? Why does it need to do that?

I haven't received my UltraBorg yet to discover for myself. (It'll be here Monday.)

Thanks.
-J

piborg's picture

Sorry about that, most of the messages I get on LinkedIn are from recruiters so I do not check them very often. I have just read your message and sent a response :)

The repeated retries are probably not really necessary anymore. The GetWithRetry / SetWithRetry code came about for two reasons:

  1. There was a timing issue with the I2C on earlier releases of Raspbian that was causing occasional bad reads. These bad values would then mess up the position values for the servo when trying to move.
  2. We wanted to have the tuning GUI check that the value written was saved correctly. The SetWithRetry function was a way to code the write - read - check sequence once rather than code it for each setting written to EEPROM.
Subscribe to Comments for "Questions about code set"