Spaces:
Sleeping
Sleeping
Upload 5 files
Browse files
Diagnostics_data/System engineering document.txt
ADDED
@@ -0,0 +1,65 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
Wiper control system
|
2 |
+
Body control module (BCM) is near the infotainment module near the car's front side. It is an electronic control module that controls the functionality of the subsystems such as wiper control system, door lock mechanism, power windows etc. Wiper control system consists of mechanical wiper blade, wiper motor, which is electrical component, wiper control buttons which is attached to electrical switches. BCM takes driver input from the wiper control buttons and actuates the wiper motor which in turn moves the wiper blades up and down. For example, there are three buttons for wiper speed – low, medium, high. When the user clicks on the low button, BCM gets this signal from Input Pin 16. It then sends the low current value of 10 ampere to the wiper motor through Output pin 20. When user clicks on medium button, BCM sends current value of 20 ampere to the wiper motor Pin 1. When user clicks on high button, BCM sends current value of 30 ampere to the wiper motor Pin 1.
|
3 |
+
Terminal diagram:
|
4 |
+
|
5 |
+
DTC
|
6 |
+
DTC
|
7 |
+
Error text
|
8 |
+
FTB
|
9 |
+
DTC Priority
|
10 |
+
DTC Aging cycle
|
11 |
+
B202501
|
12 |
+
Wiper Motor WMT1 Error
|
13 |
+
General Electrical Failure
|
14 |
+
2
|
15 |
+
10
|
16 |
+
B202701
|
17 |
+
|
18 |
+
Wiper Motor WMT1 Warning
|
19 |
+
General Electrical Failure
|
20 |
+
2
|
21 |
+
10
|
22 |
+
B202901
|
23 |
+
Wiper Switch open circuit
|
24 |
+
Open circuit error in wiper button circuit
|
25 |
+
2
|
26 |
+
10
|
27 |
+
|
28 |
+
1. B202501
|
29 |
+
Description: The DTC B202501 indicates an error specifically related to the WMT1 (Wiper Motor) within the vehicle's BCM. It suggests a fault or malfunction in the wiper motor circuit, which is responsible for controlling the operation of the vehicle's windshield wipers.
|
30 |
+
Possible Causes: The B202501 DTC can be triggered by,
|
31 |
+
1. Faulty Wiper Motor: The wiper motor itself may be defective or experiencing internal malfunctions, such as a short circuit or mechanical failure.
|
32 |
+
2. Wiring or Connector Issues: Faulty wiring harnesses, damaged connectors, or loose connections related to the wiper motor can cause this error.
|
33 |
+
3. Power Supply Problems: Insufficient power supply to the wiper motor, such as low voltage or a disrupted electrical signal, can contribute to this fault. Ideal supply voltage should be 24 V.
|
34 |
+
4. Ground problems: This issue can occur if the ground pin of wiper motor has loose connection.
|
35 |
+
5. This DTC can occur if B202901 DTC related to wiper switch open circuit occurs.
|
36 |
+
|
37 |
+
Symptoms: When the B202501 DTC is present, the vehicle may exhibit several symptoms, including:
|
38 |
+
1. Inoperative Windshield Wipers: The wipers may not work at all, failing to respond when the wiper control is activated.
|
39 |
+
2. Erratic Wiper Operation: The wipers may operate intermittently or erratically, moving at incorrect speeds or with unpredictable behavior.
|
40 |
+
3. Unusual Noises: The wiper motor may produce abnormal noises during operation, indicating a potential fault.
|
41 |
+
|
42 |
+
Diagnostic Steps: To diagnose and resolve the B202501 DTC, the following steps may be taken:
|
43 |
+
1. Visual Inspection: The wiper motor and its associated wiring and connectors should be visually inspected for any visible signs of damage, corrosion, or loose connections.
|
44 |
+
2. Electrical Testing: Using a diagnostic scan tool, electrical tests can be performed to measure voltage, current, and resistance in the wiper motor circuit to identify any abnormalities.
|
45 |
+
3. Component Replacement: If a faulty wiper motor or other defective components are identified, they should be replaced with new, functioning parts.
|
46 |
+
4. Wiring Repair: If wiring or connector issues are found, repairs or replacements should be made to ensure proper electrical connectivity.
|
47 |
+
|
48 |
+
2. B202701
|
49 |
+
Description: The DTC B202701 indicates a warning specifically related to the WMT1 (Wiper Motor) within the vehicle's BCM. It suggests a potential issue or anomaly in the wiper motor circuit, which is responsible for controlling the operation of the vehicle's windshield wipers.
|
50 |
+
Possible Causes: The B202701 DTC can be triggered by,
|
51 |
+
1. Wiper Motor Malfunction: The wiper motor may be experiencing irregularities or inconsistencies in its performance, which trigger the warning.
|
52 |
+
2. Electrical Circuits Issues: Faulty electrical circuits connected to the wiper motor, such as damaged wiring, loose connectors, or disrupted signals, can lead to this warning.
|
53 |
+
3. Power Supply Problems: Insufficient power supply or fluctuations in the electrical system that powers the wiper motor can contribute to this warning.
|
54 |
+
Symptoms: When the B202701 DTC is present, the vehicle may exhibit several symptoms or warning signs, including:
|
55 |
+
1. Warning Indicator: A warning light or message may appear on the vehicle's instrument cluster or dashboard, indicating an issue with the wiper motor.
|
56 |
+
2. Inconsistent Wiper Operation: The windshield wipers may operate sporadically or erratically, deviating from the desired or expected behavior.
|
57 |
+
3. Intermittent Functioning: The wipers may work inconsistently, functioning correctly at times and then suddenly stopping or pausing unexpectedly.
|
58 |
+
Diagnostic Steps: To diagnose and resolve the B202701 DTC warning, the following steps may be taken:
|
59 |
+
1. Visual Inspection: A visual inspection of the wiper motor, wiring, and connectors should be conducted to check for any visible signs of damage, loose connections, or corrosion.
|
60 |
+
2. Electrical Testing: Specialized diagnostic equipment can be used to perform electrical tests, such as measuring voltage, current, and resistance in the wiper motor circuit, to identify any irregularities.
|
61 |
+
3. Component Evaluation: The wiper motor and related components should be evaluated to determine if any parts are malfunctioning or require replacement.
|
62 |
+
4. Wiring and Connector Examination: If wiring or connector issues are detected, repairs or replacements should be carried out to restore proper electrical connectivity.
|
63 |
+
5. Wiper button: Check wiper button for internal damage, sticky connection.
|
64 |
+
|
65 |
+
|
faiss_index_diagnostics_RCV/index.faiss
ADDED
Binary file (73.8 kB). View file
|
|
faiss_index_diagnostics_RCV/index.pkl
ADDED
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
1 |
+
version https://git-lfs.github.com/spec/v1
|
2 |
+
oid sha256:27a08e05d2d998807f79cef5117f4814a089c177fda75d6726d7ebd58d5e58b7
|
3 |
+
size 7300
|
requirements.txt
ADDED
@@ -0,0 +1,112 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
aiohttp==3.8.4
|
2 |
+
aiosignal==1.3.1
|
3 |
+
altair==5.0.1
|
4 |
+
anyio==3.7.0
|
5 |
+
argilla==1.10.0
|
6 |
+
async-timeout==4.0.2
|
7 |
+
attrs==23.1.0
|
8 |
+
backoff==2.2.1
|
9 |
+
blinker==1.6.2
|
10 |
+
cachetools==5.3.1
|
11 |
+
certifi==2023.5.7
|
12 |
+
cffi==1.15.1
|
13 |
+
chardet==5.1.0
|
14 |
+
charset-normalizer==3.1.0
|
15 |
+
click==8.1.3
|
16 |
+
clickhouse-connect==0.5.22
|
17 |
+
colorama==0.4.6
|
18 |
+
commonmark==0.9.1
|
19 |
+
cryptography==41.0.1
|
20 |
+
dataclasses-json==0.5.8
|
21 |
+
decorator==5.1.1
|
22 |
+
Deprecated==1.2.14
|
23 |
+
dotenv==0.0.5
|
24 |
+
et-xmlfile==1.1.0
|
25 |
+
exceptiongroup==1.1.1
|
26 |
+
faiss-cpu==1.7.4
|
27 |
+
filetype==1.2.0
|
28 |
+
frozenlist==1.3.3
|
29 |
+
gitdb==4.0.10
|
30 |
+
GitPython==3.1.31
|
31 |
+
greenlet==2.0.2
|
32 |
+
h11==0.14.0
|
33 |
+
httpcore==0.16.3
|
34 |
+
httpx==0.23.3
|
35 |
+
idna==3.4
|
36 |
+
importlib-metadata==6.7.0
|
37 |
+
Jinja2==3.1.2
|
38 |
+
joblib==1.2.0
|
39 |
+
jsonschema==4.17.3
|
40 |
+
langchain==0.0.206
|
41 |
+
langchainplus-sdk==0.0.16
|
42 |
+
lxml==4.9.2
|
43 |
+
lz4==4.3.2
|
44 |
+
Markdown==3.4.3
|
45 |
+
MarkupSafe==2.1.3
|
46 |
+
marshmallow==3.19.0
|
47 |
+
marshmallow-enum==1.5.1
|
48 |
+
monotonic==1.6
|
49 |
+
msg-parser==1.2.0
|
50 |
+
multidict==6.0.4
|
51 |
+
mypy-extensions==1.0.0
|
52 |
+
nltk==3.8.1
|
53 |
+
numexpr==2.8.4
|
54 |
+
numpy==1.23.5
|
55 |
+
olefile==0.46
|
56 |
+
openai==0.27.8
|
57 |
+
openapi-schema-pydantic==1.2.4
|
58 |
+
openpyxl==3.1.2
|
59 |
+
packaging==23.1
|
60 |
+
pandas==1.5.3
|
61 |
+
pdf2image==1.16.3
|
62 |
+
pdfminer.six==20221105
|
63 |
+
Pillow==9.5.0
|
64 |
+
protobuf==4.23.3
|
65 |
+
pyarrow==12.0.1
|
66 |
+
pycparser==2.21
|
67 |
+
pydantic==1.10.9
|
68 |
+
pydeck==0.8.1b0
|
69 |
+
Pygments==2.15.1
|
70 |
+
Pympler==1.0.1
|
71 |
+
pypandoc==1.11
|
72 |
+
pyrsistent==0.19.3
|
73 |
+
python-dateutil==2.8.2
|
74 |
+
python-docx==0.8.11
|
75 |
+
python-magic==0.4.27
|
76 |
+
python-magic-bin==0.4.14
|
77 |
+
python-pptx==0.6.21
|
78 |
+
pytz==2023.3
|
79 |
+
pytz-deprecation-shim==0.1.0.post0
|
80 |
+
PyYAML==6.0
|
81 |
+
regex==2023.6.3
|
82 |
+
requests==2.31.0
|
83 |
+
rfc3986==1.5.0
|
84 |
+
rich==13.0.1
|
85 |
+
six==1.16.0
|
86 |
+
smmap==5.0.0
|
87 |
+
sniffio==1.3.0
|
88 |
+
SQLAlchemy==2.0.16
|
89 |
+
streamlit==1.23.1
|
90 |
+
streamlit-chat==0.0.2.2
|
91 |
+
tabulate==0.9.0
|
92 |
+
tenacity==8.2.2
|
93 |
+
tiktoken==0.4.0
|
94 |
+
toml==0.10.2
|
95 |
+
toolz==0.12.0
|
96 |
+
tornado==6.3.2
|
97 |
+
tqdm==4.65.0
|
98 |
+
typer==0.9.0
|
99 |
+
typing-inspect==0.9.0
|
100 |
+
typing_extensions==4.6.3
|
101 |
+
tzdata==2023.3
|
102 |
+
tzlocal==4.3.1
|
103 |
+
unstructured==0.7.6
|
104 |
+
urllib3==2.0.3
|
105 |
+
validators==0.20.0
|
106 |
+
watchdog==3.0.0
|
107 |
+
wrapt==1.14.1
|
108 |
+
xlrd==2.0.1
|
109 |
+
XlsxWriter==3.1.2
|
110 |
+
yarl==1.9.2
|
111 |
+
zipp==3.15.0
|
112 |
+
zstandard==0.21.0
|
streamlit_base.py
ADDED
@@ -0,0 +1,77 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
import langchain
|
2 |
+
from langchain.embeddings.openai import OpenAIEmbeddings
|
3 |
+
# from langchain.vectorstores import Chroma
|
4 |
+
from langchain.vectorstores import FAISS
|
5 |
+
from langchain.text_splitter import CharacterTextSplitter
|
6 |
+
from langchain.llms import OpenAI
|
7 |
+
from langchain.chains import VectorDBQA
|
8 |
+
from langchain.chains import RetrievalQA
|
9 |
+
from langchain.document_loaders import DirectoryLoader
|
10 |
+
from langchain.chains import ConversationalRetrievalChain
|
11 |
+
from langchain.memory import ConversationBufferMemory
|
12 |
+
from langchain.evaluation.qa import QAGenerateChain
|
13 |
+
import magic
|
14 |
+
import os
|
15 |
+
import streamlit as st
|
16 |
+
from streamlit_chat import message
|
17 |
+
|
18 |
+
st.title("AI Chatbot")
|
19 |
+
|
20 |
+
if 'responses' not in st.session_state:
|
21 |
+
st.session_state['responses'] = ["How can I assist you?"]
|
22 |
+
|
23 |
+
if 'requests' not in st.session_state:
|
24 |
+
st.session_state['requests'] = []
|
25 |
+
|
26 |
+
openai_api_key = os.getenv("OPENAI_API_KEY", "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")
|
27 |
+
embeddings = OpenAIEmbeddings(openai_api_key=openai_api_key)
|
28 |
+
new_db = FAISS.load_local("faiss_index_diagnostics_RCV", embeddings)
|
29 |
+
llm = OpenAI(openai_api_key=openai_api_key, temperature=0.0)
|
30 |
+
|
31 |
+
# if 'buffer_memory' not in st.session_state:
|
32 |
+
memory= ConversationBufferMemory(memory_key="chat_history", return_messages=True)
|
33 |
+
retriever = new_db.as_retriever()
|
34 |
+
chain = ConversationalRetrievalChain.from_llm(llm=llm, chain_type="stuff", memory= memory,retriever=retriever, verbose=False)
|
35 |
+
|
36 |
+
# container for chat history
|
37 |
+
response_container = st.container()
|
38 |
+
# container for text box
|
39 |
+
textcontainer = st.container()
|
40 |
+
|
41 |
+
|
42 |
+
with textcontainer:
|
43 |
+
query = st.text_input(label="Please Enter Your Prompt Here: ", placeholder="Ask me")
|
44 |
+
if query:
|
45 |
+
with st.spinner("Generating..."):
|
46 |
+
# conversation_string = get_conversation_string()
|
47 |
+
# st.code(conversation_string)
|
48 |
+
# refined_query = query_refiner(conversation_string, query)
|
49 |
+
# st.subheader("Refined Query:")
|
50 |
+
# st.write(refined_query)
|
51 |
+
# context = find_match(refined_query)
|
52 |
+
# print(context)
|
53 |
+
response = chain.run(query)
|
54 |
+
st.session_state.requests.append(query)
|
55 |
+
st.session_state.responses.append(response)
|
56 |
+
with response_container:
|
57 |
+
if st.session_state['responses']:
|
58 |
+
|
59 |
+
for i in range(len(st.session_state['responses'])):
|
60 |
+
message(st.session_state['responses'][i],key=str(i))
|
61 |
+
if i < len(st.session_state['requests']):
|
62 |
+
message(st.session_state["requests"][i], is_user=True,key=str(i)+ '_user')
|
63 |
+
|
64 |
+
# with st.expander('Message history'):
|
65 |
+
# st.info(memory.buffer)
|
66 |
+
|
67 |
+
|
68 |
+
|
69 |
+
|
70 |
+
|
71 |
+
|
72 |
+
|
73 |
+
|
74 |
+
|
75 |
+
|
76 |
+
|
77 |
+
|