Hi,

I have a very selfish request because all this is way beyond my skills : My OBD2 connector in the car does not have 3 bus, it has only one, the High Speed (pin 6/14), but on pin 3/11/12/13 I have the TX +/- and RX +/- cable for the Ethernet connection, plus Ethernet activation on pin 8.  Could it be an option to have also DoIP (Diagnostic over IP) on a future OVMS hardware ?

Didier

Le lundi 9 août 2021, 05 h 03 min 06 s HAE, <rohit@ekraft.asia> a écrit :


Hello Mark,

               Thanks for the comments. Please find the attached responses inline in green.

  1. Please don’t call this "OVMS v4", as that would cause confusion. Our ‘v’ naming is based on processor architecture:

    v1 - original prototype hand-built (PIC18F2680)
    v2 - first production version (PCI18F2685)
    v3 - refined production version (ESP32 WROVER, 16MB flash 4MB SPIRAM)

    Within that we have a .x naming scheme for subversions. The current version is v3.2 and the upcoming 4G module will be v3.3.

    It sounds like you are trying to make a different layout of the upcoming version, so perhaps a fork of v3.3?

    My concern here is to avoid confusion.  Yes this is kind of fork of v3.3 with some additions on v3.2.
  2. SIM7600 sounds ok. That is the direction we are heading as well. If we adopt the version SIM7600G-H then this is global with all regions supported. However all modules on this series are pin to pin so doesn’t matter if we go for region specific.
  3. For ESP32 are you using WROVER module with 16MB flash and 4MB/8MB SPIRAM? Noop. I am planning to use wroom only. Should I switch to wrover instead?
  4. For things like ACC detection, full power control, RGB LED, which GPIO / extended-IO pins are you using? I have used extender i.e MAX7317AEE+. Attached is the reference for esp32 connections.

  1. It doesn’t look like you support the current expansion board option? Noop. I am not using any expansion thing here. Any particular requirement for that?
  2. It seems that you are using a different vehicle connector, so this will be hardwired for Indian MG ZS EV? Noop. Since we can use this for many other vehicles also by changing the connector. In current version the PCB has exposed pads where we need to solder wires to connector.
  3. Note that we removed the LED in v3 (it was in v2) due to power consumption issues with that. There is power control option from hardware side. Only esp32 and accelero module are always on. For other things,  power control is done from GPIO of esp32.
  4. How are you intending to handle firmware? A fork of the current code, or kconfig flags to support your hardware differences? Unfortunately I am not that good on software side . Can modify it slightly by not much. Would require some support on this .

One more thing, I was not able to find the CAN ic in stock so using TCAN334 from TI. Will this work with MCP2515-E_ML?

 

Regards,

Rohit Soni

 

From: OvmsDev <ovmsdev-bounces@lists.openvehicles.com> On Behalf Of Mark Webb-Johnson
Sent: 09 August 2021 01:51 PM
To: OVMS Developers <ovmsdev@lists.openvehicles.com>
Subject: Re: [Ovmsdev] OVMS Hardware 4.0

 

Looks interesting. A few comments:

 

  1. Please don’t call this "OVMS v4", as that would cause confusion. Our ‘v’ naming is based on processor architecture:

    v1 - origjnal prototype hand-built (PIC18F2680)
    v2 - first production version (PCI18F2685)
    v3 - refined production version (ESP32 WROVER, 16MB flash 4MB SPIRAM)

    Within that we have a .x naming scheme for subversions. The current version is v3.2 and the upcoming 4G module will be v3.3.

    It sounds like you are trying to make a different layout of the upcoming version, so perhaps a fork of v3.3?

    My concern here is to avoid confusion.
  2. SIM7600 sounds ok. That is the direction we are heading as well.
  3. For ESP32 are you using WROVER module with 16MB flash and 4MB/8MB SPIRAM?
  4. For things like ACC detection, full power control, RGB LED, which GPIO / extended-IO pins are you using?
  5. It doesn’t look like you support the current expansion board option?
  6. It seems that you are using a different vehicle connector, so this will be hardwired for Indian MG ZS EV?
  7. Note that we removed the LED in v3 (it was in v2) due to power consumption issues with that.
  8. How are you intending to handle firmware? A fork of the current code, or kconfig flags to support your hardware differences?

 

Regards, Mark,



On 9 Aug 2021, at 3:18 PM, <rohit@ekraft.asia> <rohit@ekraft.asia> wrote:

 

Hello OVMS dev’s,

               I am basically hardware designer planning to use the OVMS on my MG ZS EV ( Indian version ). For this I designed the hardware containing 4g module as well as all the components on single PCB.

Have a look on below:

<image002.jpg><image004.jpg>

 

               Top Side                                                                                                        Bottom side

 

The hardware features are as follows:

  1. 4G module with active GPS antenna support ( sim7600 )
  2. ESP32 as main processor ( similar to ovms rev 3)
  3. Sim and sd card in stacked single slot to save space
  4. 3 can bus ports
  5. Battery backup in case need to use this device as security. On board charging
  6. Accelero/ gyro combined low power device
  7. ACC detection in case of supported from vehicle from OBD port
  8. Fully power control of each and every component and low power sleep mode
  9. Input power supply up-to 60 V
  10. RGB  led for status indication

 

The device case would be as below in which OBD connector would be there.

<image007.jpg><image008.jpg>

 

Do let me know if we need to add something so hardware is future ready. 

 

Regards,

Rohit Soni

+91-9660770212

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

 

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev