RE: Device Support for I2C and GPIO

[Mark Rivers <rivers@cars.uchicago.edu>]

Your derived method's connect function should be called.  Can you send your code?  I'll take a look and see if I can spot anything wrong.

Mark

________________________________________
From: Florian Feldbauer [florian@ep1.ruhr-uni-bochum.de]
Sent: Tuesday, January 12, 2016 4:38 AM
To: Mark Rivers; 'Pete Jemian'; tech-talk@aps.anl.gov
Subject: Re: Device Support for I2C and GPIO

Hey Marc, hey all!

unfortunately, I did not had the time to write and test the I2C device
support last year.
But now I have the time and I'm currently facing a problem:
My I2C device support is written as a class derived from the asynPortDriver,
reimplementing writeOctet, readOctet, connect and disconnect.

When calling the ctor of asynPortDriver I set the "autoConnect" flag to 1,
but the connect function of my class is never called, thus the file
handle for the
I2C interface is never opened.

Is there something I'm missing?
I thought autoConnect means that the connect function is automatically
called?

Cheers
Florian

On 11/25/2015 06:24 PM, Mark Rivers wrote:
> The I2C asyn driver could be considered for going into asyn itself, since it is conceptually similar to the serial, IP, GPIB, USBTMC, and VXI11 drivers.
>
> Note that "ip" is really not for software related to Industry Pack modules any more.   Most industry pack drivers now have their own modules (ip330, ipUnidig, dac128V, softGlue, ipac for ipOctal).  "ip" is really now software for asynOctet devices (serial, GPIB, TCP) that do not have another home like "vac" and "delayGen".  "ip" is no longer a good name for it.
>
> Similarly "std" was originally the home for a lot "standard" beamline control stuff.  Most of this has now been moved to other modules (calc, busy, optics, sscan), so "std" is more like "misc" now.
>
> Mark
>
>
> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Pete Jemian
> Sent: Wednesday, November 25, 2015 11:10 AM
> To: tech-talk@aps.anl.gov
> Subject: Re: Device Support for I2C and GPIO
>
> Michael describes a good procedure for completely new functionality.
> New modules should provide support distinct from other modules.
>
> This _might_ have a place in one of the existing synApps modules.  This
> is not "ip" functionality (related to Industry Pack modules), not
> "calc", not "optics", perhaps "std" is the catchall module for new
> synApps support?
>
> On 11/25/2015 9:08 AM, Michael Davidsaver wrote:
>> On 11/25/2015 03:08 AM, Florian Feldbauer wrote:
>>> I would like to upload the sources to github. Is it possible to upload
>>> it to the "epics-modules" group?
>> At this point there isn't any established criteria for when/if
>> repositories in this group are created.
>> It would suggest starting with a repository under your own account (what
>> I do), then think about moving to epics-modules at some later date,
>> which isn't difficult.
>>
>> That said, if you want to go straight to epics-modules I'm inclined to
>> just add it.  Let me know if you want to do this and I'll do this in a
>> day or so, assuming no one objects.  Of course, first you need to solve
>> the hard problem, the repository name ;)
>>
>>
>> Michael
>>

--
----------------------------------------
| Dr. Florian Feldbauer                |
|                                      |
| Helmholtz-Institut Mainz /           |
| Johannes Gutenberg-Universität Mainz |
| Johann-Joachim-Becher-Weg 36         |
| D-55128 Mainz                        |
|                                      |
| Office: SB1 / 00-213                 |
| Phone:  (+49)6131 / 39-29605         |
----------------------------------------