The driver constructor looks right, that makes your drive accept the provides line with rfid in it.
The name and plugin parameters in your config file are probably wrong. The plugin should be the name of the library that your plugin is compiled as, this needs to be in your library easrch path as well (LD_LIBRARY_PATH).

the name is the name you give to player in your drivers register function, this should be something specific to your driver such as rfid70.

Toby

On 31/08/2007, Brad Towle <btowleii@hotmail.com> wrote:

I am trying to code a custom RFID driver, however I always get confused when
I have to make the .cfg files.

I am getting the following errors AFTER player successfully initialize my
driver.

error   : Couldn't find driver "RFID"
error   : failed to parse config file simple.cfg


As far as I can see the mistake is either here in my config file:

driver(
        name "RFID"
        plugin "RFID"
        provides ["6665:rfid:0"]
        )

Or here in my driver code, I am not sure what the flag for RFID is?
rfid70Driver::rfid70Driver(ConfigFile * cf, int section):Driver
(cf,section,false,PLAYER_MSGQUEUE_DEFAULT_MAXLEN,PLAYER_RFID_CODE)

/\

L Is this right?


Any help would be appreciated.  My driver is being compiled to a file called
RFID.so and it is in the working directory.

Thanks
Brad Towle
--
View this message in context: http://www.nabble.com/RFID-driver-syntax-tf4357300.html#a12417533
Sent from the playerstage-users mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Playerstage-users mailing list
Playerstage-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/playerstage-users



--
This email is intended for the addressee only and may contain privileged and/or confidential information