Créer un projet Besoin d'aide ?
  • État du projet
  • Date de publication
Commentaires récents
Thank you sir,  i will follow up you for troubleshooting, i connected 1.5v AA dry cell in input of ICL7135 please find the photo attached out put still overvoltages.  Mean time i will make another fresh circuit follow exchatly posted circuit. 
ESP32 Digital Voltmeter
Gustavo Murta
Gustavo Murta il y a 16 heures
Padakathu ,  The reading is correctt ! You put the ESP32 Voltmeter in over voltage condition.  You can only mesure voltages between +2V and -2V. Read carefully the project.  "Tried to connect 2amp 5v usb power and measure the voltage still in -VCC Appears -3.22 between input terminals pin 9-10 measured near zero 4mv. output at serial monitor showing "Over voltage" For test, connect 1.5V AA battery at input of ESP32 Voltmeter.  
ESP32 Digital Voltmeter
PADAKATHU R RANGASAMY il y a 20 heures
sorry writing mistakes in above mentioned lines ICL7135 pin 01 (-VCC) measured -3.22V ICL7135 pin 02 (Vref) measured 1.000V ICL 7135 pin 11 (+VCC) measured +3.3V  
ESP32 Digital Voltmeter
PADAKATHU R RANGASAMY il y a 21 heures
Thank you so much Gustavo, for helping me to troubleshoot, double checked the circuits and voltages measured at ICL7135 pin 01 (-VCC)  must be -3.22V  ICL7135 pin 02 (Vref) adjust to 1.000V  ICL 7135 pin 11 (+VCC) must be +3.3V  not connect pin 9 (IN LO) to ground  Tried to connect 2amp 5v usb power and measure the voltage still in -VCC Appears -3.22 between input terminals pin 9-10 measured near zero 4mv. output at serial monitor showing "Over voltage" In addition measured with Oscilloscope Clock out at ESP32 pin GPIO2 480KHZ I2C scanner detecting PCF8574  (32, 0X20) Address pulses at SCL 98KZH  ICL7135 BCD out pins binary pulses there tried to replace the "OverVoltage ();" to "PrintVoltage ();" printing  in serial monitor "Voltage = +15.000" only continuously Still facing the same problem display in serial monitor overvoltages Please advice me  If anything possible mistakes i may done.  below attached code i downloaded and outputs  
ESP32 Digital Voltmeter
Thomas Beck
Thomas Beck il y a 1 jour
This project update adds support for OBD2 PID 0x8B (Diesel Aftertreatment Status) which is displayed in the Current Data and Freeze Frame Data menus.Changes: - recompiled all hhgui library variants to get the OBD2-Analyser NG firmware update v1.12.0 / HHGui v3.21 update, especially: - added support for bit-mapped PID 0x8B Diesel Aftertreatment Status   Internally, this PID provides the following data items:   Diesel Particulate Filter (DPF) regeneration status: yes/no   DPF regen type: active/passive   NOx Adsorber regen status: yes/no   NOx Adsorber desulfurization status: yes/no   Normalized trigger for DPF regen: 0 - 100.0 %   Average time between DPF regens: 0 - 65535 minutes   Average distance between DPF regens: 0 - 65535 km - minor changes of title font and menu fonts: shorter underscore to reduce the space needed by PID acronyms - fixed missing character 'S' in PID acronym names of long term secondary oxygen sensor fuel trim PIDs LTO2FTx -> LTSO2FTx By the way, PID acronyms have been changed in more recent versions of the SAE J1979-DA specification. The OBD2-Analyser NG firmware still uses the old PID acronyms since these are generally shorter. Most of them are only 8 characters long which better fits with the small LC display (132 x 32). The compressed PID text descriptions are generated with the text compressor which I have published in the comments section. If you run out of Flash memory in your own microcontroller project which uses texts, you might want to try this. Details are published here: German: French: Detailed installation instructions for Arduino M0/M0 Pro/Zero, Due, MEGA/MEGA2560, UNO and Elektor UNO R4 covering hardware, software and wiring are given in file installation.txt. This file is covering installation with the Arduino IDE 1.8.5. If you already have built the project for IDE 1.8.5 you actually just need to do the follwing steps: 1. if you have changed the file HHGui/Obd2ModuleCfg.h, backup this file 2. replace the old HHGui Arduino project folder with the new one from the archive 3. if step 1 was relevant, copy the Obd2ModuleCfg.h backup file to the new HHGui folder 4. rebuild the project with IDE 1.8.5 In the meantime I have compiled the software with Arduino IDE 1.8.7 which uses avr-gcc 5.4.0 for the AVR based boards UNO and MEGA. The toolchain used by the IDE was updated in the IDE 1.8.6 release. This does not work together with the HHGui libraries for UNO and MEGA built with avr-gcc 4.9.2 of IDE 1.8.5. The reason is a different format used for link time optimization (LTO). Compilation stops with an error message "lto1.exe: fatal error: bytecode stream generated with LTO version 3.0 instead of the expected 4.1". Elektor UNO R4 is unaffected since this uses avr-gcc 4.9.2 independly from the IDE version. Actually, LTO is just needed for the UNO and especially the Elektor UNO R4 where the firmware without LTO would not fit into the small Flash memory. Therefore, if you want to build the software for UNO R3 or MEGA1280/2560 under IDE 1.8.6 or IDE 1.8.7 or IDE 1.8.8, you need HHGui libraries built with avr-gcc 5.4.0. In this case, copy the relevant library from the archive to the HHGui project folder. UNO R3 + Pi-OBD module: hhguilib_agv_atmega328x.a UNO R3 + DXM module: hhguilib_dxm_atmega328x.a MEGA1280: libhhgui_mega1280.a MEGA2560: libhhgui_mega2560.a Note: if you have replaced an UNO R3 library and you later want to build the project for Elektor UNO R4, you must undo this change. With this update UNO R3 and especially the Elektor UNO R4 almost run out of Flash memory. If you have adapted the software to another display which needs more Flash memory for its driver, you can try different versions of the Arduino AVR core to get it fit. For the Elektor UNO R4, integrating the UNO R4 as variant into the Arduino UNO R3, so that the gcc 5.4.0 compiler is used, helps.
OBD2 for Arduino