[Ovmsdev] OVMS v3 getting started

[Edward Cheeseman]

Small update. A reboot was all that was required to get the CP2102 driver going, and the EEPROM python script sees it. Getting the script to go required specifying the specific python2.7 instance (of the three and counting I have managed to install over the years).

> On 26/09/2017, at 8:40 PM, Edward Cheeseman <cheesemanedward at gmail.com> wrote:
> 
> CP2102 is US$1.33 one off from Digikey.
> Must be cheaper still the closer you get to China.
> 
> It just so happens that a USB-CAN converter I bought off aliexpress a while back has a CP2102 and STM32. I wasn’t so interested in their software, just the USB connected micro with CAN attached.
> I paid NZ$24 for it shipped. Store was "Electronic products concentrated shop"
> 
> In the last couple of days I tried to get it going, using the latest OSX driver. I didn’t get a crash, but I didn’t get a tty port either (so, not going yet)
> I might try the old driver and see if that goes.
> 
> If it is of interest, I found an old project to burn the CP2102 EEPROM from *nix here: http://cp210x-program.sourceforge.net/ <http://cp210x-program.sourceforge.net/>
> 
> <Image-1.jpg>
> 
> 
>> On 26/09/2017, at 6:30 PM, HONDA S-2000 <s2000 at audiobanshee.com <mailto:s2000 at audiobanshee.com>> wrote:
>> 
>> I'm very surprised that a driver must be installed. In my experience, most hardware implements the USB Communications Device Class standard, and therefore does not need a driver with OSX. Does anyone know why Silicon Labs didn't just implement the standard CDC protocols?
>> 
>> I assumed that the ESP32 processor would have a USB peripheral that would host the protocol, and therefore the OVMS v3 firmware would be in control. I guess I didn't look closely enough.
>> 
>> What does the CP2102 cost in relation to something like a PIC with USB? Sorry for the question.
>> 
>> Brian
>> 
>> 
>> On Sep 24, 2017, at 11:42 PM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>>> 	• The Silicon Labs driver for OSX seems pretty flaky. Linux seems much better, and I haven’t tried Windows. On OSX, I had horrendous problems with the v5 drivers crashing my whole machine (Sierra 10.12). In the installation package, there is a “Legacy MacVCP Driver” directory containing the older 4.11.2 version - using that older version at least works without crashes, but has one known issue. If you ‘make monitor’ and are in the console to the board, then unplug the board, you get left with a /dev.tty.SLAB* device hanging around that messes up that one USB port and future ‘make monitor’ connections. Workaround is to power off the USB hub, and then everything cleans out nicely. If you are directly connected to your MAC’s USB port, then you seem to need to reboot the whole machine to fix the issue. Getting used to being careful to disconnect from the terminal before unplugging (or simply not unplugging - which was happening a lot when I was working on power optimisation, sleep modes, and external 12V power).
>>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> 
> Edward Cheeseman
> Electrical Engineer
> cheesemanedward at gmail.com <mailto:cheesemanedward at gmail.com>
> 

Edward Cheeseman
Electrical Engineer
cheesemanedward at gmail.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170926/fab1f6b5/attachment.htm>