diff --git a/Canbus_Support2.md b/Canbus_Support2.md
index 92815f3..ed59435 100644
--- a/Canbus_Support2.md
+++ b/Canbus_Support2.md
@@ -2,7 +2,7 @@
 title: CanBus Support
 description: 
 published: true
-date: 2020-12-16T23:45:53.186Z
+date: 2021-08-10T13:29:19.688Z
 tags: 
 editor: markdown
 dateCreated: 2020-12-15T21:58:51.731Z
@@ -75,7 +75,7 @@ The following PIDs are supports by by the OBD port
 
 When using Bit-Encoded-Notation, quantities like C4 means bit 4 from data byte C. Each bit is numerated from 0 to 7, so 7 is the most significant bit and 0 is the least significant bit (See below).
 
-![bit_notation1.png](/bit_notation1.png)
+![bit_notation1.png](/img/CAN/bit_notation1.png)
 
 ## MODE 01
 
@@ -83,7 +83,7 @@ When using Bit-Encoded-Notation, quantities like C4 means bit 4 from data byte C
 {.is-info}
 
 
-![pid_support_list.png](/pid_support_list.png)
+![pid_support_list.png](/img/CAN/pid_support_list.png)
 
 ## MODE 9
 
@@ -93,7 +93,7 @@ Mode 9 support is coming soon!
 
 Speeduino responds to the Mode 22 request for the following PID: 
 
-![mode22_pid_support.png](/mode22_pid_support.png)
+![mode22_pid_support.png](/img/CAN/mode22_pid_support.png)
 
 ## Bitwise encoded PIDs
 
@@ -104,7 +104,7 @@ A request for this PID returns 4 bytes of data (Big-endian). Each bit, from MSB
 
 For example, if the car response is BE1FA813, it can be decoded like this:
 
-![bit_encoded1.png](/bit_encoded1.png)
+![bit_encoded1.png](/img/CAN/bit_encoded1.png)
 
 So, supported PIDs are: 01, 03, 04, 05, 06, 07, 0C, 0D, 0E, 0F, 10, 11, 13, 15, 1C, 1F and 20 
 
@@ -121,14 +121,14 @@ CAN bus may also be used for communication beyond the standard OBD messages. Phy
 The functional PID query is sent to the vehicle on the CAN bus at ID 7DFh, using 8 data bytes. 
 The bytes are:
 
-![11bit_query.png](/11bit_query.png)
+![11bit CAN query](/img/CAN/11bit_query.png)
 
 #### Response
 
 The vehicle responds to the PID query on the CAN bus with message IDs that depend on which module responded. Typically the engine or main ECU responds at ID 7E8h. Other modules, like the hybrid controller or battery controller in a Prius, respond at 07E9h, 07EAh, 07EBh, etc. These are 8h higher than the physical address the module responds to. Even though the number of bytes in the returned value is variable, the message uses 8 data bytes regardless (CAN bus protocol form Frameformat with 8 data bytes). 
 The bytes are:
 
-![11bit_response.png](/11bit_response.png)
+![11bit CAN response](/img/CAN/11bit_response.png)