Elbilforum.no - driftet av Norsk elbilforening
Bilmerker => Tidlige elbiler: Think => "Nye" TH!NK City produsert fra 2008 - 2012 => Emne startet av: elektrolux på fredag 17. februar 2012, klokken 12:21
Har undersøkt litt om Lithium batteriet på Nye Thinken, og lagt inn info her:
http://www.elbil.no/wiki/Ny-Think:Revers_engineering#12V_batteriet (http://www.elbil.no/wiki/Ny-Think:Revers_engineering#12V_batteriet)
Cellene er individuelt monitorert på temperatur og spenning.
For Nicometer hadde det vært greit å lese av høyeste og laveste cellespenning, og temperatur, samt strøm, og Ahr.
Bra!
Com tool 2.11?
http://www.youtube.com/watch?v=jUiQqM4RWTM
Very nice!
This is obviously a Sodium battery. Will it work also on Lithium battery? Will there be high/low cell voltage?
When can we bye this?
Dette ser virkelig bra ut :D
Bruker du vanlig PC med bluetooth-overføring fra OBD-stikket?
Tack!
This is done with duinomite maxi board.
https://www.olimex.com/Products/Duino/Duinomite/_resources/DuinoMite-UM-1-03.pdf (https://www.olimex.com/Products/Duino/Duinomite/_resources/DuinoMite-UM-1-03.pdf)
Currently connected to a huge screen. I have ordered a foldable 4.3" screen and will try with it as soon as I get it.
I do not plan to sell this. I will publish the source code and instructions on how to make the device. There are far too many options/variations that I can cover in a product.
Drive screen with economy and avg. economy
And a new charge screen with time to 80% estimation:
http://www.youtube.com/watch?v=YHa7B_TKABg
Just mounted the new screen on the dash and did a short test drive with it.
Here is a short video of the test.
http://www.youtube.com/watch?v=qGLrYa-sBYk
The monitor is ok, but there is a black margin to the left, and I don't think I can change that without recompiling the duinomite firmware.
The Drive section shows momentary economy (E), this trip economy (T) and all (A). The trip and all show the same thing now.
I think the user interface is needs lots and lots of work.
Any ideas? Keep in mind that there is no color with the duinomite.
I was thinking of making the numbers of one parameter per section much bigger and easier to see. For the Drive section I was thinking it would be the speed... and for the battery section it would be the power.
The "Mains" section - maybe the current power?
And the charging section would be time to full, or 80%.
Also if a parameter goes beyond a certain value it can be made inverse - so the text is black and the background is light - so it will be more noticable.
Again, ideas?
Looks great!
Any ideas? Well, I'd like to see high and low cell voltage. Maybe only possible on Lithium battery?
Android screen via blue tooth...
My only new Think is in non running condition after beeing returned from repair in Holland.
Thanks for ideas - I will look in to it.
In the meantime, some improvement in user interface.
I also measured consumption - the duinomite takes approx 80mA@14V (1.12W), while the screen takes 120mA@14V (1.7W)
two photos comparing a 4.3" wide screen and 3.5" 4:3 screen
the widescreen seems more readable, and the black margins appear even on the 3.5" screen.
I have published the source code for the A306 nikometer.
https://sites.google.com/site/theevmonitor/think-ev-monitor/download (https://sites.google.com/site/theevmonitor/think-ev-monitor/download)
Let's see who is going to use it first.
SitatTack!
This is done with duinomite maxi board.
https://www.olimex.com/Products/Duino/Duinomite/_resources/DuinoMite-UM-1-03.pdf
Currently connected to a huge screen. I have ordered a foldable 4.3" screen and will try with it as soon as I get it.
I do not plan to sell this. I will publish the source code and instructions on how to make the device. There are far too many options/variations that I can cover in a product.
According to the User manual in the link above there is no such board, however there is a DuinoMite-Mega. Is that the appropriate board to use ?
Then we are only waiting for the instructions how to make the device ;)
Really Per, really?
Red color with bold and everything...
The board is Duinomite Mega (it is the only board with CAN bus I think):
https://www.olimex.com/Products/Duino/Duinomite/DUINOMITE-MEGA/
The cable I built is using the normal CAN bus pins on the OBD plug to connect to the green connector on the duinomite mega board, as well as the GND and +12V for powering both the duinomite mega board, and the screen via the power jacks.
Both the screen and the duinomite mega should tolerate up to 30V DC.
Good luck! :)
I finally had the opportunity to plug my computer to a Think with Enerdel pack.
The result is a alfa version of the nikometer that can read max, min, avg cell values, max and min temperatures, and half pack soc.
Here is a fantastic and super detailed instruction how to install and prepare the duinomite:
http://priuschat.com/threads/my-duinomite-mega-canview-v4-equivalent-project.112429/ (http://priuschat.com/threads/my-duinomite-mega-canview-v4-equivalent-project.112429/)
When you are done with this you can download the AUTORUN.BAS (for the zebra Thinks) or the ENER_AUTORUN.BAS (for the lithium enerdel Thinks) from
https://sites.google.com/site/theevmonitor/think-ev-monitor/download (https://sites.google.com/site/theevmonitor/think-ev-monitor/download)
If you download the ENER_AUTORUN.BAS you need to remove the "ENER_" part of the name before uploading it to the duinomite.
Good luck!
Veldig interessant. Jeg har fortsatt OVMSen liggende og tenkte etterhvert å gjøre et forsøk på den. Utfra kildekoden til Duinomiten virker det som du har kartlagt de fleste CAN-meldingene - har du laget noen separat oversikt, eller eksisterer det kun i kode?
Sitat fra: jahnarne på søndag 16. juni 2013, klokken 21:12
Veldig interessant. Jeg har fortsatt OVMSen liggende og tenkte etterhvert å gjøre et forsøk på den. Utfra kildekoden til Duinomiten virker det som du har kartlagt de fleste CAN-meldingene - har du laget noen separat oversikt, eller eksisterer det kun i kode?
So far only in code. Take a look at it - it is not that complicated. Let me know if you have any questions.
I like my duinomite because it is simple and gives feedback in the car.
At the same time I would like to have the OVMS possibility to check soc remotely and get warning sms, etc.
Tror jeg skjønner gangen nå. Du lytter i praksis på 10 ulike CAN-meldinger som alle sendes med standard 11-bits IDer?
0x263: general
0x264: gear shifter position
0x301: bmi 1
0x302: bmi 2
0x303: bmi 3
0x304: bmi 4
0x305: bmi 5
0x311: bmi max charge current
0x610: enerdel specific
0x611: enerdel specific
Virker riktig?
Sitat fra: jahnarne på søndag 16. juni 2013, klokken 22:44
Virker riktig?
Yes
Har sett litt mer på dette i dag. Det bør gå greit å få på plass en enkel implementasjon på OVMS basert på arbeidet du har gjort. En relevant diskusjon er i så måte hva som evt bør ligge hvor. Er nemlig i grunnen enig med deg at en kombo av begge deler i grunnen hadde vært det beste.
Personlig tenker jeg at følgende hadde vært fint å få på SMS/app:
- Ladestatus (220V @ 11,3A)
- SOC (43%)
- Tid til fulladet (EOC)
- GPS-lokasjon
På sikt er såklart mulighet til å gi kommandoer tilbake, noe man kan se på:
- Start varmer
- Start/stopp lading
- Etc.
Resten er jeg tilbøyelig til å være enig hører hjemme i en in-car-monitor som Duinomite. Skal bestille en i dag, så kan jeg teste når jeg får den.
Vet noen om man kan bruke en OBD-splitter for å koble på begge enhetene?
BauDemo: hvilken skjerm anbefaler du?
Sitat fra: jahnarne på mandag 17. juni 2013, klokken 13:19
Personlig tenker jeg at følgende hadde vært fint å få på SMS/app:
- Ladestatus (220V @ 11,3A)
- SOC (43%)
- Tid til fulladet (EOC)
- GPS-lokasjon
I tested the time to full charge, but discovered it was not very accurate, instead I am doing "time to 80%" if the soc is lower than 80%, and "time to full" if the soc is above 80%.
The "available current" signal would be nice to have - see the screenshots in an earlier post with the 11.4A charging while the limit value from the box (or the available current) was 15.4A.
I planned also "battery temperature" - not super important, but very useful.
Don't forget the warnings - I thought of making it possible for the car to send you sms when the charging stops with soc and some other parameters. Another warning could be sms when the soc is under say 15%.
Sitat fra: jahnarne på mandag 17. juni 2013, klokken 13:19
Vet noen om man kan bruke en OBD-splitter for å koble på begge enhetene?
BauDemo: hvilken skjerm anbefaler du?
As long as both are listening on the can bus, there should be no problem to use splitter cable. If you start sending messages it could get complicated, or not, depending on some factors, but it could work too... after all there are already couple of ECU talking on that bus.
From the two screens I purchased, the wide screen is a bit better, and easier to read.
Here is the link - make sure you choose the 4.3" option when buying.
http://www.ebay.com/itm/7-3-5-4-3-TFT-LCD-Color-Car-Auto-Rearview-Monitor-VCR-DVD-GPS-Security-Camera-/300842218490 (http://www.ebay.com/itm/7-3-5-4-3-TFT-LCD-Color-Car-Auto-Rearview-Monitor-VCR-DVD-GPS-Security-Camera-/300842218490)
Duinomite Mega + 4,3" screen ordered :)
Yesterday I managed to follow the instruction on the priuschat.com page and download and install the new firmware with the CAN codes.
The instructions where followed to step 11 where the specific SW for the Prius is loaded to the SD-card. Obviously I here installed the SW made for the Think.
Everything seemed to work just fine and it looked just like on the priuschat page.
I went down to connect the monitor and could not get a picture at all no matter what. With the old FW at least I got some error messages.
This morning I tested with the actual screen I ordered to use in the Think and there was some success but I have two issues.
Number one and worst is that it's only one out of 5 (estimated) times that I start the screen (power on/off or video cable in/out) that I get a Picture at all.
Number two is that the picture when present is rolling just like old time TV sets could do. The speed of the roll is varying as is the direction of the roll (up or down). Coming to Think of it it could be that the times I don't get a picture the roll is so fast I can't see it or the screen is not able to show it.
Everything seems to be normal with the Duinomite and the startsequence is as expected with both red and yellow steadily lit and the green lit for a short while when accessing the SD card.
Any ideas ?
did you try the enerdel or zebra software?
Zebra, I downloaded that before there as an Enerdel variant.
Maybe I should mention it is still a bench test. No can connection.
Here is a suggestion - try the latest zebra version - the scrolling is probably a bug in the previous version that may have been fixed.
My screen is also flashing when the duinomite is started - I think it is trying to sync with the video signal of the duinomite. I suspect that there are better ways to support this, but don't know enough.
No improvement with the lastest SW.
Still quite rare to get a picture at all and when I do its rolling.
I'll try with a VGA monitor tomorrow to see if its any different.
try the following command:
CONFIG COMPOSITE NTSC
or
CONFIG COMPOSITE PAL
Morning update.
Have not tried the VGA monitor yet.
Tested the intended 3.5" display with a DVD (PAL only) player and had a good stable picture. Nothing wrong with the display it seems.
Tried to get a picture from the Mega again by plugging/unplugging the power to the display with limited success as earlier.
When I got a picture I tested the reset button on the Mega a couple of times and for I while I got a restart with picture (always rolling) and I also noted the before the Think-specific display there is a startup screen so small there is no chance to be able to read even if not scrolling.
I tried a mass test by pushing the reset button 30 times and realize sometimes the Mega does not stop reading the sd-card. The green diod keeps on until I press reset again. Normally the green led is on for about 2 sec. During the 30 resets I never got picture once and the green led hung twize.
It seems today its a lot less then 1 to 5 to get a picture, more like 1 to 20 of plugging/unplugging power to the display.
I'm testing as I write this and just realized when I got a picture with a slow roll that there are actually two screens before the Think specific one.
If I unplugg the sd-card with picture the picture stays on (normal I guess).
Managed to get the Mega started without the sd-card and I can see one of the microscopic texts, not sure witch.
I suppose there is a promt here for me to be able to write commands like the ones you suggested but the text is so small and the roll so quick there is no way to see if any text is registered.
When I get to see a text from the Mega, before it is displayed I always see the text AV1 (generated by the display itself) before the Mega text.
(http://i39.tinypic.com/ifbawy.jpg)
Interesting photo - this should not look like this. The prompt and the copyright text should be in the upper left corner of the screen.
I could not make out from the photo - what is the version of the duinomite firmware you have? 4.3 or 4.4?
I am running 4.3. Maybe the small sync issue I had in it was "fixed" in 4.4?
Edit:
Just read the release notes on the 4.4 version and there it is:
"Fixed a bug which caused the composite video on the Colour Maximite to be shifted to the
right on the screen."
So maybe the 4.3A version or the 4.3 version would behave better?
The reason for not being at upper left is that it is always rolling and i took the photo when it happened to be where it is.
I cant make out either what firmware it is, i'll try to check tonite. Will try to find a bigger screen, maybe the VGA.
When looking for earlier versions in the archive I found this interresting info in a textfile:
"SD cards reported as NOT working:
=================================
Dick Smith brand 4 GB
Kingston 4Gb microSD SDHC card into SD converter.
SanDisk 4GB
Transcend 2G MicroSD: The card is fine, works on PC (And camera). But 'Error Accessing the SD card' when used in the Maximite"
I believe I have the Sandisk 4GB since it was the smallest I could find. Will try to pick up one of the approved ones going back from work.
The text mentioned above is exactly what I recieved before updating firmware.
Bought a new sd-card on the way home. Did not make any difference.
Connected a VGA monitor, now its working ! Can not drive around with a 19" monitor on the dash.
Connected an old TV/display (7") and got a picture ! WOW, but only after setting "config composite pal".
Tried again with the intended display a 4,25" flip up display. No picture what so ever.This is the same display that I could watch a DVD on yesterday. Strange.
Guess I have to settle with the 7" display for now and order a new small display and hope for the best.
This is very unusual. I am starting to think that it maybe cable problem between the duinomite and the monitor. It will be hard to say what the problem is without osciloscope and a trained engineer to see if there is anything wrong with the video signal.
Did you try with the 4.3A version of the duinomite firmware? I think the sync code is software implemented and could be a bit different in the 4.3A version.
Another thing to try is to save the autorun.bas file on the built-in flash, and avoid using the sd-card. I use tera term terminal program to connect to the duinomite and then xtransfer the file to the file system.
I have tried with several cables since I thought that might be the problem too.
The Mega is running the 4.3A version. I could read it with the VGA monitor.
Running on the built-in flash or the sd would that make a difference towards working on one display and not the other ? I am more towards there is something wrong with the 4.25" display even though it works with a dvd.
Tomorrow I will connect to the OBD connector and see if it really works !
Now its working, sort of.
(http://i41.tinypic.com/263h3zm.jpg)
How I use teraterm to transfer file to the internal flash disk:
Start teraterm, connect to the serial port created by the usb driver for the duinomite, and on the duinomite prompt type
xmodem receive "autorun.bas"
This command will set the duinomite in a "receive" mode.
Then use the File->Transfer->Xmodem->Send menu on the tera term program and select the file from the host pc file system.
You will see some progress report and when the file is ready the duinomite will show prompt again.
Edit: Edited the text for clarity.
I will add my experiences to this very nice post. I received my Duinomite yesterday and had it flashed with the propper sw/fw and tested the composite video with my 32" 16:9 CRT-TV.
1) All needed to get the Duinomite Mega board running is the a USB-cable. The board is powered via the USB.
2) The higher quality of the composite-cable, the better. I compared a lo-fi v.s. hi-fi type, and it was a huge difference.
3) Plug the Duinomite Mega board to the computer and install the usb-driver Maximite. If not automatically detected it can be downloaded here
http://geoffg.net/Downloads/Maximite/Silicon_Chip_USB_Serial_Port_Driver.zip (http://geoffg.net/Downloads/Maximite/Silicon_Chip_USB_Serial_Port_Driver.zip)
4) Install TeraTerm at the computer, which offers serial communication and filetransfer. It can be downloaded from here:
http://en.sourceforge.jp/projects/ttssh2/downloads/58915/teraterm-4.78.exe/ (http://en.sourceforge.jp/projects/ttssh2/downloads/58915/teraterm-4.78.exe/)
5) Download the Duinomite Mega sw/fw. Due to some problems with scrolling display I found out that version 4.3A is working, and that 4.4 don't. There are two files needed for flashing the board, they can be found in the following zip-files:
- http://geoffg.net/Downloads/Maximite/Archives/DuinoMite_MMBasic_V4.3A.zip (http://geoffg.net/Downloads/Maximite/Archives/DuinoMite_MMBasic_V4.3A.zip) you need BootLoader.exe
- http://geoffg.net/Downloads/Maximite/Archives/MMBasic%20with%20CAN_V4.3A.zip (http://geoffg.net/Downloads/Maximite/Archives/MMBasic%20with%20CAN_V4.3A.zip) you need DuinoMite_MMBasic_V4.3A with CAN.hex
Store the files anywhere on the computer.
6) Start BootLoader.exe, push and hold the black button closes to the usb-connector on the Duinomite board and plugg the board to your computer. Then click "Load Hex file", browse to you find the file "DuinoMite_MMBasic_V4.3A with CAN.hex" and click "Program Device". When the board is flashed, you can unplug and plug it to restart.
7) Open a TeraTerm serial connection to the comport connected to the board (use device manager to find the correct com-port). To set up TeraTerm read the document "Installing the USB Serial Port Device Driver.pdf" you got in step 3 (Maximite usb driver)
When connected to the board and you have the prompt, type:
config composite pal
8 ) Download BauDemo's special made code for:
- Zebra https://sites.google.com/site/theevmonitor/think-ev-monitor/download/evmonZ.bas?attredirects=0&d=1 (https://sites.google.com/site/theevmonitor/think-ev-monitor/download/evmonZ.bas?attredirects=0&d=1)
- EnerDel https://sites.google.com/site/theevmonitor/think-ev-monitor/download/ENER_AUTORUN.BAS?attredirects=0&d=1 (https://sites.google.com/site/theevmonitor/think-ev-monitor/download/ENER_AUTORUN.BAS?attredirects=0&d=1)
Depending of your battery type:
either:
a) Copy one of those files to a MicroSD card root directory and insert into the Duinomite. When the board is restarted, this program is automatically loaded.
or
b) Transfer the autorun.bas to the boards flash (then you don't need a MicroSD-card. (I'll quote BauDemo here:) At the board prompt, type:
drive a:
xmodem receive "autorun.bas"
In the TeraTerm menu -> File->Transfer->Xmodem->Send menu on the TeraTerm program and select the file autorun.bas from the host pc file system.
9) Connect your composite video output to a display, and check if you get a stable image showing the new-Nikometer printout.
Next up for me is connecting the board CAN_L and CAN_H to the car and see if any battery data appears. I have not yet received my 4,3" display, and I don't intend to drag my 75kg 32" CRT-TV into the car, so I will wait for the package to arrive ;)
Thanks allot to BauDemo for all the effort put into testing, programming and posting to this forum!
/Håkon
I will add some information of how to handle files at the Duinomite board. The information is available in the MMBasic-archive in the file "MMBasic Language Manual.pdf".
The Duinomite has a built in flash which can store files, like autorun.bas. You should be careful not to wear out the flash. E.g. you can write and delete one file on it every day for 175 years before you reach the endurance limit - but if you write once a minute you reach the limit in about 6 weeks.
When the board is connected to the computer and TeraTerm is running you can run commands.
The built in flash is referred to as 'drive a:'.
The SD-card is refered to as 'drive b:'
Change drive by typing:
drive a:
drive b:
To list files on active drive:
files
To delete files on active drive:
kill "filename" e.g. kill "autorun.bas"
To run a file on active drive:
run "filename.bas" e.g. run "autorun.bas" or simply type
run
to start the default program stored in the flash/SD-card
To stop a running program and get back to the prompt >:
<CTRL>-C
To copy a file between drives, e.g. from SD-card to flash:
go to destination drive (flash a:)
drive a:
save file (autorun.bas) from SD-card:
save "autorun.bas"
I have noticed that the MMBasic is using the SD-card (drive b:) as default drive. So if you connect the board to TeraTerm, when no SD-card is inserted, and you type:
files
you get "Error: Cannot access the SD card".
Then you type:
drive a:
and you are ready to transfer the file (autorun.bas) from you computer to the flash:
xmodem receive "autorun.bas"
the prompt is gone and the board waits for your input of setting xmodem send
File -> Transfer -> Xmodem -> Send
Select "autorun.bas" and click Open.
Just had a short and successful test of the New Nikometer in my car. I have not received the 4,3" monitor yet, so I tested with my computer and TeraTerm.
Note that the Duinomite is sensible for polarization of CAN_L and CAN_H (not all CAN-devices are). If you look at the OBD2 from the passenger seat, CAN_H is third pin from the front on the left row, and CAN_L is the third pin from the front on the right row. On the Duinomite Mega board the CAN_H and CAN_L is evidently marked on the green connector.
BauDemo has made three different screens, which automatically are switched, depending if you charge, drive or have key off (left without charging).
See attached images.
@BauDemo:
I noticed that my "off-screen" displays:
2 * reduced number of batteries *
The 303 message variable is "variable _reduced_number_of_batteries" (Sys_Num_Batt_Reduced) is a True/False type.
I cannot find any logical usage of such message on the Zebra. Is it possible this message is for Enerdel only?
Great work hma! And congrats on your successful run of the program..
Sitat fra: hma på onsdag 17. juli 2013, klokken 21:36
@BauDemo:
I noticed that my "off-screen" displays:
2 * reduced number of batteries *
The 303 message variable is "variable _reduced_number_of_batteries" (Sys_Num_Batt_Reduced) is a True/False type.
I cannot find any logical usage of such message on the Zebra. Is it possible this message is for Enerdel only?
I also get this message when the pack is "off" (the car is not driving, nor charging) - I think (...speculation ahead...) it has to do with the fact that there are no batteries connected. So this error (or warning) tells that the contactors have disconnected the battery.
Some more info regarding the different screens.
The screens are drive, charge, standby.
Each screen has sections - possible sections are battery, drive, mains.
For example the drive screen is composed of battery and drive sections. While the charge screen is composed of the battery and mains sections.
Each section displays related data - the drive section shows speed, and economy values, while the mains section shows mains voltage, current and limit value sent from the EVSE (or PCS), as well as calculated power.
Also if errors/warnings are present they will be shown on the bottom of the screen. Some of these are normal - like the "iso test flag" once in a while, or "reduced number of batteries" when in standby.
Here is a drive screen with battery and drive sections annotated.
Got my 4,3" lcd-screen and the plastic box for the DuinoMite card (sold separately) today :-)
Made a preliminary test with the unit not attached to the canbus.
Her are my comments:
1) The autoscreen works fine (toggled either by restarting the program or hitting F8 (dec key code 152)
2) The standby page, toggled by F5 (d149), works fine.
3) The drive page, toggled by F6 (d150), works fine.
4) The charge page, toggled by F7 (d151), is fine for half a second. Then the text fields is displaced and overlaps it self. Maybe this will work better when the unit is reading a can-signal(?)
5) Diagnostic page, toggled by F10 (d154), works fine I assume (prints only zeros when no can signal is attached. The comment to the codeline is wrong, telling F9 is diagnosis.
6) Drive counters reset, togled by F9 (d153), I have not tried yet.
I think this looks very nice, and the code can be quite easy customized for tailored setup.
Next up is installing the devices in my Think, but that will happen the earliest in a few weeks. Have do deal with some traveling meanwhile ;)
I f anyone have a good suggestion how to pacth the wires from the lcd screen on top of the dash, please post it here :)
@BauDemo:
I got the idea that the program could be expanded to addition read data from the PCU, sort of like Chas.
Do you think that is possible?
The DuinoMite RS232 could be attached to the PCU/siadis-connector, then the program must open the serial port and read the data (...sounds easy in theory...)
First of all I'm thinking of reading the fault status bits (FltSt0-4) and print out the flag name and/or the fault cause.
There are other useful status flags which would be nice to display on a pcu-screen.
What do you think?
Update:
I recieved a new display the other day.
Heres what happened when I connected it
(http://i44.tinypic.com/312afer.jpg)
Looking good.
Evrything is off in the car.
Power comes from the OBDII plug.
Heres what happens when i turn to Ignition
(http://i41.tinypic.com/2nlr1pf.jpg)
The most interresting is that when you are driving, sorry no Picture showing this, is that the speed display ("0"'s in the Picture above) can be different if the speed is going up or down. I saw a differency of about 6-7 km/h between the "upper/lower speed figure during acceleration/braking. This should mean that it is not the display that is confused by some interferrence but the Duinimite.
Where does the "?" come from ? Should it not be a "D" ?
I get a similar distorted figure during charging.
Next step is to try to supply 12V from a separate battery.
Update 2:
Here's the dharging screen
(http://i42.tinypic.com/2u880fa.jpg)
Same screen but all Power to Duinomite and screen comes from a separate battery
(http://i41.tinypic.com/2mzfhx1.jpg)
This is a result of the duinomite wanting to display too much info on the screen.
I suspect you may have some errors present and when printed they scroll the screen up, the next refresh though restores the original positioning of the numbers, until the errors are printed. This happens very quickly and looks like a scroll.
The way to test is to comment away (using the apostrophe character - or single quote) the code for printing errors and warnings and see if it works better.
I can also try to send you a version with error printing commented away if adding the apostrophe is hard for you.
Sitat fra: Poppe på torsdag 01. august 2013, klokken 12:59
Update 2:
Here's the dharging screen
(http://i42.tinypic.com/2u880fa.jpg)
Same screen but all Power to Duinomite and screen comes from a separate battery
(http://i41.tinypic.com/2mzfhx1.jpg)
This is an interesting idea!
I have not looked at the communication on the PCU diagnostic connector and know nothing about it. In theory it would work - there are 3 serial ports on the duinomite - 1 rs232 and 2 ttl.
Sitat fra: hma på fredag 26. juli 2013, klokken 01:43
@BauDemo:
I got the idea that the program could be expanded to addition read data from the PCU, sort of like Chas.
Do you think that is possible?
The DuinoMite RS232 could be attached to the PCU/siadis-connector, then the program must open the serial port and read the data (...sounds easy in theory...)
First of all I'm thinking of reading the fault status bits (FltSt0-4) and print out the flag name and/or the fault cause.
There are other useful status flags which would be nice to display on a pcu-screen.
What do you think?
SitatI can also try to send you a version with error printing commented away if adding the apostrophe is hard for you.
That would be highly appreciated. You know I'm not a software guy.
Here's the lastest Picture after charging has finished. The picture is stable and with only one image. The only glitch seems to be the double "%" at the right top.
(http://i39.tinypic.com/2zo9a8n.jpg)
Now all my problems are solved thanks to intense mailexchange with Baudemo and a lot of his assistance.
This is what my display looks like now. I even got the old display that I ordered first to work with the new adjusted SW.
(http://i40.tinypic.com/funhic.jpg)
(http://i40.tinypic.com/a17976.jpg)
This newer firmware is available for download at
https://sites.google.com/site/theevmonitor/think-ev-monitor/download/evmonZ.bas?attredirects=0&d=1
You would need to change the name of the file to autorun.bas.
Medan eg ventar på masse CAN duppedittar kan eg kanskje stilla eit lite søtt spørsmål: korleis har ein kome fram til den informasjonen som hentast ut frå CAN bussen i autorun.bas, eksisterer det dokumentasjon eller er det reverse engineering heile vegen.?..
Har nokon kikka på OpenXC prosjektet (http://openxcplatform.com/)?
Det er jo eit Ford prosjekt i utgongspunktet, og ein kan uppdatera firmware og tilpassa CAN trafikk til ein standard protokoll, ganske greit om ein vil lage eit bluetooth/mobil interface til masse data..
Hmm, det fristar nesten å bruke ein RaspberryPi eller BeagleBone til å støtte både OpenXC og OVMS i same duppeditt, kanskje med ein 10.1 HDMI touch skjerm tilkobla.. :)
Sitat fra: habazot på onsdag 07. august 2013, klokken 11:47
Medan eg ventar på masse CAN duppedittar kan eg kanskje stilla eit lite søtt spørsmål: korleis har ein kome fram til den informasjonen som hentast ut frå CAN bussen i autorun.bas, eksisterer det dokumentasjon eller er det reverse engineering heile vegen.?..
There is no documentation that I know of. Maybe someone would like to document it.
Sitat fra: habazot på onsdag 07. august 2013, klokken 11:47
Hmm, det fristar nesten å bruke ein RaspberryPi eller BeagleBone til å støtte både OpenXC og OVMS i same duppeditt, kanskje med ein 10.1 HDMI touch skjerm tilkobla.. :)
Sounds spectacular - please do try and keep us posted!
Today I mounted the LCD-display on the top dash, by disassembling the silver plastic frame and the top plastic dash.
The display is fastened by velcro and its position can be adjusted.
Currently I'm working on a common cable loom for providing +12V, GND and CAN-signals to both the Duinomite/display and the OVMS-unit.
Tomorrow I will finalize it and mount all equipment in the car.
Next up is trying to implement some of the messages from the PCU/siadis port to the Duinomite RS232/com4-port.
It would be so cool to display the PCU-faults and other relevant values,in addition to the battery-data, on the dash-display. :)
We love pictures, send more if you can.. :)
I have not picked the dash apart yet, so I'm curious to where you guy guys put all the wires and stuff.
I'm planning a series of "pimps":
- changing CD/radio player to DAB bluetooth iphone handsfree bla bla
- changing speakers to 13cm two-way speakers, possibly adding a sub..
- install the OVMS module
- install parking distance sensors (ok, I know some of you migth choke on this, but hey..)
- install "myownCANdoeverythingandtalktoeverything" thingy.?..
But first of all I need to get my car back from the garage and all my gizmoz from china...
Oh, I forgot..:
- LED driving lights and generally leds everywhere, preferably with "tunnel sensor" :)
Usual disclaimer: All of the above if time, money and wife permits... ;)
Cable loom ready. Now, all equipment is installed in the car and works fine :)
The two black wires, exiting the picture on the right side, is composite video, +12V and GND for the dash-display.
The four light blue connectors hooks to the RAC connector (X12 24-pin):
- Pin1, +12V "always hot" - 10A - Fuse18 (optional pin 7 "Key run" - 5A - Fuse 39, but then the OVMS wont work when key is off)
- Pin 13 GND
- Pin 6: CAN_L
- PIN 18: CAN_H
Selger et komplett Duinomite-sett om noen er interessert: http://elbilforum.no/forum/index.php/topic,9705.0.html
Sitat fra: jahnarne på torsdag 03. oktober 2013, klokken 13:55
Selger et komplett Duinomite-sett
Er du i ferd med å gjennomgå en skillsmisse med Thinken? ;)
Da er også min Duinomite i gang.
Hadde problemer med å få inn driveren for serieport, men brukte bootloader først og la inn hex-fila, deretter fikk jeg inn driveren for serieporten.
Sitat fra: hma på torsdag 03. oktober 2013, klokken 20:06
Sitat fra: jahnarne på torsdag 03. oktober 2013, klokken 13:55
Selger et komplett Duinomite-sett
Er du i ferd med å gjennomgå en skillsmisse med Thinken? ;)
Uff, ja. Var faktisk veldig trist å la den gå. Etter jeg fikk på plass dieselvarmeren var den dønn solid og pålitelig. Ble desverre litt for snau plass m/nytt medlem i familien.
Duinomiten er forøvrig fortsatt til salgs. :/
Da ble det kuldegrader for første gang i Trondheim og dermed dukket det opp en liten bug i programmet!
Ved minusgrader viser duinomite plutselig 122 grader!
Tror dette kanskje kan løses på følgende vis (har ikke hatt tid til å teste ennå).
Legg til følgende funksjon rundt linje 500
Function getS7(hi)
Local result
result = hi
If (result > &H80) Then result = result - &HFF
getS7 = result
End Function
Så erstartter du linjen med tilordning av verdi for _pcu_ambient_temp (rundt linje 570) med:
_pcu_ambient_temp = getS7(rxData(2))/ 2
A new version with nice improvements by HMA is now available for download at:
https://sites.google.com/site/theevmonitor/think-ev-monitor/download/AUTORUN.BAS?attredirects=0&d=1 (https://sites.google.com/site/theevmonitor/think-ev-monitor/download/AUTORUN.BAS?attredirects=0&d=1)
Hello
We here in Germany have developed another kind of Data Display for the New Think.
Its based on the BMS from GK-Anlagentechnik (in Norway better known as the Robometer).
We adapted Can readout to the BMS Headunit and wrote some lines of code. ;-)
The Think CAN-Bus Display is still in development, but it exists Version 1.0.
We actually can display Voltage, Current, SOC and Zebra Temperature.
I now have a very practical question:
How did you (the Nikometer users) solve that the OBD plug is under the Fuse department closure, and with OBD plugged in, its no more possible to close the compartment. See pic. Before I make a new closing with an opening for the plug in it, I wanted to ask...
More pragmatic thinkers maybe leave it open all the time but I'd like a more elegant solution.
evdriver
Cool stuff :)
In the picture below you can see the connection for New-Nikometer/OVMS for my Think
(http://elbilforum.no/forum/index.php?action=dlattach;topic=6755.0;attach=13328;image)
It's attached to the RAC-connector (the black Molex-connector) which one can access from the area above the relay-box. The RAC-connector contains CAN_H, CAN_L, +12V (always hot + key on), GND and Airbag-lamp control.
It depends, if you have a RAC-unit you could use that plug, og piggyback on that signal. (Unfortunately, you must then fix the aibag-light if you roemove the RAC-unit).
If you have a Gen2 veichle like me and dont have a RAC, you can just buy a matching OBD2-splitter and mount that in where your plug now resides...
(guess you can do that in any case ;) )
I bought this one: http://www.obd2plugs.com/Product-453.html
(I got it at the end, even tho communications was somewhat difficult)
Hello Thinkers.
As time is precious I took a break the last months and no further progress was done in the proper connection of my Think CANbus Display.
Meanwhile I had to change a broken relay and could take a closer look underneath the passengers side. My RAC unit has been removed, but I think the cables are still there strapped together.
My aim is to get out the CAN H/ L Signals and 12V without using the original OBD plug.
I found it arkward to have the fusebox always open...
Is there knowledge about the PINOUT or Cable colours of the RAC Connector. Maybe it exists a drawing or someone can take a picture for the wiki.
This would be very very helpful.
evdriver
Think CANbus Display working: https://www.youtube.com/watch?feature=player_detailpage&v=fHMgeO-v7vU#t=449
Hello Thinkers.
I hate to reply myself, but meanwhile I found the solution.
In another Thread from hma is the pinout of the RAC molex connector:
Sitat fra: hma på søndag 29. september 2013, klokken 01:18
The 24-pin RAC-connector in the car is Molex 43025-2400 (female).
For the Ovms-cable one need a 43020-2401 (male)
RAC-pins:
- Pin 1: Always hot
- Ping 6: CAN_L
- (Pin 7: Key run, not needed, but nice to know)
- Pin 10: Airbag ECU status
- Pin 13: Gnd
- Pin 18: CAN_H
And heres a circuit diagram of the RAC.
http://elbilforum.no/forum/index.php?action=dlattach;topic=6755.0;attach=7787;image
The wire colours are:
- Pin 1: Always hot (white/yellow)
- Pin 6: CAN_L (blue)
- Pin 13: Gnd (black)
- Pin 18: CAN_H (red)
Will try to get the matching molex connector and adapt the Can Signal from here to my OBD Cable so that the fusebox can stay untouched.
evdriver
Hei,
i dag fikk jeg til å fungere på min Think for et annet formål. Etter det tok jeg ut reléboksen og hadde en titt på RAC. Ligger det.
Kan jeg trekke 24 Pin Connector uten å få noen feilmeldinger f.eks airbag lampe?
Er det mulig å fjerne / demontere RAC eller skal jeg la den i? Dens uten bruk lenger.
Hello,
today I got to work on my Think for another purpose. After that I took out the relay box and had a look at the RAC. Located it.
Can I pull the 24 Pin Connector without getting any error messages e.g. airbag lamp ?
Is it possible to remove/disassemble the RAC or should I leave it in? Its of no use any more.
regards evdriver
If you pull out the RAC the airbag error lamp will be lit always. HMA however have made a fix for this in the OVMS software (I do not know if this also is done with the duinomite).
You are correct that there is no practical use of the RAC anymore, except the error-check for the airbag.
Yes, it's correct as Warlock sais; an open 24-pinconnector will litt the airbag lamp.
Unless you plan to implement an airbag lamp control unit, I would recommend you to leave it.
The Ovms can control the lamp if adding a mosfet and resistor to one of the outputs.
The Duinomite can also do this thask (or any other programmable CAN-reading device). This requires a piece of code reading the airbag-status and setting one free analog i/o-pin according to the state. I have not done that, but it's doable.
A new version of the nikometer for the "new" Think is out. Read more about it here:
http://www.evmonitor.info/2014/09/economy-bargraph-in-think-ev-monitor.html (http://www.evmonitor.info/2014/09/economy-bargraph-in-think-ev-monitor.html)
Man, that is cool! Well done :)
(unfortunately I have no Think anymore, but my 2009-Think is not that far away; at my parents house, so I'll think I'll drive by and do an upgrade)
Fikk omsider lagt inn oppgraderingen, ser kjempebra ut helt til bilen kjører isolasjonsmåling!
Skjermen bli nesten uleselig, se vedlagte bilde. Er det min skjerm som er for liten?
Hello everyone:
I have fixed the latest Nikometer with compatibility for Enerdel and added the Economy bar.
https://www.dropbox.com/sh/2apq0xq72y7u8sy/AABBzAPvZWOhAW6J2lSVGRe1a?dl=0 (https://www.dropbox.com/sh/2apq0xq72y7u8sy/AABBzAPvZWOhAW6J2lSVGRe1a?dl=0)
Thanks for your work Victor!
Do you mind sending me a photo of your nikometer setup? I would love to publish this on www.evmonitor.info.
You changes also come quite handy - I am converting a Zebra Think to Enerdel and was thinking of bringing the latest changes to the Enerdel version of the program.
I had a go and improved (I think) the code and published the latest here:
The only thing not working is the charge time estimation - I tried to improve it and broke it.
Here is a blog post with more info and two videos showing functions:
http://www.evmonitor.info/2016/08/new-version-of-nikometer-for-think-a306.html (http://www.evmonitor.info/2016/08/new-version-of-nikometer-for-think-a306.html)
Sitat fra: BauDemo på onsdag 24. august 2016, klokken 12:22
I had a go and improved (I think) the code and published the latest here:
The only thing not working is the charge time estimation - I tried to improve it and broke it.
Here is a blog post with more info and two videos showing functions:
http://www.evmonitor.info/2016/08/new-version-of-nikometer-for-think-a306.html (http://www.evmonitor.info/2016/08/new-version-of-nikometer-for-think-a306.html)
Just tried, TeraTerm gives me answer:
[1] ;?' v. 2016-08-24
Error: Invalid character
>
Where is the problem?
Sitat fra: BauDemo på tirsdag 23. august 2016, klokken 08:33
Thanks for your work Victor!
Do you mind sending me a photo of your nikometer setup? I would love to publish this on www.evmonitor.info.
You changes also come quite handy - I am converting a Zebra Think to Enerdel and was thinking of bringing the latest changes to the Enerdel version of the program.
You're welcome!
Here are pictures of my setup.
The Duinomite takes it's power via USB and the display shares the power input from the car's radio power connection DIY Y-splitter.
Sitat fra: Victor Micordia på søndag 28. august 2016, klokken 18:17
Sitat fra: BauDemo på onsdag 24. august 2016, klokken 12:22
I had a go and improved (I think) the code and published the latest here:
The only thing not working is the charge time estimation - I tried to improve it and broke it.
Here is a blog post with more info and two videos showing functions:
http://www.evmonitor.info/2016/08/new-version-of-nikometer-for-think-a306.html (http://www.evmonitor.info/2016/08/new-version-of-nikometer-for-think-a306.html)
Just tried, TeraTerm gives me answer:
[1] ;?' v. 2016-08-24
Error: Invalid character
>
Where is the problem?
The problem is the first two characters in the file - the ;?
Remove them and all should be fine - I think these are added when transferring the file from the duinomite to my computer... I will double check this and change the file on the site.
Thanks for the photos - very smart usage of the box!
Does anyone have a store to reccomend where I can buy the duinomite? Or is it Only the "official" store? I see Amazon.Com sell the as well.
I buy mine from mouser.com ... they have free delivery when you buy above certain amount...
But there are many different outlets - ask your local electronics shop.
Thanks, ordered from Mouser today. Got a screen yesterday, looking forward to get some control over my battery and consumption :)
Sitat fra: BauDemo på mandag 29. august 2016, klokken 23:30
Sitat fra: Victor Micordia på søndag 28. august 2016, klokken 18:17
Just tried, TeraTerm gives me answer:
[1] ;?' v. 2016-08-24
Error: Invalid character
>
Where is the problem?
The problem is the first two characters in the file - the ;?
Remove them and all should be fine - I think these are added when transferring the file from the duinomite to my computer... I will double check this and change the file on the site.
Removed the ";?" and all the release notes, still not working.
Updated the ENERDEL_AUTORUN_DEBUG.BAS file.
Er tilkoblingsskjema det samme som i denne tråden med tanke på OBD-kontakten?
http://priuschat.com/threads/my-duinomite-mega-canview-v4-equivalent-project.112429/
Sitat fra: Victor Micordia på lørdag 10. september 2016, klokken 08:22
Removed the ";?" and all the release notes, still not working.
"still not working" does not give me much to work with - can you please take a screenshot of the error?
I had some time and made a new version where the program senses if the nikometer is connected to a Zebra or Enerdel car and displays different interface dependant on this.
Please give it a go and let me know if you see any problems.
Sitat fra: Go-carter på mandag 12. september 2016, klokken 11:52
Er tilkoblingsskjema det samme som i denne tråden med tanke på OBD-kontakten?
http://priuschat.com/threads/my-duinomite-mega-canview-v4-equivalent-project.112429/
I think this would work - I think there was a detailed instruction somewhere in this thread by HMA.
Thanks a lot! Red HMA's explanation and everything went smooth :) teste it with my laptop and everything seems right (it even show my termal ISO fault)
Do you guys keep the power on the screen and computer at all times? Or do you power them off when the car is off? In that case, you wouldnt be able to read the charge screen?
I have not been able to figure out a good solution for the powering of the device and the screen. I usually just unplug it... but I have a use for it in more than one car and it is easier for development and debugging.
Maybe someone else can chime in.
I have a termal ISO error so I have to have the car plugged in all the time, so for me it probaby doesnt matter.
Big thanks for the software and all the time you have spent making this. Smiled all the way home today looking at the screen. Should have done this mod waaaay earlier, would have saved me for a lot of trouble and time in the workshop.
Sorry for spamming down the thread... But is there a explanation of the error messages somewhere? Today I got iso test flag (which I understanding was normal) but also "BMI error: 1" what cold the last one be?
Sitat fra: Go-carter på torsdag 15. september 2016, klokken 16:21
"BMI error: 1" what cold the last one be?
sys_highestErrCat, Highest error cattegory among active errors in battery system:
0 = No error
1 = Category statistic, (forsvinder af sig selv når fejlen forsvinder/rettes)
2 = Category notice, (skal resettes af zebra-monitor)
3 = Category delayed switch off, (skal resettes af zebra-monitor)
4 = Category switch off, (skal resettes af zebra-monitor)
Men,.....som jeg opdagede, så kan selv en category 3 fejl resette sig selv, og sker det ville jeg nok køle batteriet ned og få BMI'en undersøgt grundigt før næste "katastrofe" sætter ind. :o
sys_BMI_State, BMI state:
0 = Park
1 = Discharge
2 = Ready to charge
3 = Charging in progress
4 = OpenCircuitVoltage messurement in progress
5 = Charge complete
6 = Battery temperature below lower operating treshold. Heating in progress
7 = Battery temperature abowe higher operating treshold. Coling in progress
8 = Power up
9 - E(14) = TBD, (to be discussed ?)
F (15) = Fault. Set if ErrCat = 3 or 4. Battery operation will terminate
Takk. Står dette noe sted i koden, eller i servicemanual?
Det skal nevnes at samtidig med BMI Error:1 så lyser varsellampe for varmt drivverk i dashbordet. Dette får jeg stort sett hver dag, etter jeg har ladet en dag på jobb i parkeringshus. Kanskje det er en feilmelding for at BMI blir for varm? Både PCU og batteritemp er OK. (henholdsvis 28,5 og 270-280)
Sitat fra: Go-carter på fredag 16. september 2016, klokken 09:51
Takk. Står dette noe sted i koden, eller i servicemanual?
Det er fra noget zebra-dokumentation. Det står ikke i BauDemo's program.
Original nicometret er nok mest tænkt som et kørselsinstrument mere end som et diagnose værktøj. Jeg "bygger" på en version hvor focus er mere på diagnose, og hvor diagnose siden er mere forklarende og mere omfattende, men jeg blev langfra færdig før bilen satte et midlertidig stop for den aktivitet. Du må gerne få den ufærdige version hvis du vil programmere videre selv. Skylder også BauDemo en version, men for de fleste er programmet lidt for "alpha" endnu ;)
Sitat fra: Orla Pedersen på fredag 16. september 2016, klokken 10:14
Sitat fra: Go-carter på fredag 16. september 2016, klokken 09:51
Takk. Står dette noe sted i koden, eller i servicemanual?
Det er fra noget zebra-dokumentation. Det står ikke i BauDemo's program.
Original nicometret er nok mest tænkt som et kørselsinstrument mere end som et diagnose værktøj. Jeg "bygger" på en version hvor focus er mere på diagnose, og hvor diagnose siden er mere forklarende og mere omfattende, men jeg blev langfra færdig før bilen satte et midlertidig stop for den aktivitet. Du må gerne få den ufærdige version hvis du vil programmere videre selv. Skylder også BauDemo en version, men for de fleste er programmet lidt for "alpha" endnu ;)
Gjerne det! Jeg har kun begrenset erfaring med programmering i forbindelse med Arduino og RaspberryPi, men pappa har programmert siden 80-tallet så kan evt. høre med han om hjelp :)
Can you publish the code you have somewhere so anyone that wants can access it and work on it? I can publish it on the www.evmonitor.info if you like.
Sitat fra: BauDemo på fredag 16. september 2016, klokken 11:51
Can you publish the code you have somewhere so anyone that wants can access it and work on it? I can publish it on the www.evmonitor.info if you like.
I've mailed the sw to you, please publish it on the web. It's very far from finished. I've been away from the car some time, but next month there might be time to investigate BMI emulation and maybe drivetrain test.
Sitat fra: BauDemo på onsdag 14. september 2016, klokken 14:52
I have not been able to figure out a good solution for the powering of the device and the screen. I usually just unplug it... but I have a use for it in more than one car and it is easier for development and debugging.
Maybe someone else can chime in.
Try this?
http://www.ebay.com/itm/12V-24V-Male-Car-Cigarette-Lighter-Socket-Plug-Connector-On-Off-Switch-1-5m-HUUL-/161912866678?hash=item25b2c24776:g:2rcAAOSw8-tWaB0o
Finally had time to paint and fix my 3d printed mount this morning. Not exactly the best finish, but very easy to read :)
(https://scontent-amt2-1.xx.fbcdn.net/v/t1.0-9/14330073_10153676749346612_6122173740547753116_n.jpg?oh=076d71b7e3f4249f2ec78242e68c641b&oe=586C9A15)
(https://scontent-amt2-1.xx.fbcdn.net/v/t1.0-9/14344155_10153676749516612_4013499409909954004_n.jpg?oh=691bdf91280f47d58d8d48f5c107b837&oe=583C6F43)
Sitat fra: Go-carter på lørdag 17. september 2016, klokken 12:20
Finally had time to paint and fix my 3d printed mount this morning. Not exactly the best finish, but very easy to read :)
Nice!
Can I publish these photos on www.evmonitor.info as an example of install?
Thanks! No problem :)
Veldig fin løsning. 8)
Printet du hele plata ny, eller kuttet du hull i den gamle og printet bare "innsatsen"?
Sitat fra: Warlock på mandag 19. september 2016, klokken 22:58
Veldig fin løsning. 8)
Printet du hele plata ny, eller kuttet du hull i den gamle og printet bare "innsatsen"?
Takk :) Vurderte å printe hele platen, men jeg kuttet bare hull i den eksisterende med en Dremel. Hadde jeg fortsatt hatt tilgang til skoleverkstedet hadde jeg lagd en plugg i treverk tilsvarende holderen og plata slik den ble nå og vakuumtrekt den med plastikk. Det hadde blitt vesentlig høyere finish 8)
Hello guys, we're actually in Norway and brought something with us....
From today on you can order the new Think-O-meter OBD plug and play Display via Elbilhjelpen. Its called the new RoboMeter 306 there.
Kind regards evdriver
Sitat fra: cs på søndag 23. mars 2014, klokken 18:16
Hello
We here in Germany have developed another kind of Data Display for the New Think.
Its based on the BMS from GK-Anlagentechnik (in Norway better known as the Robometer).
We adapted Can readout to the BMS Headunit and wrote some lines of code. ;-)
The Think CAN-Bus Display is still in development, but it exists Version 1.0.
We actually can display Voltage, Current, SOC and Zebra Temperature.
I now have a very practical question:
How did you (the Nikometer users) solve that the OBD plug is under the Fuse department closure, and with OBD plugged in, its no more possible to close the compartment. See pic. Before I make a new closing with an opening for the plug in it, I wanted to ask...
More pragmatic thinkers maybe leave it open all the time but I'd like a more elegant solution.
evdriver
Sitat fra: cs på torsdag 13. oktober 2016, klokken 14:34
Hello guys, we're actually in Norway and brought something with us....
From today on you can order the new Think-O-meter OBD plug and play Display via Elbilhjelpen. Its called the new RoboMeter there.
Kind regards evdriver
Sitat fra: cs på søndag 23. mars 2014, klokken 18:16
Hello
We here in Germany have developed another kind of Data Display for the New Think.
Its based on the BMS from GK-Anlagentechnik (in Norway better known as the Robometer).
We adapted Can readout to the BMS Headunit and wrote some lines of code. ;-)
The Think CAN-Bus Display is still in development, but it exists Version 1.0.
We actually can display Voltage, Current, SOC and Zebra Temperature.
I now have a very practical question:
How did you (the Nikometer users) solve that the OBD plug is under the Fuse department closure, and with OBD plugged in, its no more possible to close the compartment. See pic. Before I make a new closing with an opening for the plug in it, I wanted to ask...
More pragmatic thinkers maybe leave it open all the time but I'd like a more elegant solution.
evdriver
Pictures? :D
Hej.
I have only a video from an early test https://youtu.be/fHMgeO-v7vU#t=0h8m0s
You will find product pictures in Roborts shop soon. I saw him taking them this morning...
;)
Legges straks ut på nettbutikken (http://www.yourvismawebsite.com/elbilhjelpenno-as/shop/product/robometer-for-think-a306?tm=annet-utstyr), men her er noen bilder.
Plug and play. 1 meny på Zebra med systemspenning, strøm og temperatur, og 2 på Litium versjon med bl.a høyeste og laveste cellespenning. Ble overrasket over hvor jevne fatteren sine celler var etter nesten 80 000 km og null verkstedsbesøk.
Pris 2500.-
Pen løsning, og en helt grei pris for plug-n-play iallefall. :) Synd Think har plassert OBD-kontakten på et så ugunstig sted. Hjalp ARV her på forumet med å montere BauDemo sitt oppsett i går, og selv med vinklet OBD-kontakt lot det seg ikke å få på lokket. Kanskje det går an å skru det ned?
Enig. Det enkleste er enten å flytte diagnosekontakten eller lage et hull like over den.
Jeg ville kjøpt en splittekabel (eller egnentlig, jeg har kjøpt en y-kabel fra et kinafirma. Kommunikasjonen var vel o merke svært spesiell). Man kan da skru ned kontakten, og plugge sammen og skru en av y-armene inn ved siden av sikringsboken og a en løs OBDII kontakt henende under klar til mer eller mindre permanent inplugging...
Sitat fra: Warlock på onsdag 19. oktober 2016, klokken 23:42
Jeg ville kjøpt en splittekabel (eller egnentlig, jeg har kjøpt en y-kabel fra et kinafirma. Kommunikasjonen var vel o merke svært spesiell). Man kan da skru ned kontakten, og plugge sammen og skru en av y-armene inn ved siden av sikringsboken og a en løs OBDII kontakt henende under klar til mer eller mindre permanent inplugging...
Har du lust att ladda upp en bild på din lösning?
Ikke så lett å ta bilder av installert kabel, men legger ved et bilde av splitterkabelen. Man skrur løs ODBII pluggen i bilen og slipper den end. Skrur inn den blå kontakten til venstre i bildet i dennes sted, og man ser ingen forskjell (og lokket går på uten modifikasjoner). Original kabel plugges inn i kontakten til høyre. og med noen få strips har man også fått festet dette opp ganske bra. Nå har man en ekstra ODBII plugg under "hanskehyllen" også, den bakerst til venstre på bildet...
God løsning.
Er dette ordinær handelsvare?
Ja, jeg bestilte den fra http://www.obd2plugs.com/Product-453.html for noen år siden men som sagt, kommunikasjonen var svært rar, og transporten kostet dobbelt så mye som kabelen, så jeg vil anbefale å bestille opp en liten batch....
http://www.ebay.com/itm/OBD2-Y-Connector-Cable-Universal-Snap-In-with-Underdash-Bracket-Y-Adapter-OBDII-/191594075585?hash=item2c9be595c1:m:majmuJ6AG02VZ_V-jnyRCcQ&item=191594075585&vxp=mtr
290,- pr. stk. inkl frakt på ebay. 80 for kabelen og 210 for frakt...
Alternativt kan man kjøpe brakett for 140,-:
http://www.ebay.com/itm/OBD2-Under-Dash-Mounting-Bracket-for-OBDII-Y-adapter-cable-/191721236045?hash=item2ca379e64d:g:5B4AAOSwq5lTmgeY
Og en spliot-kabel til snap-in montering til 45,-
http://www.ebay.com/itm/1-To-2-16-Pin-J1962-Y-OBD2-II-Cable-Female-Splitter-Extension-Auto-Car-Connector-/261995798868?hash=item3d002aa154:g:v5oAAOSwHjNV-34z
Og havne på 185 totalt,-. Tror jeg hadde gått for førstnevnte :)
Takk. Forespørsel på 5-10 kabler sendt.
http://www.ebay.com/itm/OBD2-Y-Connector-Cable-Universal-Underdash-Type-Y-Adapter-OBDII-/302054301356?hash=item4653d6deac:g:q84AAOSwgY9XeLtH&item=302054301356&vxp=mtr
Liker ikke Nikometeret minusgrader? Nå som det begynner å bli kalt ute påstår den at PCU holder 125 grader :p
Og foresten - stemmer SOC? Når bilen sier 30 % sier Nikometeret 39%. har jeg så mye å gå på?
Høres ut som noen har glemt at integere er signed/unsigned :)
Når det gjelder SOC så sier vel noe i dokumentasjonen som dukket opp nylig at SOC ikke er så alt for godt mål på rekkevidde, spesielt ved lave verdier, og at et annet mål burde brukes som rekkeviddemåler. Kanskje det bilen viser dette istedet for SOC? Tror den ble kalt SOUE (State of usable Energy) men uansett tviler jeg på at det er så stor forskjell. Mer mulig at Think har spart en del i hver ende....
Sitat fra: Go-carter på torsdag 03. november 2016, klokken 23:03
Liker ikke Nikometeret minusgrader? Nå som det begynner å bli kalt ute påstår den at PCU holder 125 grader :p
Og foresten - stemmer SOC? Når bilen sier 30 % sier Nikometeret 39%. har jeg så mye å gå på?
Unsigned/signed is my fault - I will try to rectify this very soon.
Are you seeing 30% on the dashboard? I don't think what you see on the
dash is very accurate. The best way would be if you could get a computer with working zebramonitor and check the SOC reported by the BMI... then we can compare values.
Nikolay
Is it possible to use this to readout error codes and reset them?
Sitat fra: Urfalo på torsdag 02. februar 2017, klokken 07:18
Is it possible to use this to readout error codes and reset them?
Read, yes, at least many of the codes and values, but you have to read the program source to understand fully what is going on.
Reset, no, that would involve more programming....
What is the programming language for the software on the Nicometer? If it's Basic, what Basic and version?
ThinkGeo
Sitat fra: ThinkGeo på fredag 03. februar 2017, klokken 22:39
What is the programming language for the software on the Nicometer? If it's Basic, what Basic and version?
ThinkGeo
It's a kind of basic ported to PIC-microcontrolers, you can read about it here: http://mmbasic.com
It makes it very easy to use in and output pins on the microcontroler.
Where do I buy this developer card? Anyone tried making this for Raspberry pi? Seams preatty easy comunicate with the can bus, but I what I really want is a USB-OBD/CAN BUS cable with a software to read out the error codes.
I have asked around on eBay, the different stores selling OBD scanners, palmerperformance and so on. I have 5 different scanners/cables, but none of them will talk to my think. I found a service document for Think recomending using Can Viewer for diagnostic, but my USB OBD cable does not work with this eighter. Is the CAN bus pin 6 and 14 as normal in other cars?
Sitat fra: Urfalo på søndag 05. februar 2017, klokken 23:32
Where do I buy this developer card? Anyone tried making this for Raspberry pi? Seams preatty easy comunicate with the can bus, but I what I really want is a USB-OBD/CAN BUS cable with a software to read out the error codes.
I have asked around on eBay, the different stores selling OBD scanners, palmerperformance and so on. I have 5 different scanners/cables, but none of them will talk to my think. I found a service document for Think recomending using Can Viewer for diagnostic, but my USB OBD cable does not work with this eighter. Is the CAN bus pin 6 and 14 as normal in other cars?
I think if you get a shield that supports OBD, you can probably even use Arduino.
I bought the develloper card (duinomite) on Mouser electronics homepage.
OBDII is just a set of common command set to list out data sent over the CAN-bus, a 3rd layer. It doesn't cover all car specific codes/requests, just a very limited and basic set for the most common tasks. So what you need is a CAN-shield for your raspberry so you can operate on a lower level. If you get hold of that, its easy(? depending on skill/time) to port whatever open software written to monitor the Think, being the nicometer or the OVMS.
Thanks for the support. Now I've ordered the duinomite hoping to find the reason for the red wrench.
Anyone tested the Can bus view?
http://vehiculeselectriques.free.fr/Download/Think/THINK%20City%20Enerdel%20Battery%20Service%20Manual.pdf
A bit expencive, but seems to give raw hex data from the CAN bus.
After installing the MMBasic with CAN_V4.3A the computer does not recognize the Dunomite_Mega. Before Firmware upgrade it comes up as COM3. It comes up as a unknown unit, and it will not install the Silicon_Chip_USB_Serial_Port_Driver. :o
Sitat fra: Urfalo på mandag 13. februar 2017, klokken 07:32
After installing the MMBasic with CAN_V4.3A the computer does not recognize the Dunomite_Mega. Before Firmware upgrade it comes up as COM3. It comes up as a unknown unit, and it will not install the Silicon_Chip_USB_Serial_Port_Driver. :o
Have you followed the guide on the Prius forum, mentioned earlier in this thread?
It worked with external power on the card. :+1:
Sitat fra: Urfalo på mandag 13. februar 2017, klokken 19:32
It worked with external power on the card. :+1:
I've made a "diagnostic" version of the software. It covers a bit more than the original "nicometer" and has a bit more "user friendly" messages.
(http://www.tfv-org.dk/th!nk/diagnose/foto/diagterm.jpg)
It is far from finished, and there are most likely some faults left to be considered, so absolutely no garanties given. This is "as is", use it and develop it as you like, but pleace share here.
Find it here http://www.tfv-org.dk/th!nk/diagnose/ remember to change the ".txt" to ".bas" after download.
På dansk:
Projectet er langt fra færdigt, men da jeg ved at tid er en mangelvare og udsigterne til et "færdigt" diagnoseværktøj har lange udsigter, så får i denne version af mit diagnose værktøj til frit brug. Det er grundlæggende baseret på bauDemo's "nicometer", men udvidet med mere funktionalitet og en mere brugervenlig visning. Husk at der sikkert er fejl her og der når du bruger programmet, og meld gerne tilbage med de "bugs" du opdager. Der gives ingen garantier. Hvis du udvikler videre på denne software håber jeg at du offentliggør din version her. :)
Tusen takk! Jeg skal laste ned VGA-versjonen og teste i morgen :)
Great work!
I made a small post about it here -
http://www.evmonitor.info/2017/02/think-a306-new-diagnostic-utility.html
Hopefully it gets big exposure and more people can use it.
Is it ok to publish your screenshot on the blog?
Nikolay
Sitat fra: Orla Pedersen på tirsdag 21. februar 2017, klokken 19:45
Sitat fra: Urfalo på mandag 13. februar 2017, klokken 19:32
It worked with external power on the card. :+1:
I've made a "diagnostic" version of the software. It covers a bit more than the original "nicometer" and has a bit more "user friendly" messages.
(http://www.tfv-org.dk/th!nk/diagnose/foto/diagterm.jpg)
It is far from finished, and there are most likely some faults left to be considered, so absolutely no garanties given. This is "as is", use it and develop it as you like, but pleace share here.
Find it here http://www.tfv-org.dk/th!nk/diagnose/ remember to change the ".txt" to ".bas" after download.
På dansk:
Projectet er langt fra færdigt, men da jeg ved at tid er en mangelvare og udsigterne til et "færdigt" diagnoseværktøj har lange udsigter, så får i denne version af mit diagnose værktøj til frit brug. Det er grundlæggende baseret på bauDemo's "nicometer", men udvidet med mere funktionalitet og en mere brugervenlig visning. Husk at der sikkert er fejl her og der når du bruger programmet, og meld gerne tilbage med de "bugs" du opdager. Der gives ingen garantier. Hvis du udvikler videre på denne software håber jeg at du offentliggør din version her. :)
Sitat fra: BauDemo på mandag 27. februar 2017, klokken 10:28
Is it ok to publish your screenshot on the blog?
Nikolay
Yes, please do
Sitat fra: Orla Pedersen på tirsdag 21. februar 2017, klokken 19:45
Sitat fra: Urfalo på mandag 13. februar 2017, klokken 19:32
It worked with external power on the card. :+1:
I've made a "diagnostic" version of the software. It covers a bit more than the original "nicometer" and has a bit more "user friendly" messages.
(http://www.tfv-org.dk/th!nk/diagnose/foto/diagterm.jpg)
It is far from finished, and there are most likely some faults left to be considered, so absolutely no garanties given. This is "as is", use it and develop it as you like, but pleace share here.
Find it here http://www.tfv-org.dk/th!nk/diagnose/ remember to change the ".txt" to ".bas" after download.
På dansk:
Projectet er langt fra færdigt, men da jeg ved at tid er en mangelvare og udsigterne til et "færdigt" diagnoseværktøj har lange udsigter, så får i denne version af mit diagnose værktøj til frit brug. Det er grundlæggende baseret på bauDemo's "nicometer", men udvidet med mere funktionalitet og en mere brugervenlig visning. Husk at der sikkert er fejl her og der når du bruger programmet, og meld gerne tilbage med de "bugs" du opdager. Der gives ingen garantier. Hvis du udvikler videre på denne software håber jeg at du offentliggør din version her. :)
Thank you. Is it yust to edit the .txt and then the program cahnges, or does it need some kind of compiling?
Seems kind of understandable language.
Sitat fra: Urfalo på fredag 17. mars 2017, klokken 21:21
Thank you. Is it yust to edit the .txt and then the program cahnges, or does it need some kind of compiling?
Seems kind of understandable language.
Just change the extension to ".bas" and move the file to the duinomite SD-card, no compiling no changes. The 2 reasons for ".txt" is that, 1. It is actually just a textfile that the duinomite interpretes, 2. You will never be alowed to download a ". bas" file for your antivirus program ;)
Hello guys!
With the cars are getting older and dies, also the forum activity goes down while the faults and errors are getting more and more complex.... :police:
I'm trying to get the duinomite to put out composite but it seems stuck in VGA mode. I have read various documentation and tried different commands in Tera-term and also gotten fast replies from Geoff in Oz.
Still no luck... any of you having the same issues and solved them?
As I understand it it's either VGA or Composite and VGA works. Seems stuck in VGA mode. This is controlled by checking for grounding in the VGA connector when the screen is plugged in. Maybe it's as easy as tracing the problem to a faulty soldering on the board?
Well, any way thought I would ask.
Thanks 1000 for all great posts over here.
Can you write a bit more on what you have tried, instead of me trying to guess what you did try and what you did not.
Sitat fra: BauDemo på tirsdag 30. juni 2020, klokken 16:50
Can you write a bit more on what you have tried, instead of me trying to guess what you did try and what you did not.
Sure, thanks for your reply
Reflash Duinomite with 4.3 and 4.4 fw
Re-write SD card with various versions of nikometer
Installing directly on the board
Cleaning the board from white powder from manufacturing
Call reseller and ask if this is heard of (nope)
Emailing Geoff with answer that recompiling the code you could switch of VGA permanent (not tried it)
Tried two different screens
Switch of VGA with tera term, yellow led goes out but then no video at all
Force composite with tera term - no difference
Tried pulling pin 19/20 up or down with no results
Next would be de solder the VGA connector from board to se of it shorts the ground signal making the board thing the screen is there.
If this is never heard of before chases my board is bad are quite high I think.
you tried config composite command?
you restarted the board after the command?
Sitat fra: BauDemo på onsdag 01. juli 2020, klokken 12:48
you tried config composite command?
you restarted the board after the command?
Yep. That did not switch on my composite screen, how ever I did not test with vga, if that one did shut down with the command sent.
Did you test your composite screen?
Where do you live? Maybe there is someone that has a working duinomite so you can compare or switch modules to make sure?
Hello! I'm trying to revive this thread.
For a first time for many years, i have a think again. i tried to use the diagnostic software from Orla, and it was nice to see so much information.
Does anyone know if this is written for zebra-battery or enerdel? I have a enerdel-battery now, and it looks so healthy i have a hard time beliveing that it really has no failed cells :D
[ This attachment cannot be displayed inline in 'Print Page' view ]
Muligens litt off det du spør om, mitt Zebra batteri tok jo kvelden høsten 2017. Jeg kom den gangen over en Enerdel Li Think delebil med flere feil som gjorde at den verken ladet eller startet. Jeg overtok den og fikk satt batteriet over i min, og det viste seg at dette var et full funksjonelt batteri, uten ødelagte eller svake celler, til tross for at bilen hadde stått ute på tunet i 12-15 mnd på det tidspunktet. Heldigvis var den ikke fulladet, lå på ca 60% som vel er ideelt ved langtidslagring. Nå, mer enn tre år senere går fremdeles bilen 16 mil ved pen kjøring sommer/høst. Bilen har gått nesten 110' og Li batteriet nesten 100'. Så for min del virker Enerdel batteriet utrolig solid bygget.
Sitat fra: Go-carter på tirsdag 09. februar 2021, klokken 08:12
Does anyone know if this is written for zebra-battery or enerdel? I have a enerdel-battery now, and it looks so healthy i have a hard time beliveing that it really has no failed cells :D
There is an enerdel version of nikometer software that shows minimum, average and maximum cell voltage. Try it.
Sitat fra: Go-carter på tirsdag 09. februar 2021, klokken 08:12
Hello! I'm trying to revive this thread.
Does anyone know if this is written for zebra-battery or enerdel?
[ This attachment cannot be displayed inline in 'Print Page' view ]
It's for zebra, and It's been idle for some time. ::)
I've done small progress on the BMI emulater and a power supply to test the power train. Other things have had priority, sadly.
Mvh
Orla
Always nice to dig out an old thread, especially when you get the warning about that nobody wrote something here in more than 120 days. How ever... ;D
Because of some trouble with my red Think, I startet to use more time analysing the "Nicometer" Basic-program.
I started to move subbroutines and functions and changed some names. I deleted unused codelines and put inn a lot of comments. I even have created a flowchart to explain the whole program and literally every codeline. This will help a lot of others to perhaps make their own versions.
I'm not finished yet, but I started to design the screens a little bit more userfriendly. And even if I only can use black and white elements, I started to change the look of some modules which are used on the different pages. The most changes are under the hood for now.
Since I don't use a keyboard in my car - who do that? - I changed the programcode which gives the possibility to change between the four screens. Of course, there is a autoscreen function or routine, but I use buttons now, which I connected to my "Duinomite Mega" board.
I even startet to program a overlay menue which should be easier to use with two-three buttons or a small joystick. Could be as fancy as in a modern car. :D
In addition I created two fonts which I use for special signs. Font 1 and 2 havn't special signs or pictograms to make some values easier to understand, like arrows to show max and min values or something like an "ø" for mean values or even the "degree sign" is not available in the two original fonts. It looks much more better with some pictograms!
How ever...Here is just a short preview of a start animation and a slightly changed "Drive page".
I will use some time from now on to customize "Nicometer" to my needs, or perhaps others, too.
My main attention is to have a nicer user experience, easier presentation of the most important informations and some other gimmicks.
So stay tuned...
Here just a closer look of the "Drive page":
(https://ams03pap004files.storage.live.com/y4mCcb8j1lOhjVvJ0tcfzsa-zOqf8mGPuFEymojARNINeO7lFFecXVmVLmoluYRAAfIXK229MXt-WTjG0hR2rZWOJo-18F-LGrJAKIjpitR7tDvkgjxGTGC3GpN97785MdJJ9ZujilEI2nuPVE5DdNpO2xJdmvCQ-VwU2oFhOkAggRTeI0NBZNG_JP8jlQ_EQJm?width=1024&height=771&cropmode=none)
I've seen a problem with the code which is responsible to find the right gear lever position - P and E isn't working for me. But I have allready a solution. I found some other Bits in the same CAN-message which are decoding the position.
I'm not sure about the need of max an min temprature of the battery (under SoC - State of Charge). I guess I will remove them. When I'm following the temprature values in my CAN-messages, there are almost no changes over a longer period of time.
I've designed another graphic presentation of the "SoC" of the two battery packs and the total "SoC". It looks like the battery pack but with two halves.
There are some letters to distinguish between the different "modules" like "Battery Info", "Mains" and so on. I've removed some of them allready. Some others I have to remove.
---
So if you have some other suggestions or bugs you've seen, just write them down here.
I'll write a "to-do-list" and sort them after workload. ;)
If you want, you can make an option to reset fault messages of the Enerdel battery from the Nicometer ;)
Sakset fra "Vehicle_CAN_Bus_Guide_V3.0":
"
0BDiag_Cmd
ID: 745
Received by BMS
Periodic Rate: non-periodic (Special diagnostic command)
To clear all fault codes, send the following message (values in hex):
ID Data 0 Data1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7
745 03 14 FF 00 xx xx xx xx
(xx bytes are "don't care" and may be transmitted as 00 or not transmitted)
Upon successful clearing of fault codes, the BMS will transmit the following message :
ID Data 0 Data1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7
74D 03 54 FF 00 00 00 00 00
Notes:
Any faults that are presently active may be immediately set again by the BMS diagnostic executive.
Messages 745 and 74D are not called out in the dbc file, because they are special messages typically only used by a diagnostic tool.
"
( https://www.dropbox.com/s/pe4rl3crl9tbhps/Vehicle_CAN_Bus_Guide_V3.0.docx?dl=0 )
Sitat fra: Warlock på onsdag 29. mars 2023, klokken 18:09If you want, you can make an option to reset fault messages of the Enerdel battery from the Nicometer ;)
I've allready thought of that, but didn't used more time for investigations.
But since I'm knowing now that CommTool get a message after "Clear all Malf Codes" which is translated "Security passed", I suggested that there must be some kind of confirmation.
Fault Reset - noted ;)
Just some updates from the last days.
Since I have to fix my Think, too, I'm trying to find some smart solutions I can use later in the "Nicometer".
I used some houres the last days to get the programcode to look more tidy and deleted more "dead/unused code".
Overlaymenu is working now. There are five menuitems to choose between. It is controlled with one or two buttons. I have to figure out, what's best. The menuitem which is choosen has reversed text - black on white. The other menuitems are white on black.
My dream is to use a small joystick with button up, down, left right and middle. This would be genious and as I mentiod before, it would look like in a modern car.
My first "menuitem" is named "Battery". I created a picture in GIMP. It shows a 3D view of the (ENERDEL)battery. The battery is splittet in 16 modules, like the original battery. In front of the picture you can find two rectangles where the "StateOfCharge" of the left and the right part of the battery is showed.
Above the battery picture the "whole" StateOfCharge is showed.
Every module has the original number as it showes in ENERDEL documentation.
Beside the number I can show the voltage of the module or the temprature and so on. I have to figure out what looks best. Less informations at once are best! Or it becomes confusing.
I have startet to change the colour of a module if there are warnings or faults. So I can reverse the colour of the module from black to white. This is actually something I wanted to do for myself, since I have problems with one module. ;) So in future it will be easier to find a fault in "Nicometer".
I use the telegrams from CommTool. CommTool sends telegrams to get informations from the slaves and so on. In the "Nicometer" one CAN-message is configured to send telegrams. But it is not in use in the version we have now. So I use it now. There are many interessting telegrams in CommTool to get more information from the battery which normally aren't transfered on the CAN-bus.
Unfortunately I have no pictures right now. I mounted the small display in my car and use an old flat TV at home to see what I'm programming. I will try to take some useful pictures. ;)
The programcode has so many comments, now, that the size of the file is quite bigger than before. :D Loading of the file take a little bit longer, but not so much that somebody will recognize it.
Since I'm useing to new FONTS and some BMPs, now, it's necessary to download more files to the Duinomite, since the programcode is useing them.
By the way - I changed the start animation again. I took the original "THINK-logo" and converted it in GIMP. The Duinomite can only show Bitmaps (bmp) with 1Bit colour - black or white. ;D
Now, the original logo is showed in the beginning, than it's vanishing and the exclamation mark comes on again before the "CAN-configuration" is printed on the screen.
I will make a new video. ;)
Have a nice evening!
This just sound sooo cool 8)
Really looking forward to see what you are making :+1:
A little update, since I was/I am quiet busy fixing my Think.
Here is a video about the changes I did in the "Nicometer" program. I wrote some explanations in the description field.
You will see the different standard pages with some minor design changes - using symbols and graphic elements.
You will see the overlay menue and choosing an item and closing automatically if you don't choose an item.
You will see the battery info page with the 16 modules and two battery halfs (Enerdel).
Since I haven't connect my car to it (difficult since it's partially disassembled :D ) you can't see any values. Neither did I use/activate testvalues. It's possible since there is a subroutine already, but I didn't put inn other variables which I need for the battery info page.
How ever, the joystick control is working fine. I like it very much! All button signals are push/impulse signals. It's easier to override such signals in the program. Otherwise you're dependent to change a button position.
Looking very good! :+1:
I really like the battery screen you have drawn (has 5 and 6 swapped places?)
If you need to "fake" your car for testing, you can play back a grabbed file in SavvyCAN (and even add in more messages if you like) :)
Sitat fra: Warlock på mandag 10. april 2023, klokken 21:23Looking very good! :+1:
I really like the battery screen you have drawn (has 5 and 6 swapped places?)
If you need to "fake" your car for testing, you can play back a grabbed file in SavvyCAN (and even add in more messages if you like) :)
I saw first in the video that I swapped 5 & 6 ::)
Changed it at once. Now it's right. ;)
I thought about the possibility to record telegrams with SavvyCAN, but I didn't play back my record before.
Did you do that before?
Yeah, I've used SavvyCAN for "playback" just to simulate a car. It was very helpful to find which messages was necessary to start up a CAN (well actually LIN) controlled heater, and most of all to find out which messages was not necessary, just by taking them out of the playback-loop.
More recently I have used it with other projects just to see if builds of small controller-cards or new cheap hardware from Aliexpress is working the way I thought (ie. is capable of receiving any kind of message.) It is easier to do on the workbench than fiddling with it in a car. Just remember you might need to put in the bus termination resistor.
That's cool!
I recorded a lot and over a longer period of time before I started to disamble my car.
So I'll try to do that with my PCAN cable and a 120Ohm resistance, if necessary.
Nice! :)
Guys, I take a break from the forum for a year or two and you make wonders with my code!
I should have taken break long time ago!
bcx238h - the latest video is amazing!
I am back now and want to help - where do I find the latest code?
Should I put it on github so we can manage changes easier?
Sitat fra: BauDemo på torsdag 27. april 2023, klokken 08:14Guys, I take a break from the forum for a year or two and you make wonders with my code!
I should have taken break long time ago!
bcx238h - the latest video is amazing!
I am back now and want to help - where do I find the latest code?
Should I put it on github so we can manage changes easier?
Hello again!
I'm sorry for my extended pause, too. ;)
In the meantime I had to fix some other stuff at home. ::)
But fortunately I got my "new" RLEC which I want to install tomorrow. :)
I haven't published the code online. But I can do it. I'll come back to that when I'm ready...
I've moved my inputs/outputs installasjon to a smaller breadboard.
And I changed the connectors of my joystick. Now it will fit better in the car, too.
I started to build a 12V battery state of charge LED indicator with 8 LED's since I have so many electronic parts I have to build something with. :) I'll place it in the dashbord, too. After a while my Think will look like a small spaceship inside. ;D
CU soon...
I changed the bulb on one of the unused buttons with an RGB-led and made a 12V indicator
less than 11.9V -> RED
11.9V to 12.7V -> Orange
and over 12.7V -> Green
Works perfect for me, and looks integrated. The button press also makes the light glow brighter, and turn on the backlight on a Inside/Outside temperature display i mounted between the gear-selector and the coin/keys storage slot...
Sitat fra: Warlock på søndag 30. april 2023, klokken 15:12I changed the bulb on one of the unused buttons with an RGB-led and made a 12V indicator
less than 11.9V -> RED
11.9V to 12.7V -> Orange
and over 12.7V -> Green
Works perfect for me, and looks integrated. The button press also makes the light glow brighter, and turn on the backlight on a Inside/Outside temperature display i mounted between the gear-selector and the coin/keys storage slot...
That's a nice idea! Perhaps I consider your solution. ;)
I like the old fashion of a LED-bar. :D RGB came later ... after my time on school. ;D
Hello again!
I put the "newer Nicometer" code and the font- and bitmap-files in a zip-folder.
As usual I had to change the file-extension name from zip to txt.
Just download, change the extension name and unpack.
You will get the autorun.bas which everybody can open with notepad.
The two font-files can be opened with notepad, too.
The two logo-bitmaps can be opened with every normal picture viewer.
(https://ams03pap004files.storage.live.com/y4mmAzR2mBzXvfSAuyys6lRh3cMcZisT1jTJwTPyjpKZfI9S39fXzqVgB0Jh4ehGa3wALgMAzT1IGMmctGgb3_scDV47M-QGRJ1fDJicdpci7acS6zRdFxlQFXCVnLfIOemmLCeB7r7ZGZksfP1-k6RjxgdnptNUJIYs3ByV4y2QBIeHNaloQ5HmRd9TdF7rUUS?width=771&height=1024&cropmode=none)
As you can see on the picture you can see my hardwareconfiguration for this program.
The biggest change is the joystick for the menue-navigation.
I use manual signals to change between the different pages, since I can't use "autoscreen" function without a car. ;)
The code is full of comments. Unfortunately I wasn't consistent with use of english and norwegian explanations. Sorry for that! I hope there're no german phrases left. ::)
Some parts are not fully developed, like the battery-overview.
But all the other stuff is working ... so long.
Have fun exploring the changes... ;D
I have a yellow 2010 Think with zebra battery. Would I be able to use this setup to diagnose my battery charging problems?
Sitat fra: twirk på søndag 20. august 2023, klokken 18:58I have a yellow 2010 Think with zebra battery. Would I be able to use this setup to diagnose my battery charging problems?
Work in progress...but I'm definitely working with diagnostic functions. ;)
Hello guys!
I have done few small changes in the programcode.
I wrote a lot of comments and changed some variablenames to be more consistent.
The batterypage is displaying the three SoC values, now.
If somebody want to take a look, I uploaded the zip-file. Just change the extension from .txt to .zip as usual.
Aside from that I uploaded a pdf-file. It's a scan of the original Nicometer with some extra informations and a lot of comments/explanations.
Perhaps some of you always wanted to know more about the program structure and so on.
The autorun.bas in the zip-file can be opened with the normal texteditor, too.
There are a lot of comments/explanations, too.
Remember that I use a joystick with x- and y-axis and button to move around. The program is a little bit different.
ZEBRA-battery-drivers have to change the variable "_is_enerdel" to 0. Because of debugging, I change it manually.
I have to logg more telegrams with Savvy-CAN. I want to get more informations from the 16 battery modules. Since my battery is working fine, now, I can concentrate me more on the "Nicometer". :laugh:
Just two pictures of the Nicometer as it's now...no big differences! *Debug mode with random values*
(https://onedrive.live.com/embed?resid=1A3B2D16F7AEF36E%21352634&authkey=%21AHFgEqZ0wxQ8fYY&width=1024)
(https://onedrive.live.com/embed?resid=1A3B2D16F7AEF36E%21352633&authkey=%21AJqKjb_aaFNkO0k&width=1024)