 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : I2C2
| Author | Message | ||||
palcal Guru  Joined: 12/10/2011 Location: AustraliaPosts: 1997 |
Trying to use I2C2 on a 100 pinner with V4.7b37 Using the command I2C2 OPEN 100,1000 I get an error UNKNOWN COMMAND. Am I using the correct syntax, I can't find any reference to I2C2 anywhere in the manual except on the chip pinout. Paul "It is better to be ignorant and ask a stupid question than to be plain Stupid and not ask at all" |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2948 |
Exactly the issue I had yesterday. I emailed Grogster to see if he knew the latest as even in the change logs it is not mentioned. I did see a post from Geoff explaining that I2C2 should be in the next release but I ended up using the first I2C channel for now. Am emailing Geoff to find out current status. WW |
||||
Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3303 |
The story is that with the development of the I2C CFunction (included in the 5.0 distribution for the MX170) the need for the second I2C channel has largely gone away - with the CFunction you can have as many I2C channels as you want. A second factor is that the I2C code needs to be rewritten to support a second channel (it was not written by me) and I have run out of time to do this. So, in summary, there will not be an I2C2 but you can use a CFunction instead. Geoff P.S The I2C CFunction refered to above will work fine on a 100 pinner with V4.7b37 Geoff Graham - http://geoffg.net |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2948 |
Thanks for clarifying this 
Will the v5.0 CFunction work as it is on both the 64pin & 100pin MM+'s? I have not looked at the code yet so sorry if this is a silly question. WW |
||||
| Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3303 |
Yes it will. BTW I edited my post while you were typing your question. Geoff Graham - http://geoffg.net |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2948 |
@Geoffg Can I recommend that the references to the I2C2 pins (in the 64pin & 100pin pinout diagrams) be removed from the User Manual. This will avoid any confusion to others in the future.
Will try the CFunction on 100pinner later and report any issues . . . . WW |
||||
| palcal Guru Joined: 12/10/2011 Location: AustraliaPosts: 1997 |
A bit of a bummer. I designed a board and had them made using both I2C channels. Will have to cut tracks an hard wire. Paul. "It is better to be ignorant and ask a stupid question than to be plain Stupid and not ask at all" |
||||
| viscomjim Guru Joined: 08/01/2014 Location: United StatesPosts: 925 |
Palcal, can you not use those pins with the Cfunction and make your project work? |
||||
| palcal Guru Joined: 12/10/2011 Location: AustraliaPosts: 1997 |
It,s OK, the device connected to I2C2 is on short flying leads so I moved them directly to the I2C pins and all is working. Paul. "It is better to be ignorant and ask a stupid question than to be plain Stupid and not ask at all" |
||||
| Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3303 |
With the CFunction you can select the I/O pins. So why not select the pins that were going to be used by I2C2? Geoff Graham - http://geoffg.net |
||||
| palcal Guru Joined: 12/10/2011 Location: AustraliaPosts: 1997 |
Thanks for that Geoff, I haven't looked at the CFunction yet but will do that. Thanks. Paul. "It is better to be ignorant and ask a stupid question than to be plain Stupid and not ask at all" |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
