Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What do I connect to vref? #2

Closed
delchrys opened this issue Apr 17, 2017 · 13 comments
Closed

What do I connect to vref? #2

delchrys opened this issue Apr 17, 2017 · 13 comments

Comments

@delchrys
Copy link

In the schematics vref is named. But what should I connect it to?
And do you have some better pictures of your breadboard setup or a parts list from Farnell or something?

@bbqkees
Copy link
Owner

bbqkees commented Apr 17, 2017

You only need to connect every line that is named U_Ref. No external connections.
It is an internal reference voltage.

For a picture of the breadboard see the Documentation page again, I added one.

I do not have a parts list, there are only a few parts in the schematic, it is not that difficult.

@delchrys
Copy link
Author

So the u refs are connected to each other or to the lm393?

@bbqkees
Copy link
Owner

bbqkees commented Apr 17, 2017

Draw a line from each U_Ref to the other and remove the label, maybe that will make it more clear.
The labels are there just so you do not have to show crossing wires.

@delchrys
Copy link
Author

Ah ok I get it. Now it's clear for me thanks. Will buildo it soon to test if it works.

@bbqkees
Copy link
Owner

bbqkees commented Apr 17, 2017

So now its clear I will close the issue.

@bbqkees bbqkees closed this as completed Apr 17, 2017
@delchrys
Copy link
Author

Sorry bbqkees i have another question. I see you used all through hole components. Which diodes (schottky) you used instead of a smd Bat54s+ and BAT46 package??

@bbqkees
Copy link
Owner

bbqkees commented Apr 18, 2017

You can probably use 1N4148 diodes for all.
I used two different diode types (1N4148 and the other of unknown type but identical or similar), but only because I had those at hand.
The BAT46 diode is available as through-hole.

There is also a big capacitor on the breadboard which is not present in the schematic, I added this to increase stability, but this is not mandatory. Also if you want to build the transmitter part with through hole components you can replace the BC847 transistor with f.i. a BC337.

@delchrys
Copy link
Author

delchrys commented May 8, 2017

another question,
i'm not that electric but i think i can make it work, but does the lm393 also need vcc and ground connected?? on pin 8 and 4??? maybe that's why my circuit isn't working properly

@bbqkees
Copy link
Owner

bbqkees commented May 8, 2017

Yes you need to connect those pins too, otherwise the chip itself has no power.

@delchrys
Copy link
Author

delchrys commented May 8, 2017

thanks will do that, stupid mistake

@delchrys
Copy link
Author

delchrys commented May 8, 2017

Yes it works now. Thanks for the help.
Is it possible to get more data from the EMS bus??? In the documentation i read a lot of other info, but how can i find out if this is all the data my Nefit spits out?
Maybe a RAW read of the data message????

@delchrys
Copy link
Author

question, how did you figure out the addresses, can't seem to find any similar entry's in the wiki.
for instance 0x08,0x18,0x12,0x02,

@bbqkees
Copy link
Owner

bbqkees commented May 11, 2017

So if you read this page VERY carefully:
https://emswiki.thefischer.net/doku.php?id=wiki:ems:telegramme
You see that the offset for the first databyte is 5. So the first databyte is at the 5th byte of the message.

Now check the UBAMonitorFast table.
You can see f.i. 08 | 00 | 18 | 23 | 1 | ASCII | Service-Code 1. Zeichen
Sender: 0x08
Type: 0x18
Byte offset from start: 23 DEC = 0x17
Description: Service Code 1st sign.

Now note the sequence of your question: 0x08 | 0x18 | 0x12 | 0x02 | //#9 8 status code 1st letter.
Sender: 0x08
Type: 0x18
Byte offset from first databyte: 0x12 (remember it is +5 bytes from the start so 0x12+5=0x17)
Datatype: 0x02 = ASCII (Only used in the sketch)
Description: //#9 8 status code 1st letter

So if you check the other parameters in the sketch you see that most of them are just a decoding of the UBAMonitorFast and UBAMonitorWWMessage message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants