hi,
I found some of other intepreters here. I suggest that you can categorized to Device::Interpreter and in that category,you can hold all your interpreter families like ELM 322, ELM320 and so on.As you mentioned,ELM323::OBDII is reasonable.
-kulls
Comment on Re: Namespaces and module suggestions again, OBDII
Apparently the ELM327 is only a few weeks old.
Didn't really pick up on it before, but the 320 and 322 are for cars that utilize PWM and VPW respectively. I thought they were previous revisions of the interface.
Looking at the data sheets, seems to confirm that the command set and return values are the same for all (Excluding the 327, which uses CAN and has a lot of other options). So this should work in theory for all of the popular varients.
So maybe OBDII::ELM32X instead? Though it seems like Device should be in there somewhere from a taxonomy point of view.
Plus It needs a Device::SerialPort or Win32::SerialPort or subclass passed to it's constructor. What do you think of "Device::OBDII::ELM32X"