[Ovmsdev] OVMS v3.3 hardware
mark at webb-johnson.net
Tue Oct 12 19:38:18 HKT 2021
First ‘final’ v3.3 sample received (the one that also went to the certification lab):
rst:0xc (SW_CPU_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
mode:DIO, clock div:2
I (1062) psram: This chip is ESP32-D0WD
I (1062) spiram: Found 64MBit SPI RAM device
I (1062) spiram: SPI RAM mode: flash 40m sram 40m
I (1065) spiram: PSRAM initialized, cache is in low/high (2-core) mode.
I (1072) cpu_start: Pro cpu up.
I (1076) cpu_start: Application information:
I (1081) cpu_start: Project name: ovms3
I (1086) cpu_start: App version: 3.2.016-393-g07db2f8d
I (1092) cpu_start: Compile time: Sep 16 2021 21:09:48
I (1099) cpu_start: ELF file SHA256: 8aa1db50ae1ea15d...
I (1105) cpu_start: ESP-IDF: v3.3.4-848-g1ff5e24b1
I (1111) cpu_start: Starting app cpu, entry point is 0x40081720
I (1103) cpu_start: App cpu up.
I (1989) spiram: SPI SRAM memory test OK
I (1989) heap_init: Initializing. RAM available for dynamic allocation:
I (1989) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (1996) heap_init: At 3FFBE250 len 00021DB0 (135 KiB): DRAM
I (2002) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (2008) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (2015) heap_init: At 4009D5A4 len 00002A5C (10 KiB): IRAM
I (2021) cpu_start: Pro cpu start user code
I (2026) spiram: Adding pool of 4096K of external SPI memory to heap allocator
Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3
OVMS# module memory
Free 8-bit 103580/273840, 32-bit 6440/10796, SPIRAM 3460832/4194252
Version: 3.2.016-393-g07db2f8d/factory/main (build idf v3.3.4-848-g1ff5e24b1 Sep 16 2021 21:12:48)
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3
$ esptool.py --port /dev/tty.usbserial-0001 --baud 115200 chip_id
Serial port /dev/tty.usbserial-0001
Detecting chip type... ESP32
Chip is ESP32D0WDQ5 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
Michael should be very happy with that @ESP32D0WDQ5 (revision 3).
I’m working through the other tests now, but so far so good.
> On 14 Sep 2021, at 3:01 PM, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
> Progress update…
> I’ve completed the basic support for plugin modem drivers and SIM7600 in the for-v3.3 branch, and it seems stable on my bench and car (although I never saw many problems before with this). I would still appreciate it if others could test and feedback any crashes they get. You can get the update OTA from api.openvehicles.com <http://api.openvehicles.com/> by setting tag ‘pre’.
> We’ve also completed the testing of the hardware. The DTR low-power control option seems to be working well (but will require firmware support later). The ‘final’ list of hardware changes are as follows:
> Main Board:
> Silkscreen label “OVMS V3.3” (with date of production batch)
> Change to improved internal antenna cables for GSM and GPS
> Strengthen soldering on micro USB connector
> Strengthen soldering on power supply capacitors
> WROVER module to use revision 3 ESP32
> Add 0.1uF capacitor to 12v measuring voltage divider ADC input (https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/adc.html#minimizing-noise <https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/adc.html#minimizing-noise>)
> Modem Board:
> Silkscreen label “OVMS MDM V3.3” (with date of production batch)
> Add support for SIM7600 module
> Fixed DTR support
> Improve/check voltage regulator and capacitor protection
> Reduce brightness of blue LED by at least 50%
> Airplane mode pin fix (working ok now, but safer to pull up/down properly)
> Confirm PWRKEY circuit tuning
> Product label - just one label with CE and FCC certification for global use
> We are now producing a few final samples of the above to go to the certification labs for CE, FCC, and ROHS testing later this month. We hope that certification will take 6 to 8 weeks and be complete around the end of November. Once that is done, we should be able to go to full production in time for Christmas. Pricing will be confirmed early December, but likely more expensive than v3.2 due to the extra cost for SIM7600G and certification fees.
> Stock of existing SIM5360 modules are as follows:
> EU kits; in stock at open energy monitor (but selling out fast and likely to be unavailable soon).
> US kits; in stock at Medlock, Fasttech, and Open Vehicles (HK).
> Regards, Mark
>> On 30 Aug 2021, at 2:03 PM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>> I now have two prototypes of the 4G modem using SIM7600G R2 chip for OVMS v3.
>> One is for my own work, but willing to send the other free to a volunteer developer willing to spend time working with me to develop and test this new option. Obviously looking for someone who has spent some time on the OVMS code base, with a good history of contributions to the project and a willingness to work on improving the cellular modem driver.
>> Any volunteers? Please eMail me directly (mark at openvehicles.com <mailto:mark at openvehicles.com>).
>> Regards, Mark.
>>> On 17 Aug 2021, at 1:30 PM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>>> For the 4G modem options we need to go through FCC, CE, and ROHS certification. Minimising/eliminating the changes to the main board simplifies this (and brings down the exorbitant costs) but if there is anything urgent / necessary, now is the time to do it.
>>> The goal here is to maintain 100% compatibility with existing OVMS main boards, to keep this is a simple and relatively cheap upgrade of the modem board.
>>> So far, I have come up with this minimal list:
>>> Main board v3.3: Improve soldering of micro USB port. Bigger solder pads, and more solder to secure it better.
>>> Modem board v1.3: Add support for SIM7600 module.
>>> Modem board v1.3: Fix support for DTR sleep/awake support.
>>> Is there anything else required for this update?
>>> Regards, Mark.
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev