AxelG

lol, doing the same with my 2012 Hemi Charger....

Dave:

Thanks for the reply.  We did, and actually still are considering that option. Longer term we want to use the larger 100 pin STM chip to take advantage of extra IO.

We also wanted the first generation to tap into SPI3 for the onboard SD card: but I can always mount the SD on SPI1 with ND2.

One factor is having a real-time CAN bus capturing OBD data.  Still have not decided on the best approach; but it would be nice not having to add a lot of hardware to do that.

Cost is not the only factor; total size is also a design factor, which is why we jettisoned the Ethernet.  There are several add-on devices needed to fit into a total footprint < 3" X 3"

As always, thanks for the insight!

I have an extra board;happy to send it along... Just PM me.

Thanks, I saw your reply in the other thread.  I decided to spin up a separate VM for gen2 development work.  I'll suck it up until WinUSB drivers are available for gen 2     (No pressure....)

Honestly, thanks for all you do in support of this platform.  It's really appreciated.

All of my ND and ND+ gen 1 and gen 2 are flashed to the latest firmware and everything running under 4.2 NETMF.

ND gen 1: 4.2.0.1

ND+ gen 1 4.2.0.1

ND+ gen 2 4.2.2.2

All the gen 1s are running WINUSB and gen 2 MFUSB on the latest  VM Player 5.0 Win7 ultimate 64 bit.

I can get all my gen 1 running OK together.  I have to reconnect them often in order to deploy and get into debug, but it is workable.

For the most part when running the gen 2 alone, deploying and debugging works OK.  If the gen 2 stops responding and needs to be disconnected; I will 100% of the time get a BSOD.  (It's not always fun having the ND+2 act as a hardware reset button in the middle of coding a project )