* DVT/Helper/CAN/Display Settings can be used to view and modify settings (be sure to set your node address correctly)

* If you know your index and sub index virtually any setting in the controller DCF can be modified.

Things I have yet to confirm:

* The unit can take a controller in and out of PreOp

* The unit requires Sevcon support to change the logo and splash screen

* The DCF can be saved off and manually modified (did this save yesterday, took forever, today I will poke around in it)

* Modified profiles (DCF) can be loaded back into the unit

* Unit is highly programmable in terms of CANopen behavior.

* Unit can be tailored to match customer standard setup... by hiding unneeded values... and exposing others. This will take many hours to get right, but once done, should be as quick as any other DCF flash.

* ThunderStruck-EV has posted quick start and programming manuals. These manuals are enough... but forget to tell you the tip above about accessing via DVT.

* There are 4 levels of programming access that can be applied via a hexadecimal code. These levels affect what your customer can and can not change. These expose things like Back Door and Personalities. THIS IS VERY DANGEROUS.... PEOPLE WILL FUBAR THEIR SYSTEMS... PROCEED WITH CAUTION. DO NOT FIDDLE SETTINGS!!!

-methods

Increasing battery voltage and controller current limit will result in a non linear experience

If you are not using DVT you may need to request the CANopen network to enter pre-operational
before all objects can be written to.

To enter pre-operational, write ‘1’ to 2800h on the master node.
To restore the CANopen network to operational, write ‘0’ to 2800h.

The controller may refuse to enter pre-operational if part of the system is active: for example, if the
vehicle is being driven. The request is logged in the EEPROM however, so if power is recycled the
system won’t enter operational and remains in pre-operational after powering up.

The NMT state can be read at 5110h where 05 = operational and 7F = pre-operational.

Here is data extracted from the DCF file on the Clearview itself... (i.e. this is stuff you can tootle over to and adjust from the buttons ... since this will be your CAN broadcaster)

Enter, navigate to Back Door
You can then select your device... either the display or the Master

At this point you decide whether you are changing settings directly on the Sevcon... or in the Display.
Hrmmm

We know if we change it in the Sevcon it will happen.
We know if the display broadcasts the above it will haveppen.
We dont know if the display will automatically broadcast the change.

So we try it

We set Device to DIsplay
We step into Index

I am going to go look at index 2800 (as dictated above by findings in the DCF)

Sub 9 shows the value of 00h (remember that in binary and hex we start counting at 0... not 1... so if there is only one it is sub0 and if there are 5 it counts up to 4 -> source of "off by one errors")

That should correspond with Operational... (checking with DVT...)
Hrm... DVT says its in Pre-Op

Ok... That did not work.
It was marked as READ WRITE as well... strange.

So now we will set to Master and fiddle the bits.
Listening for a loud click
Watching for smoke, sparks, runaway motors... dead kids... ghosts...

So... make sure you back out completely
Try a power cycle
At my first try... STALE DATA lead me astray.

** This is a huge problem with Sevcon tools.... STALE DATA **

Anyhow... after sprinkling some "fresh" on the data I see that the master now reads 0x01
Perfect.

Wait for it...

Wait for it...

BAM
Works.

Oh yea...
Now hood-rats in the ghetto can throw their Sevcon into Operational... Picturing crotchety old men in golf carts with Humvee plastics... and San Jose State kids with ridiculous go-karts...

SO... what you need to be a super hero is:

1) Known good DCF for your controller... so you know where stuff is
2) ClearView with level 4 access
3) No ACTUAL problems in your system (some changes kick you into Pre-Op and some changes can not be made while in Op)

To go back into Pre-Op... write 0x2800 with a 0x01

So Simpo.

-methods

Increasing battery voltage and controller current limit will result in a non linear experience