methods
1 GW
Looking to share information around the following:
USB-to-CAN compact
1.01.0087.xxxxx
1.01.0088.xxxxx
AKA V1.5 and V1.6
Have tested compatibility around:
* Clone Boxes claiming compatibility
* USB-to-CAN V2 compact
Have found:
* Using the tools I have access to... that the V2 and Clones can brick (temporarily?) the Sevcon into a mode where it has a solid green LED with no flicker in a situation where you enter bootloader mode and attempt to flash the DLD. No CAN response. No CAN traffic. Pending testing.
EDIT: Testing has shown that the clone devices are compatible with both new and old versions of DVT. Clones some times lock up and require a USB physical disconnect cycle. Clone devices may run slower on bulk data movement than the original IXXAT (unconfirmed) or otherwise increase probability of Green-Bricking
* Clones and V2 work fine for flashing dcf files and basic monitoring (SO IF YOU ARE A HOBBYIST... CLONE OR V2 SHOULD MEET YOUR REQUIREMENTS IN MOST CASES)
* I need to be able to flash DLD files because I have advanced use cases
Key Words:
Zero Motorcycles, Sevcon Programming, Sevcon DVT, V1.5, V1.6, V2, ixxat, dld, dcf, V4, V3, V2, V1 drivers clone, ebay clone, Chinese clone
Research pointed to:
* 10uW lurk claimed a license key is required to unlock V2 compatibity with DVT. Unconfirmed. confirmed
Best Guess:
* V1 had undocumented capabilities that were exploited by Sevcon leading to legacy issues.
* Forcing old drivers (by cleaning all new ixxat drivers off of the machine) MAY allow one to emulate V1.5 / V1.6 capabilities - untested.
* Sevcon claims to be burdened by customer support issues... yet they have a clear path forward on eliminating said issues.
All incorrect
Options:
* If I had paid engineering hours I would either approach Sevcon with an argument to resolve or try every permutation of establishing a sustainable path forward as V1.5 and V1.6 have gone into extinction. It is not acceptable to need legacy parts to maintain systems in the field moving forward.
I had engineering hours and through epicly obnoxious trial and error with both old and new DVT versions we have achieved precision such that we can predict results.
-methods
New Terminology:
Black-Brick = Sevcon in Bootloader mode (solution, get out of bootloader)
Green-Brick = DLD disrupted during transfer, use command line to force into bootloader at next restart, flash DLD
Where black means no LED
Where Green means solid LED but controller does not work or respond
Where blinking LED means all good but with errors
Where solid LED with comms means you are golden
USB-to-CAN compact
1.01.0087.xxxxx
1.01.0088.xxxxx
AKA V1.5 and V1.6
Have tested compatibility around:
* Clone Boxes claiming compatibility
* USB-to-CAN V2 compact
Have found:
* Using the tools I have access to... that the V2 and Clones can brick (temporarily?) the Sevcon into a mode where it has a solid green LED with no flicker in a situation where you enter bootloader mode and attempt to flash the DLD. No CAN response. No CAN traffic. Pending testing.
EDIT: Testing has shown that the clone devices are compatible with both new and old versions of DVT. Clones some times lock up and require a USB physical disconnect cycle. Clone devices may run slower on bulk data movement than the original IXXAT (unconfirmed) or otherwise increase probability of Green-Bricking
* Clones and V2 work fine for flashing dcf files and basic monitoring (SO IF YOU ARE A HOBBYIST... CLONE OR V2 SHOULD MEET YOUR REQUIREMENTS IN MOST CASES)
* I need to be able to flash DLD files because I have advanced use cases
Key Words:
Zero Motorcycles, Sevcon Programming, Sevcon DVT, V1.5, V1.6, V2, ixxat, dld, dcf, V4, V3, V2, V1 drivers clone, ebay clone, Chinese clone
Research pointed to:
* 10uW lurk claimed a license key is required to unlock V2 compatibity with DVT. Unconfirmed. confirmed
Best Guess:
* V1 had undocumented capabilities that were exploited by Sevcon leading to legacy issues.
* Forcing old drivers (by cleaning all new ixxat drivers off of the machine) MAY allow one to emulate V1.5 / V1.6 capabilities - untested.
* Sevcon claims to be burdened by customer support issues... yet they have a clear path forward on eliminating said issues.
All incorrect
Options:
* If I had paid engineering hours I would either approach Sevcon with an argument to resolve or try every permutation of establishing a sustainable path forward as V1.5 and V1.6 have gone into extinction. It is not acceptable to need legacy parts to maintain systems in the field moving forward.
I had engineering hours and through epicly obnoxious trial and error with both old and new DVT versions we have achieved precision such that we can predict results.
-methods
New Terminology:
Black-Brick = Sevcon in Bootloader mode (solution, get out of bootloader)
Green-Brick = DLD disrupted during transfer, use command line to force into bootloader at next restart, flash DLD
Where black means no LED
Where Green means solid LED but controller does not work or respond
Where blinking LED means all good but with errors
Where solid LED with comms means you are golden