Automotive Linux Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== Meeting Notes for AGL Connectivity Expert Group =====

Meetings of the Connectivity EG are held every other Thursday. The upcoming schedule can be found on the [[https://lists.automotivelinux.org/g/agl-dev-community/calendar | project calendar]]. 

Conference Information:

https://zoom.us/j/151930034?pwd=OEt1VnhIUmdQZEwwTzE2cHdCYzZTZz09

Meeting ID: 151 930 034
Passcode: 460200
Find your local number: https://zoom.us/u/ameRude4a

-------

NOTE:  Starting March 12, 2023 the Connectivity EG meetings have been held during the App FW EG Meeting. Please refer to the [[eg-app-fw:meetings|meeting minutes]] for details. 

==== February 9, 2023 ====
Attendees: Walt, Scott, Jan-Simon, 

   * CAN/ Vehicle Signaling
     * 1/26
       * Kuksa.val running in the CES demo and is up to date in the Needlefish and Octopus releases. 


   * Bluetooth
     * No update


   * Ref HW
     * No update

 
   * 5G/LTE module and Telephony
     * No update


   * New:
     * Off-topic - discussed Yocto CVE checker and whether the members are interested in using it. Would need to back port to kirkstone and dunfell once the upstream work is completed. 

     * Discussed the AVL / TU Graz use case. Scott will document the CES build instructions on the doc site. Suggested using the Flutter Cluster demo because it has a larger number of signals that are changing. Update 2/9 - Scott got Markus unblocked. Still needs to update documentation. 


==== January 26, 2023 ====
Attendees: Walt, Scott, Jan-Simon, Markus Wolf (AVL), Andrea Pferscher (TU Graz)


   * CAN/ Vehicle Signaling
     * 1/26
       * Kuksa.val running in the CES demo and is up to date in the Needlefish and Octopus releases. 


   * Bluetooth
     * No update


   * Ref HW
     * No update

 
   * 5G/LTE module and Telephony
     * No update


   * New:
     * Radio tuner API added back using gRPC and is included in Needlefish and Octopus. 
     * Discussed the AVL / TU Graz use case. Scott will document the CES build instructions on the doc site. Suggested using the Flutter Cluster demo because it has a larger number of signals that are changing. 
     * 

==== January 12, 2023 ====
Attendees: Walt, Scott 


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine.
     * 7/28
       * Kuksa.val improved gRPC is starting to show up in their repo along with the refactoring of their repo that Scott previously discussed with Sebastian. Will decide if it goes into a Needlefish release point release or directly into Octopus. 
     * 8/11
       * Kuksa.val gRPC work looks like it is complete upstream. Scott looking for an official release and will try to join their call next week.  
     * 8/25
       * Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year. 
     * 9/8
       * Getting ready for training class on September 29 and ELCE
     * 9/21
       * Uploaded fixes for kuksa_viss_client (cert issue w/ python, cmd2 utility fix) - master and needlefish
       * Likely update kuksa to get grpc
     * 10/6
       * Scott looking at bumping kuksa.val to the latest tag or head of master. 
     * 11/3
       * Kuksa.val was bumped to latest tag on AGL/master and Needlefish 
     * 12/15
       * Kuksa.val running in the CES demo. 


   * Bluetooth
     * No update


   * Ref HW
     * No update

 
   * 5G/LTE module and Telephony
     * No update


New:


==== December 15, 2022 ====
Attendees: Walt, Jan-Simon, Scott 

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update
     * 9/22
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine.
     * 7/28
       * Kuksa.val improved gRPC is starting to show up in their repo along with the refactoring of their repo that Scott previously discussed with Sebastian. Will decide if it goes into a Needlefish release point release or directly into Octopus. 
     * 8/11
       * Kuksa.val gRPC work looks like it is complete upstream. Scott looking for an official release and will try to join their call next week.  
     * 8/25
       * Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year. 
     * 9/8
       * Getting ready for training class on September 29 and ELCE
     * 9/21
       * Uploaded fixes for kuksa_viss_client (cert issue w/ python, cmd2 utility fix) - master and needlefish
       * Likely update kuksa to get grpc
     * 10/6
       * Scott looking at bumping kuksa.val to the latest tag or head of master. 
     * 11/3
       * Kuksa.val was bumped to latest tag on AGL/master and Needlefish 
     * 12/15
       * Kuksa.val running in the CES demo. 


   * Bluetooth
     * No update


   * Ref HW
     * No update

 
   * 5G/LTE module and Telephony
     * No update


New:


==== November 3, 2022 ====
Attendees: Walt, Jan-Simon, Scott 

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update
     * 9/22
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine.
     * 7/28
       * Kuksa.val improved gRPC is starting to show up in their repo along with the refactoring of their repo that Scott previously discussed with Sebastian. Will decide if it goes into a Needlefish release point release or directly into Octopus. 
     * 8/11
       * Kuksa.val gRPC work looks like it is complete upstream. Scott looking for an official release and will try to join their call next week.  
     * 8/25
       * Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year. 
     * 9/8
       * Getting ready for training class on September 29 and ELCE
     * 9/21
       * Uploaded fixes for kuksa_viss_client (cert issue w/ python, cmd2 utility fix) - master and needlefish
       * Likely update kuksa to get grpc
     * 10/6
       * Scott looking at bumping kuksa.val to the latest tag or head of master. 
     * 11/3
       * Kuksa.val was bumped to latest tag on AGL/master and Needlefish 


   * Bluetooth
     * No update


   * Ref HW
     * No update

 
   * 5G/LTE module and Telephony
     * No update


New:



==== October 6, 2022 ====
Attendees: Walt, Paul, Scott 

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update
     * 9/22
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine.
     * 7/28
       * Kuksa.val improved gRPC is starting to show up in their repo along with the refactoring of their repo that Scott previously discussed with Sebastian. Will decide if it goes into a Needlefish release point release or directly into Octopus. 
     * 8/11
       * Kuksa.val gRPC work looks like it is complete upstream. Scott looking for an official release and will try to join their call next week.  
     * 8/25
       * Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year. 
     * 9/8
       * Getting ready for training class on September 29 and ELCE
     * 9/21
       * Uploaded fixes for kuksa_viss_client (cert issue w/ python, cmd2 utility fix) - master and needlefish
       * Likely update kuksa to get grpc
     * 10/6
       * Scott looking at bumping kuksa.val to the latest tag or head of master. 


   * Bluetooth
     * No update


   * Ref HW
     * No update

 
   * 5G/LTE module and Telephony
     * No update


New:


==== September 22, 2022 ====
Attendees: Jan-Simon, Scott, Ayush Kumar, 

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update
     * 9/22
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine.
     * 7/28
       * Kuksa.val improved gRPC is starting to show up in their repo along with the refactoring of their repo that Scott previously discussed with Sebastian. Will decide if it goes into a Needlefish release point release or directly into Octopus. 
     * 8/11
       * Kuksa.val gRPC work looks like it is complete upstream. Scott looking for an official release and will try to join their call next week.  
     * 8/25
       * Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year. 
     * 9/8
       * Getting ready for training class on September 29 and ELCE
     * 9/21
       * Uploaded fixes for kuksa_viss_client (cert issue w/ python, cmd2 utility fix) - master and needlefish
       * Likely update kuksa to get grpc


   * Bluetooth
     * No update


   * Ref HW
     * No update

 
   * 5G/LTE module and Telephony
     * No update


New:


==== September 8, 2022 ====
Attendees: Walt, Scott, Shubkam, Shruti

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine.
     * 7/28
       * Kuksa.val improved gRPC is starting to show up in their repo along with the refactoring of their repo that Scott previously discussed with Sebastian. Will decide if it goes into a Needlefish release point release or directly into Octopus. 
     * 8/11
       * Kuksa.val gRPC work looks like it is complete upstream. Scott looking for an official release and will try to join their call next week.  
     * 8/25
     * Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year. 
     * 9/8
     * Getting ready for training class on September 29 and ELCE
     * 

   * Bluetooth
     * No update


   * Ref HW
     * No update

 

   * 5G/LTE module and Telephony
     * No update

New:


==== August 25 2022 ====
Attendees: Walt, Scott, Jan-Simon

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine.
     * 7/28
       * Kuksa.val improved gRPC is starting to show up in their repo along with the refactoring of their repo that Scott previously discussed with Sebastian. Will decide if it goes into a Needlefish release point release or directly into Octopus. 
     * 8/11
       * Kuksa.val gRPC work looks like it is complete upstream. Scott looking for an official release and will try to join their call next week.  
     * 8/25
     * Kuksa.val gRPC work landed. Latest version needs to be updated in our builds. gRPC conversion on our side will be later in the year. 

   * Bluetooth
     * No update


   * Ref HW
     * No update

 

   * 5G/LTE module and Telephony
     * No update

New:



==== August 11 2022 ====
Attendees: Walt, Jan-Simon, Scott, Aakash 

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine.
     * 7/28
       * Kuksa.val improved gRPC is starting to show up in their repo along with the refactoring of their repo that Scott previously discussed with Sebastian. Will decide if it goes into a Needlefish release point release or directly into Octopus. 
     * 8/11
       * Kuksa.val gRPC work looks like it is complete upstream. Scott looking for an official release and will try to join their call next week.  

   * Bluetooth
     * No update


   * Ref HW
     * No update

 

   * 5G/LTE module and Telephony
     * No update

New:




==== July 28, 2022 ====
Attendees: Walt, Jan-Simon, Scott, Bernard 

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine.
     * 7/28
       * Kuksa.val improved gRPC is starting to show up in their repo along with the refactoring of their repo that Scott previously discussed with Sebastian. Will decide if it goes into a Needlefish release point release or directly into Octopus.  

   * Bluetooth
     * No update


   * Ref HW
     * No update

 

   * 5G/LTE module and Telephony
     * No update

New:




==== July 14, 2022 ====
Attendees: Walt, Jan-Simon, Scott 

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine. 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 
     * 1/13 - Bluetooth done for Marlin, settings app still WIP for networking. 
     * 1/27 - No update for Bluetooth. Connman wrapper is ready to be pushed which will fix the settings app. 
     * 2/10 - The Connman wrapper has been merged. There is a known issue with BLuetooth start up requiring a manual rfkilll to get running on master (SPEC-4253). Scott looking at fixing that. 

   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 
     * 1/27
       * Still a WIP. Scott thinks maybe he can use the same approach that he used for Connmamn to wrap ofono. Most likely does not happen for Marlin initial release. 
     * 2/10
       * Still a WP. Scott may stub out the calls so at least the apps come up an run even if it is not connected to anything on the back end. 

New:
   * Discussed Speech rec and Alexa possibilities. Richard will ask about creating and maintaining an Yocto layer internally. Alexa Auto SDK switched to Conan. (conan.io)
   * Open source engine vosk 




==== June 2, 2022 ====
Attendees: Walt, Jan-Simon, Scott 

   * ACAIS V2C Demo - Chih-Ming 
     * 6/1
       * No update


   * CAN/ Vehicle Signaling
     * 6/1
       * Scott has kuksa.val and the VIS connected up to the steering wheel for LIN on the green machine. 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 
     * 1/13 - Bluetooth done for Marlin, settings app still WIP for networking. 
     * 1/27 - No update for Bluetooth. Connman wrapper is ready to be pushed which will fix the settings app. 
     * 2/10 - The Connman wrapper has been merged. There is a known issue with BLuetooth start up requiring a manual rfkilll to get running on master (SPEC-4253). Scott looking at fixing that. 

   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 
     * 1/27
       * Still a WIP. Scott thinks maybe he can use the same approach that he used for Connmamn to wrap ofono. Most likely does not happen for Marlin initial release. 
     * 2/10
       * Still a WP. Scott may stub out the calls so at least the apps come up an run even if it is not connected to anything on the back end. 

New:
   * Discussed Speech rec and Alexa possibilities. Richard will ask about creating and maintaining an Yocto layer internally. Alexa Auto SDK switched to Conan. (conan.io)
   * Open source engine vosk 



==== April 21, 2022 ====
Attendees: Walt, Jan-Simon, 

   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 
     * 12/2
       * Demo was shown internally yesterday and Damiano said they showed good progress. Will try to show a demo at the next V2C Eg meeting. 
     * 12/16
       * AICAS showed a demo of their work at Monday's V2C call. Not on this call today. 
     * 1/13
       * No AICAS
     * 1/27
       * Making slow progress due to having other tasks that are higher priority.  Chih-Ming has a [[https://www.youtube.com/watch?v=00_23cQOmCI | video of a partner]] using their solution on an NXP board.
     * 2/10
       * Working on their demo some more. Discussed which version of AGL to port to and we suggested that they use Marlin since they will be creating new services and they should not waste their time adapting to the old App FW and binders. 
       * Discussed which NXP board they should use because we do not have a BSP available for the NXP Gold Box (S32G-based). No known Yocto layer for the S32G. 
     * 2/24
       * No AICAS


   * CAN/ Vehicle Signaling
     * 2/10
       * Kuksa.val is building locally for Scott. gRPC support is problematic on the latest version due to known issues upstream with Yocto. Trying to get vehicle speed and working with Web Sockets to now. 
     * 3/10
       * Scott has the kuksa.val server building, booting up, and starting. Going to test python client which is used for their CAN messaging via WebSockets. Subscription API is missing things like notification on a range of values or only when a change of value is detected.  Noted that this is a reference implementation of the W3C spec. gRPC implementation does not have subscription implemented at all (only set and get). 
     * 3/24
       * We will have the kuksa.val building and running with their VISS API for Marlin. 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 
     * 1/13 - Bluetooth done for Marlin, settings app still WIP for networking. 
     * 1/27 - No update for Bluetooth. Connman wrapper is ready to be pushed which will fix the settings app. 
     * 2/10 - The Connman wrapper has been merged. There is a known issue with BLuetooth start up requiring a manual rfkilll to get running on master (SPEC-4253). Scott looking at fixing that. 

   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 
     * 1/27
       * Still a WIP. Scott thinks maybe he can use the same approach that he used for Connmamn to wrap ofono. Most likely does not happen for Marlin initial release. 
     * 2/10
       * Still a WP. Scott may stub out the calls so at least the apps come up an run even if it is not connected to anything on the back end. 

New:
   * Discussed Speech rec and Alexa possibilities. Richard will ask about creating and maintaining an Yocto layer internally. Alexa Auto SDK switched to Conan. (conan.io)
   * Open source engine vosk 




==== March 24, 2022 ====
Attendees: Walt, Jan-Simon, Scott, Richard, Bernard

   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 
     * 12/2
       * Demo was shown internally yesterday and Damiano said they showed good progress. Will try to show a demo at the next V2C Eg meeting. 
     * 12/16
       * AICAS showed a demo of their work at Monday's V2C call. Not on this call today. 
     * 1/13
       * No AICAS
     * 1/27
       * Making slow progress due to having other tasks that are higher priority.  Chih-Ming has a [[https://www.youtube.com/watch?v=00_23cQOmCI | video of a partner]] using their solution on an NXP board.
     * 2/10
       * Working on their demo some more. Discussed which version of AGL to port to and we suggested that they use Marlin since they will be creating new services and they should not waste their time adapting to the old App FW and binders. 
       * Discussed which NXP board they should use because we do not have a BSP available for the NXP Gold Box (S32G-based). No known Yocto layer for the S32G. 
     * 2/24
       * No AICAS


   * CAN/ Vehicle Signaling
     * 2/10
       * Kuksa.val is building locally for Scott. gRPC support is problematic on the latest version due to known issues upstream with Yocto. Trying to get vehicle speed and working with Web Sockets to now. 
     * 3/10
       * Scott has the kuksa.val server building, booting up, and starting. Going to test python client which is used for their CAN messaging via WebSockets. Subscription API is missing things like notification on a range of values or only when a change of value is detected.  Noted that this is a reference implementation of the W3C spec. gRPC implementation does not have subscription implemented at all (only set and get). 
     * 3/24
       * We will have the kuksa.val building and running with their VISS API for Marlin. 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 
     * 1/13 - Bluetooth done for Marlin, settings app still WIP for networking. 
     * 1/27 - No update for Bluetooth. Connman wrapper is ready to be pushed which will fix the settings app. 
     * 2/10 - The Connman wrapper has been merged. There is a known issue with BLuetooth start up requiring a manual rfkilll to get running on master (SPEC-4253). Scott looking at fixing that. 

   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 
     * 1/27
       * Still a WIP. Scott thinks maybe he can use the same approach that he used for Connmamn to wrap ofono. Most likely does not happen for Marlin initial release. 
     * 2/10
       * Still a WP. Scott may stub out the calls so at least the apps come up an run even if it is not connected to anything on the back end. 

New:
   * Discussed Speech rec and Alexa possibilities. Richard will ask about creating and maintaining an Yocto layer internally. Alexa Auto SDK switched to Conan. (conan.io)
   * Open source engine vosk 

==== March 10, 2022 ====
Attendees: Walt, Jan-Simon, Scott, Paul

   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 
     * 12/2
       * Demo was shown internally yesterday and Damiano said they showed good progress. Will try to show a demo at the next V2C Eg meeting. 
     * 12/16
       * AICAS showed a demo of their work at Monday's V2C call. Not on this call today. 
     * 1/13
       * No AICAS
     * 1/27
       * Making slow progress due to having other tasks that are higher priority.  Chih-Ming has a [[https://www.youtube.com/watch?v=00_23cQOmCI | video of a partner]] using their solution on an NXP board.
     * 2/10
       * Working on their demo some more. Discussed which version of AGL to port to and we suggested that they use Marlin since they will be creating new services and they should not waste their time adapting to the old App FW and binders. 
       * Discussed which NXP board they should use because we do not have a BSP available for the NXP Gold Box (S32G-based). No known Yocto layer for the S32G. 
     * 2/24
       * No AICAS


   * CAN/ Vehicle Signaling
     * 2/10
       * Kuksa.val is building locally for Scott. gRPC support is problematic on the latest version due to known issues upstream with Yocto. Trying to get vehicle speed and working with Web Sockets to now. 
     * 3/10
       * Scott has the kuksa.val server building, booting up, and starting. Going to test python client which is used for their CAN messaging via WebSockets. Subscription API is missing things like notification on a range of values or only when a change of value is detected.  Noted that this is a reference implementation of the W3C spec. gRPC implementation does not have subscription implemented at all (only set and get). 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 
     * 1/13 - Bluetooth done for Marlin, settings app still WIP for networking. 
     * 1/27 - No update for Bluetooth. Connman wrapper is ready to be pushed which will fix the settings app. 
     * 2/10 - The Connman wrapper has been merged. There is a known issue with BLuetooth start up requiring a manual rfkilll to get running on master (SPEC-4253). Scott looking at fixing that. 

   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 
     * 1/27
       * Still a WIP. Scott thinks maybe he can use the same approach that he used for Connmamn to wrap ofono. Most likely does not happen for Marlin initial release. 
     * 2/10
       * Still a WP. Scott may stub out the calls so at least the apps come up an run even if it is not connected to anything on the back end. 

New:


==== February 24, 2022 ====
Attendees: Walt, Scott,

   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 
     * 12/2
       * Demo was shown internally yesterday and Damiano said they showed good progress. Will try to show a demo at the next V2C Eg meeting. 
     * 12/16
       * AICAS showed a demo of their work at Monday's V2C call. Not on this call today. 
     * 1/13
       * No AICAS
     * 1/27
       * Making slow progress due to having other tasks that are higher priority.  Chih-Ming has a [[https://www.youtube.com/watch?v=00_23cQOmCI | video of a partner]] using their solution on an NXP board.
     * 2/10
       * Working on their demo some more. Discussed which version of AGL to port to and we suggested that they use Marlin since they will be creating new services and they should not waste their time adapting to the old App FW and binders. 
       * Discussed which NXP board they should use because we do not have a BSP available for the NXP Gold Box (S32G-based). No known Yocto layer for the S32G. 
     * 2/24
       * No AICAS


   * CAN/ Vehicle Signaling
     * 2/10
       * Kuksa.val is building locally for Scott. gRPC support is problematic on the latest version due to known issues upstream with Yocto. Trying to get vehicle speed and working with Web Sockets to now. 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 
     * 1/13 - Bluetooth done for Marlin, settings app still WIP for networking. 
     * 1/27 - No update for Bluetooth. Connman wrapper is ready to be pushed which will fix the settings app. 
     * 2/10 - The Connman wrapper has been merged. There is a known issue with BLuetooth start up requiring a manual rfkilll to get running on master (SPEC-4253). Scott looking at fixing that. 

   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 
     * 1/27
       * Still a WIP. Scott thinks maybe he can use the same approach that he used for Connmamn to wrap ofono. Most likely does not happen for Marlin initial release. 
     * 2/10
       * Still a WP. Scott may stub out the calls so at least the apps come up an run even if it is not connected to anything on the back end. 

New:


==== February 10, 2022 ====
Attendees: Walt, Jan-Simon, Scott, Chih-Ming, Eric, Heewon

   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 
     * 12/2
       * Demo was shown internally yesterday and Damiano said they showed good progress. Will try to show a demo at the next V2C Eg meeting. 
     * 12/16
       * AICAS showed a demo of their work at Monday's V2C call. Not on this call today. 
     * 1/13
       * No AICAS
     * 1/27
       * Making slow progress due to having other tasks that are higher priority.  Chih-Ming has a [[https://www.youtube.com/watch?v=00_23cQOmCI | video of a partner]] using their solution on an NXP board.
     * 2/10
       * Working on their demo some more. Discussed which version of AGL to port to and we suggested that they use Marlin since they will be creating new services and they should not waste their time adapting to the old App FW and binders. 
       * Discussed which NXP board they should use because we do not have a BSP available for the NXP Gold Box (S32G-based). No known Yocto layer for the S32G. 


   * CAN/ Vehicle Signaling
     * 10/7
       * No progress
     * 11/4
       * Discussed path forward with removal of App FW. Jan-Simon will try to set up a meeting with Oliver H. to discuss how VW and SocketCAN are being used. 
       * Initial thought is to throw out the Signal Composer since it is tightly coupled to the App FW and give apps access to binary CAN messages or to subscribe to a field in CAN messages. 
       * Create some CANOE compatible method for creating the message libraries. 
       * Use of gRPC for IPC? 
     * 11/18
       * Setting up a meeting with Oliver H. for tomorrow to discuss SocketCan. 
       * Scott came across [[https://github.com/eclipse/kuksa.val | Kuksa.val project]] that we will investigate for possible use as a message broker to CAN.  Kuksa.val is the GENIVI project that was done in conjunction with W3C. 
     * 12/2
       * Met with Oliver on Nov 19. He reminded us of [[https://wiki.automotivelinux.org/_media/agl-distro/agl2018-socketcan.pdf | this presentation]] he made at an AGL F2F workshop on usage of SocketCAN. 
       * Scott looked at building Kuksa.val some.  He noted it that it uses git submodules. 
     * 12/16
       * No update due to other priorities
     * 1/13
       * No update
     * 1/27
       * No update. Scott may be able to get Kuksa.val integrated for the Marlin M2 release and possible connected to the HVAC and/or dashboard app. Paul also interested in using it. 
     * 2/10
       * Kuksa.val is building locally for Scott. gRPC support is problematic on the latest version due to known issues upstream with Yocto. Trying to get vehicle speed and working with Web Sockets to now. 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 
     * 1/13 - Bluetooth done for Marlin, settings app still WIP for networking. 
     * 1/27 - No update for Bluetooth. Connman wrapper is ready to be pushed which will fix the settings app. 
     * 2/10 - The Connman wrapper has been merged. There is a known issue with BLuetooth start up requiring a manual rfkilll to get running on master (SPEC-4253). Scott looking at fixing that. 

   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 
     * 1/27
       * Still a WIP. Scott thinks maybe he can use the same approach that he used for Connmamn to wrap ofono. Most likely does not happen for Marlin initial release. 
     * 2/10
       * Still a WP. Scott may stub out the calls so at least the apps come up an run even if it is not connected to anything on the back end. 

New:
   * Eric asked about open source interfaces to vehicle micros.  Suggested that IC EG is working on adding [[https://github.com/Bosch-SW/linux-iccom | ICCOM]] to AGL. 
   * Eric mentioned ErikaOS ([[https://github.com/evidence/erika3 | github]] and [[https://www.erika-enterprise.com/website]]) as a possible open source Implementation of Autosar in the future. 



==== January 27, 2022 ====
Attendees: Walt, Jan-Simon, Scott, Chih-Ming, Paul, Saket


   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 
     * 12/2
       * Demo was shown internally yesterday and Damiano said they showed good progress. Will try to show a demo at the next V2C Eg meeting. 
     * 12/16
       * AICAS showed a demo of their work at Monday's V2C call. Not on this call today. 
     * 1/13
       * No AICAS
     * 1/27
       * Making slow progress due to having other tasks that are higher priority.  Chih-Ming has a [[https://www.youtube.com/watch?v=00_23cQOmCI | video of a partner]] using their solution on an NXP board. 


   * CAN/ Vehicle Signaling
     * 10/7
       * No progress
     * 11/4
       * Discussed path forward with removal of App FW. Jan-Simon will try to set up a meeting with Oliver H. to discuss how VW and SocketCAN are being used. 
       * Initial thought is to throw out the Signal Composer since it is tightly coupled to the App FW and give apps access to binary CAN messages or to subscribe to a field in CAN messages. 
       * Create some CANOE compatible method for creating the message libraries. 
       * Use of gRPC for IPC? 
     * 11/18
       * Setting up a meeting with Oliver H. for tomorrow to discuss SocketCan. 
       * Scott came across [[https://github.com/eclipse/kuksa.val | Kuksa.val project]] that we will investigate for possible use as a message broker to CAN.  Kuksa.val is the GENIVI project that was done in conjunction with W3C. 
     * 12/2
       * Met with Oliver on Nov 19. He reminded us of [[https://wiki.automotivelinux.org/_media/agl-distro/agl2018-socketcan.pdf | this presentation]] he made at an AGL F2F workshop on usage of SocketCAN. 
       * Scott looked at building Kuksa.val some.  He noted it that it uses git submodules. 
     * 12/16
       * No update due to other priorities
     * 1/13
       * No update
     * 1/27
       * No update. Scott may be able to get Kuksa.val integrated for the Marlin M2 release and possible connected to the HVAC and/or dashboard app. Paul also interested in using it. 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 
     * 1/13 - Bluetooth done for Marlin, settings app still WIP for networking. 
     * 1/27 - No update for Bluetooth. Connman wrapper is ready to be pushed which will fix the settings app. 

   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 
     * 1/27
       * Still a WIP. Scott thinks maybe he can use the same approach that he used for Connmamn to wrap ofono. Most likely does not happen for Marlin initial release. 

New:




==== January 13, 2022 ====
Attendees: Walt, Jan-Simon, Scott


   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 
     * 12/2
       * Demo was shown internally yesterday and Damiano said they showed good progress. Will try to show a demo at the next V2C Eg meeting. 
     * 12/16
       * AICAS showed a demo of their work at Monday's V2C call. Not on this call today. 
     * 1/13
       * No AICAS


   * CAN/ Vehicle Signaling
     * 10/7
       * No progress
     * 11/4
       * Discussed path forward with removal of App FW. Jan-Simon will try to set up a meeting with Oliver H. to discuss how VW and SocketCAN are being used. 
       * Initial thought is to throw out the Signal Composer since it is tightly coupled to the App FW and give apps access to binary CAN messages or to subscribe to a field in CAN messages. 
       * Create some CANOE compatible method for creating the message libraries. 
       * Use of gRPC for IPC? 
     * 11/18
       * Setting up a meeting with Oliver H. for tomorrow to discuss SocketCan. 
       * Scott came across [[https://github.com/eclipse/kuksa.val | Kuksa.val project]] that we will investigate for possible use as a message broker to CAN.  Kuksa.val is the GENIVI project that was done in conjunction with W3C. 
     * 12/2
       * Met with Oliver on Nov 19. He reminded us of [[https://wiki.automotivelinux.org/_media/agl-distro/agl2018-socketcan.pdf | this presentation]] he made at an AGL F2F workshop on usage of SocketCAN. 
       * Scott looked at building Kuksa.val some.  He noted it that it uses git submodules. 
     * 12/16
       * No update due to other priorities
     * 1/13
       * No update

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 
     * 1/13 - Bluetooth done for Marlin, settings app still WIP for networking. 


   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 

New:


==== December 16, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Matteo Z.(Western Digital)


   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 
     * 12/2
       * Demo was shown internally yesterday and Damiano said they showed good progress. Will try to show a demo at the next V2C Eg meeting. 
     * 12/16
       * AICAS showed a demo of their work at Monday's V2C call. Not on this call today. 


   * CAN/ Vehicle Signaling
     * 10/7
       * No progress
     * 11/4
       * Discussed path forward with removal of App FW. Jan-Simon will try to set up a meeting with Oliver H. to discuss how VW and SocketCAN are being used. 
       * Initial thought is to throw out the Signal Composer since it is tightly coupled to the App FW and give apps access to binary CAN messages or to subscribe to a field in CAN messages. 
       * Create some CANOE compatible method for creating the message libraries. 
       * Use of gRPC for IPC? 
     * 11/18
       * Setting up a meeting with Oliver H. for tomorrow to discuss SocketCan. 
       * Scott came across [[https://github.com/eclipse/kuksa.val | Kuksa.val project]] that we will investigate for possible use as a message broker to CAN.  Kuksa.val is the GENIVI project that was done in conjunction with W3C. 
     * 12/2
       * Met with Oliver on Nov 19. He reminded us of [[https://wiki.automotivelinux.org/_media/agl-distro/agl2018-socketcan.pdf | this presentation]] he made at an AGL F2F workshop on usage of SocketCAN. 
       * Scott looked at building Kuksa.val some.  He noted it that it uses git submodules. 
     * 12/16
       * No update due to other priorities

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 


   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 

New:
   * Western Digital interested MMC and hypervisors. 


==== December 2, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Damiano


   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 
     * 12/2
       * Demo was shown internally yesterday and Damiano said they showed good progress. Will try to show a demo at the next V2C Eg meeting. 


   * CAN/ Vehicle Signaling
     * 10/7
       * No progress
     * 11/4
       * Discussed path forward with removal of App FW. Jan-Simon will try to set up a meeting with Oliver H. to discuss how VW and SocketCAN are being used. 
       * Initial thought is to throw out the Signal Composer since it is tightly coupled to the App FW and give apps access to binary CAN messages or to subscribe to a field in CAN messages. 
       * Create some CANOE compatible method for creating the message libraries. 
       * Use of gRPC for IPC? 
     * 11/18
       * Setting up a meeting with Oliver H. for tomorrow to discuss SocketCan. 
       * Scott came across [[https://github.com/eclipse/kuksa.val | Kuksa.val project]] that we will investigate for possible use as a message broker to CAN.  Kuksa.val is the GENIVI project that was done in conjunction with W3C. 
     * 12/2
       * Met with Oliver on Nov 19. He reminded us of [[https://wiki.automotivelinux.org/_media/agl-distro/agl2018-socketcan.pdf | this presentation]] he made at an AGL F2F workshop on usage of SocketCAN. 
       * Scott looked at building Kuksa.val some.  He noted it that it uses git submodules. 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code
     * 12/2 - Scott making progress on removal of App FW binding. 


   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 

New:



==== November 18, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Paul, Chih-Ming


   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 
     * 11/18
       * Proof of concept Connman Manager has been implemented and is being evaluated. 


   * CAN/ Vehicle Signaling
     * 10/7
       * No progress
     * 11/4
       * Discussed path forward with removal of App FW. Jan-Simon will try to set up a meeting with Oliver H. to discuss how VW and SocketCAN are being used. 
       * Initial thought is to throw out the Signal Composer since it is tightly coupled to the App FW and give apps access to binary CAN messages or to subscribe to a field in CAN messages. 
       * Create some CANOE compatible method for creating the message libraries. 
       * Use of gRPC for IPC? 
     * 11/18
       * Setting up a meeting with Oliver H. for tomorrow to discuss SocketCan. 
       * Scott came across [[https://github.com/eclipse/kuksa.val | Kuksa.val project]] that we will investigate for possible use as a message broker to CAN.  Kuksa.val is the GENIVI project that was done in conjunction with W3C. 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code


   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module and Telephony
     * 11/18
       * Scott started thinking about how we get telephony, phonebook, and messaging working again with the removal of the App FW.  Telephony should be relatively straightforward since it basically wraps ofono.  PB and messaging will take some more thought.  Possible to get them back for MM release, but not likely to be ready for M1. 

New:



==== November 4, 2021 ====
Attendees: Walt, Scott, Jan-Simon, Damiano, Raouf 

   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 
     * 11/4
       * Chi-Ming on vacation. Not much progress the last few weeks due to vacations. 


   * CAN/ Vehicle Signaling
     * 10/7
       * No progress
     * 11/4
       * Discussed path forward with removal of App FW. Jan-Simon will try to set up a meeting with Oliver H. to discuss how VW and SocketCAN are being used. 
       * Initial thought is to throw out the Signal Composer since it is tightly coupled to the App FW and give apps access to binary CAN messages or to subscribe to a field in CAN messages. 
       * Create some CANOE compatible method for creating the message libraries. 
       * Use of gRPC for IPC? 

   * Bluetooth
     * 11/4 - Scott looking at how get Bluetooth working with App FW removal. Plan is to remove the existing binding code


   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module
     * 10/7

New:


==== October 7, 2021 ====
Attendees: Walt, Scott, Chi-Ming, Sergio

   * ACAIS V2C Demo - Chih-Ming 
     * 10/7
       * No progress on getting Connection Manager working due to illness. 
       * Got GPS (VK-162) working with RPI4. 


   * CAN/ Vehicle Signaling
     * 10/7
       * No progress


   * Ref HW
     * 10/7
       * No progress. 
 

   * 5G/LTE module
     * 10/7

New:




==== September 23, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Chih-Ming

   * Chih-Ming is using the RPI3 for their telematics demo. Discussed best way to go about it. May revisit removal of Pi3 support for Lamprey for Telematics profile only if Chih-Ming has a need. 
     * 7/15 : Chih-Ming compiled the koi branch and got the telematics demo working
       * For master / lamprey 12.0.1 : lets look to get MACHINE=raspberrypi3-64 back.
       * Revert https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26429 and uprev to pi3-64bit
       * Chih-Ming will check if they can use 64-bit
   * Discussed Daniel's latest work
     * 7/29
       * Update: Platform can use pi4 underneath, so no pi3 required.
       * Trying to integrate their application using the SDK
   * 8/12
     * Chih-Ming - switched to RPI4 with [[https://www.waveshare.com/sim8200ea-m2-5g-hat.htm | Waveshare 5g modem]]. Able to build RPI 64-bit image and run their software. Able to receive CAN data via CAN board. 
   * 8/26 
     * No update from Chih-Ming this week. 
   * 9/9
     * Chih-Ming having problems with 4 of the 6 RPI 4 modules that ACAIS has do not boot due to not seeing the partitions.  Might be related to https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26624 which fixes an issue seen with newer versions of the RPI 4 hardware.  Chi-Ming to check the versions of his boards. Scott and Jan-Simon will look at the best way to get this into the build (either directly from upstream or this change.)
   * 9/23
     * Chih-Ming's issues with all of the RPI4s were fixed with the updates suggested by Scott.  Working on connection to AWS. 


   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update
       * 6/4
         * Scott is now back full-time on AGL and will be able to debug CAN FD and decoding issues. 
         * Thomas looking at OpenOBD2
           * https://github.com/commaai/opendbc
           * https://github.com/alan707/openOBD2
           * https://www.csselectronics.com/screen/page/simple-intro-obd2-explained/language/en
       * 6/18
         * Scott no-progress due to other topics
         * Thomas has only about 3 more weeks at Ruetlingen University.  He is not sure who if anyone will take over the vehicle simulator. 
       * 7/1
         * Thomas last day is Monday, Starting his presentation for AGL Tech Day. He shared a few student apps from Github.  Will include the final links in his Tech Day presentation. 
         * Scott hoping to get back to CAN next week.
       * 7/15
         * WIP on CAN.
       * 8.12
         * Scott has been on vacation, no update. 
       * 8/26 
         * No update
       * 9/23
         * Scott tested CAN FD Pi hats with Debian and they work. Will need a 5.10 kernel to get it to work on RPI 4. 
         * Tested CAN on the reference hardware. Works but the driver is throwing a lot of errors. Might be a problem with the way he has it wired. 


   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.
     * 7/29
       * Board arrived and Scott is looking at the integration of the wifi/bt board.
     * 8/12
       * No updates. 
     * 9/9
       * Scott working with Ito-san on the CAN power enablement patch that he submitted. 
       * Having issues with BT audio. A2DP stuttering so badly as to be unusable (same issue seen on KF). Scott suspects a PipeWire issues and will reach out to George.  HFP does not work at all. Most likely needs a special PipeWire or WirePlumber change to enable this. 

   * 5G/LTE module
     * Richard received the 5G module and it works
     * Sorting out module

New:



==== September 9, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Chih-Ming

   * Chih-Ming is using the RPI3 for their telematics demo. Discussed best way to go about it. May revisit removal of Pi3 support for Lamprey for Telematics profile only if Chih-Ming has a need. 
     * 7/15 : Chih-Ming compiled the koi branch and got the telematics demo working
       * For master / lamprey 12.0.1 : lets look to get MACHINE=raspberrypi3-64 back.
       * Revert https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26429 and uprev to pi3-64bit
       * Chih-Ming will check if they can use 64-bit
   * Discussed Daniel's latest work
     * 7/29
       * Update: Platform can use pi4 underneath, so no pi3 required.
       * Trying to integrate their application using the SDK
   * 8/12
     * Chih-Ming - switched to RPI4 with [[https://www.waveshare.com/sim8200ea-m2-5g-hat.htm | Waveshare 5g modem]]. Able to build RPI 64-bit image and run their software. Able to receive CAN data via CAN board. 
   * 8/26 
     * No update from Chih-Ming this week. 
   * 9/9
     * Chih-Ming having problems with 4 of the 6 RPI 4 modules that ACAIS has do not boot due to not seeing the partitions.  Might be related to https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26624 which fixes an issue seen with newer versions of the RPI 4 hardware.  Chi-Ming to check the versions of his boards. Scott and Jan-Simon will look at the best way to get this into the build (either directly from upstream or this change.)



   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update
       * 6/4
         * Scott is now back full-time on AGL and will be able to debug CAN FD and decoding issues. 
         * Thomas looking at OpenOBD2
           * https://github.com/commaai/opendbc
           * https://github.com/alan707/openOBD2
           * https://www.csselectronics.com/screen/page/simple-intro-obd2-explained/language/en
       * 6/18
         * Scott no-progress due to other topics
         * Thomas has only about 3 more weeks at Ruetlingen University.  He is not sure who if anyone will take over the vehicle simulator. 
       * 7/1
         * Thomas last day is Monday, Starting his presentation for AGL Tech Day. He shared a few student apps from Github.  Will include the final links in his Tech Day presentation. 
         * Scott hoping to get back to CAN next week.
       * 7/15
         * WIP on CAN.
       * 8.12
         * Scott has been on vacation, no update. 
       * 8/26 
         * No update


   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.
     * 7/29
       * Board arrived and Scott is looking at the integration of the wifi/bt board.
     * 8/12
       * No updates. 
     * 9/9
       * Scott working with Ito-san on the CAN power enablement patch that he submitted. 
       * Having issues with BT audio. A2DP stuttering so badly as to be unusable (same issue seen on KF). Scott suspects a PipeWire issues and will reach out to George.  HFP does not work at all. Most likely needs a special PipeWire or WirePlumber change to enable this. 

   * 5G/LTE module
     * Richard received the 5G module and it works
     * Sorting out module

New:


==== August 26, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Richard

   * Chih-Ming is using the RPI3 for their telematics demo. Discussed best way to go about it. May revisit removal of Pi3 support for Lamprey for Telematics profile only if Chih-Ming has a need. 
     * 7/15 : Chih-Ming compiled the koi branch and got the telematics demo working
       * For master / lamprey 12.0.1 : lets look to get MACHINE=raspberrypi3-64 back.
       * Revert https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26429 and uprev to pi3-64bit
       * Chih-Ming will check if they can use 64-bit
   * Discussed Daniel's latest work
     * 7/29
       * Update: Platform can use pi4 underneath, so no pi3 required.
       * Trying to integrate their application using the SDK
   * 8/12
     * Chih-Ming - switched to RPI4 with [[https://www.waveshare.com/sim8200ea-m2-5g-hat.htm | Waveshare 5g modem]]. Able to build RPI 64-bit image and run their software. Able to receive CAN data via CAN board. 
   * 8/26 
     * No update from Chih-Ming this week. 


   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update
       * 6/4
         * Scott is now back full-time on AGL and will be able to debug CAN FD and decoding issues. 
         * Thomas looking at OpenOBD2
           * https://github.com/commaai/opendbc
           * https://github.com/alan707/openOBD2
           * https://www.csselectronics.com/screen/page/simple-intro-obd2-explained/language/en
       * 6/18
         * Scott no-progress due to other topics
         * Thomas has only about 3 more weeks at Ruetlingen University.  He is not sure who if anyone will take over the vehicle simulator. 
       * 7/1
         * Thomas last day is Monday, Starting his presentation for AGL Tech Day. He shared a few student apps from Github.  Will include the final links in his Tech Day presentation. 
         * Scott hoping to get back to CAN next week.
       * 7/15
         * WIP on CAN.
       * 8.12
         * Scott has been on vacation, no update. 
       * 8/26 
         * No update


   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.
     * 7/29
       * Board arrived and Scott is looking at the integration of the wifi/bt board.
     * 8/12
       * No updates. 

   * 5G/LTE module
     * Richard received the 5G module and it works
     * Sorting out module

New:



==== August 12, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Chih-Ming

   * Chih-Ming is using the RPI3 for their telematics demo. Discussed best way to go about it. May revisit removal of Pi3 support for Lamprey for Telematics profile only if Chih-Ming has a need. 
     * 7/15 : Chih-Ming compiled the koi branch and got the telematics demo working
       * For master / lamprey 12.0.1 : lets look to get MACHINE=raspberrypi3-64 back.
       * Revert https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26429 and uprev to pi3-64bit
       * Chih-Ming will check if they can use 64-bit
   * Discussed Daniel's latest work
     * 7/29
       * Update: Platform can use pi4 underneath, so no pi3 required.
       * Trying to integrate their application using the SDK
   * 8/12
     * Chih-Ming - switched to RPI4 with [[https://www.waveshare.com/sim8200ea-m2-5g-hat.htm | Waveshare 5g modem]]. Able to build RPI 64-bit image and run their software. Able to receive CAN data via CAN board. 


   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update
       * 6/4
         * Scott is now back full-time on AGL and will be able to debug CAN FD and decoding issues. 
         * Thomas looking at OpenOBD2
           * https://github.com/commaai/opendbc
           * https://github.com/alan707/openOBD2
           * https://www.csselectronics.com/screen/page/simple-intro-obd2-explained/language/en
       * 6/18
         * Scott no-progress due to other topics
         * Thomas has only about 3 more weeks at Ruetlingen University.  He is not sure who if anyone will take over the vehicle simulator. 
       * 7/1
         * Thomas last day is Monday, Starting his presentation for AGL Tech Day. He shared a few student apps from Github.  Will include the final links in his Tech Day presentation. 
         * Scott hoping to get back to CAN next week.
       * 7/15
         * WIP on CAN.
       * 8.12
         * Scott has been on vacation, no update. 


   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.
     * 7/29
       * Board arrived and Scott is looking at the integration of the wifi/bt board.
     * 8/12
       * No updates. 

   * 5G/LTE module
     * Richard received the 5G module and it works
     * Sorting out module

New:



==== July 29, 2021 ====
Attendees: Walt, Jan-Simon, Chih-Ming, Bernard

   * Chih-Ming is using the RPI3 for their telematics demo. Discussed best way to go about it. May revisit removal of Pi3 support for Lamprey for Telematics profile only if Chih-Ming has a need. 
     * 7/15 : Chih-Ming compiled the koi branch and got the telematics demo working
       * For master / lamprey 12.0.1 : lets look to get MACHINE=raspberrypi3-64 back.
       * Revert https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26429 and uprev to pi3-64bit
       * Chih-Ming will check if they can use 64-bit
   * Discussed Daniel's latest work
     * 7/29
       * Update: Platform can use pi4 underneath, so no pi3 required.
       * Trying to integrate their application using the SDK


   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update
       * 6/4
         * Scott is now back full-time on AGL and will be able to debug CAN FD and decoding issues. 
         * Thomas looking at OpenOBD2
           * https://github.com/commaai/opendbc
           * https://github.com/alan707/openOBD2
           * https://www.csselectronics.com/screen/page/simple-intro-obd2-explained/language/en
       * 6/18
         * Scott no-progress due to other topics
         * Thomas has only about 3 more weeks at Ruetlingen University.  He is not sure who if anyone will take over the vehicle simulator. 
       * 7/1
         * Thomas last day is Monday, Starting his presentation for AGL Tech Day. He shared a few student apps from Github.  Will include the final links in his Tech Day presentation. 
         * Scott hoping to get back to CAN next week.
       * 7/15
         * WIP on CAN.
       * 7/29


   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.
     * 7/29
       * Board arrived and Scott is looking at the integration of the wifi/bt board.

   * 5G/LTE module
     * Richard received the 5G module and it works
     * Sorting out module

New:
  * Scott looked at telephony and call hold support. More digging into ofono required.
  * KF Bluetooth (and lateron the refhw module) need some debugging of a race between the binding and the userspace daemon startup



==== July 15, 2021 ====
Attendees: Jan-Simon, Scott, Eric, 


   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update
       * 6/4
         * Scott is now back full-time on AGL and will be able to debug CAN FD and decoding issues. 
         * Thomas looking at OpenOBD2
           * https://github.com/commaai/opendbc
           * https://github.com/alan707/openOBD2
           * https://www.csselectronics.com/screen/page/simple-intro-obd2-explained/language/en
       * 6/18
         * Scott no-progress due to other topics
         * Thomas has only about 3 more weeks at Ruetlingen University.  He is not sure who if anyone will take over the vehicle simulator. 
       * 7/1
         * Thomas last day is Monday, Starting his presentation for AGL Tech Day. He shared a few student apps from Github.  Will include the final links in his Tech Day presentation. 
         * Scott hoping to get back to CAN next week.
       * 7/15
         * WIP on CAN.


   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.

   * 5G/LTE module
     * Richard received the 5G module and it works. 
     * Sorting out module

   * Chih-Ming is using the RPI3 for their telematics demo. Discussed best way to go about it. May revisit removal of Pi3 support for Lamprey for Telematics profile only if Chih-Ming has a need. 
     * 7/15 : Chih-Ming compiled the koi branch and got the telematics demo working
       * For master / lamprey 12.0.1 : lets look to get MACHINE=raspberrypi3-64 back.
       * Revert https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26429 and uprev to pi3-64bit
       * Chih-Ming will check if they can use 64-bit
   * Discussed Daniel's latest work

New:
  * Scott looked at telephony and call hold support. More digging into ofono required.
  * KF Bluetooth (and lateron the refhw module) need some debugging of a race between the binding and the userspace daemon startup


==== July 1, 2021 ====
Attendees: Walt, Jan-Simon, Thomas, Scott, Chih-Ming, Daniel CB


   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update
       * 6/4
         * Scott is now back full-time on AGL and will be able to debug CAN FD and decoding issues. 
         * Thomas looking at OpenOBD2
           * https://github.com/commaai/opendbc
           * https://github.com/alan707/openOBD2
           * https://www.csselectronics.com/screen/page/simple-intro-obd2-explained/language/en
       * 6/18
         * Scott no-progress due to other topics
         * Thomas has only about 3 more weeks at Ruetlingen University.  He is not sure who if anyone will take over the vehicle simulator. 
       * 7/1
         * Thomas last day is Monday, Starting his presentation for AGL Tech Day. He shared a few student apps from Github.  Will include the final links in his Tech Day presentation. 
         * Scott hoping to get back to CAN next week. 


   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.

   * 5G/LTE module
     * Richard received the 5G module and it works. 
     * Sorting out module

New:
   * Chih-Ming is using the RPI3 for their telematics demo. Discussed best way to go about it. May revisit removal of Pi3 support for Lamprey for Telematics profile only if Chih-Ming has a need. 
   * Discussed Daniel's latest work



==== June 18, 2021 ====
Attendees: Walt, Jan-Simon, Thomas, Scott, Chih-Ming


   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update
       * 6/4
         * Scott is now back full-time on AGL and will be able to debug CAN FD and decoding issues. 
         * Thomas looking at OpenOBD2
           * https://github.com/commaai/opendbc
           * https://github.com/alan707/openOBD2
           * https://www.csselectronics.com/screen/page/simple-intro-obd2-explained/language/en
       * 6/18
         * Scott no-progress due to other topics
         * Thomas has only about 3 more weeks at Ruetlingen University.  He is not sure who if anyone will take over the vehicle simulator. 


   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.

   * 5G/LTE module
     * Richard received the 5G module and it works. 
     * Sorting out module

New:



==== June 4, 2021 ====
Attendees: Walt, Jan-Simon, Thomas, Scott, Bernard, Eric S (Panasonic)


   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update
       * 6/4
         * Scott is now back full-time on AGL and will be able to debug CAN FD and decoding issues. 
         * Thomas looking at OpenOBD2
           * https://github.com/commaai/opendbc
           * https://github.com/alan707/openOBD2
           * https://www.csselectronics.com/screen/page/simple-intro-obd2-explained/language/en

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.

   * 5G/LTE module
     * Richard received the 5G module and it works. 
     * Sorting out module

New:
  * Evidence (a Huawei) Erika V3 open source is an open source Autosar alternative. 




==== May 20, 2021 ====
Attendees: Jan-Simon, Thomas, Richard, Scott, Daniel, Bala


   * Vehicle Signaling
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  
       * 5/20
         * No update

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama
     * 5/20
       * Still need to ship.

   * 5G/LTE module
     * Richard received the 5G module and it works. 
     * Sorting out module

New:
  * Thomas has 2 student groups working on demos




==== April 29, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Richard


   * [[ https://docs.google.com/spreadsheets/d/1WsFPh_-2wAYE8NvKlBGywYixhhJz9EBlbUR02r0UWF8/edit?usp=sharing | Connectivity EG feature list]]. 


   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama

   * 5G/LTE module
     * Richard received the 5G module and it works. 
     * 
New:



==== April 15, 2021 ====
Attendees: Walt, Scott, Thomas, 


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update
   * 11/26 - No update.
   * 12/10 - No update

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.  
       * 4/15
         * Scott had no time to debug the CAN decoding issue.  

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above
       * 11/26 - Nothing new

New:
   * Richard still waiting on 5G hardware. 
   * Took another look at the [[ https://docs.google.com/spreadsheets/d/1WsFPh_-2wAYE8NvKlBGywYixhhJz9EBlbUR02r0UWF8/edit?usp=sharing | EG feature list]]. 



==== April 1, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Thomas, Richard, Kurokawa


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update
   * 11/26 - No update.
   * 12/10 - No update

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. (SPEC-3810)
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.
       * 4/1 
         * SPEC-3810 - CAN decoding. Scott can reproduce the issue. Has not had a lot of time to debug.
         * Discussed options for improving the CAN binding and signal composer. Would like to get some feedback about using Canoe format and whether pursuing Kayak as a tool for formatting messages would be something OEMs are interested in. 
         * Most likely would get rid of Signal Composer depending on the App FW rework proposal from Collabora.   

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 
     * 4/1 
       * Sending out from Yokohama

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above
       * 11/26 - Nothing new

New:
   * Richard still waiting on 5G hardware. 
   * Took another look at the [[ https://docs.google.com/spreadsheets/d/1WsFPh_-2wAYE8NvKlBGywYixhhJz9EBlbUR02r0UWF8/edit?usp=sharing | EG feature list]]. 

==== March 4, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Thomas, Richard E


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update
   * 11/26 - No update.
   * 12/10 - No update

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. 
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 
       * 3/4
         * No updates due to other priorities.

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 
     * 3/4
       * Modules not received in Yokohama. 

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above
       * 11/26 - Nothing new

New:




==== February 18, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Thomas, Richard E


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update
   * 11/26 - No update.
   * 12/10 - No update

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 
       * 2/18
         * Thomas did some more testing of Cannelloni usage. Values up to 255 are received and sent ok. Larger values are not received incorrectly. Scott suggests it is in the message JSON or maybe has todo with the CAN binding changes that IoT.bzh did in 2019. 
         * Scott received CAN-FD Pi hats so he can test that out in the near future. 

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 
     * 2/18
       * TI Wifi/BT modules should be received in LF Yokohama office by the end of the month, Delivery plan for the software from Panasonic is TBD. 

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above
       * 11/26 - Nothing new

New:



==== February 4, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Tanikawa, Thomas, Richard E


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update
   * 11/26 - No update.
   * 12/10 - No update

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 
       * 2/4
         * Thomas did some basic testing of packet/message loss with Cannelloni. Test was about a minute long and both computers were on the same network.  He is going to do some more stressful testing over the next few weeks, 

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 
     * 2/4
       * Scott wired up the RF HW for CAN. Hardware is set up as CAN FD, but he does not have CAN FD capable hardware to test it. Ordered a RPI hat that is supposed to support CAN FD.  He theorizes that the reference hardware can be configured for non-FD, but needs to poke around the device tree/ driver to see if it can be reconfigured. 

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above
       * 11/26 - Nothing new

New:




==== January 21, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Tanikawa


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update
   * 11/26 - No update.
   * 12/10 - No update

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 
       * 1/21
         * Scott's fixes went into master. 

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above
       * 11/26 - Nothing new

New:




==== January 7, 2021 ====
Attendees: Walt, Jan-Simon, Scott, Thomas, Sekine, Tanikawa, Li


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update
   * 11/26 - No update.
   * 12/10 - No update

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  
       * 1/7 - No updates from Thomas. 
         * CAN test failures.  SPEC-3756, SPEC-3755 Scott noticed that we lost the configuration file that was in /etc as part of one of the merges last year.  This is needed for the green machine demo, but would not be noticed by most users. 

   * Ref HW
     * 1/7 
       * Panasonic will provide the TI based Bluetooth/Wifi boards at the end of January.  Would like to know if Panasonic will provide drivers and firmware as well as what testing will be done prior to shipping it. Also will need an installation procedure for how to add the board to the existing hardware. 

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above
       * 11/26 - Nothing new

New:




==== December 10, 2020 ====
Attendees: Jan-Simon, Scott, Thomas, Dennis


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update
   * 11/26 - No update.
   * 12/10 - No update

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)
       * 12/10 - Cannelloni added and it is working. 
         * Thomas reports that his  conversion from Canoe to JSON is progressing. Messages are being sent from the driving simulator to AGL and low CAN service is decoding the messages properly.  

   * Ref HW
     * 10/15
       * Booting
       * wifi not showing up in lspci, firmware ?, devicetree ?
       * need more info from Panasonic/Mazda
       * working: hdmi, usb2, 
       * not working: audio (device there, likely wireplumber)
     * 11/26
       * Raquel looking into  HDMI-in, need to decide on CAN bus (pins)
         * GPS working
       * 12/10 
         * Raquel has left Konsulko for a position at an automotive company.  Ref HW sent to Paul.
         * Scott working through the CAN pin-out on the RFHW to be able to test it. 
         * HDMI input needs to be looked at.

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above
       * 11/26 - Nothing new

New:
  * 12/10
    * Networking/BT race conditions - Scott resolved so we do not expect to see the networking to fail. He does still occasionally see BT fail to start up. 




==== November 26, 2020 ====
Attendees: Jan-Simon, Scott, Thomas, 


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update
   * 11/26 - No update.

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]
       * 11/26 - Cannelloni working. Thomas showed remote operation. Will send patches when ready.
         * straight to meta-agl-demo (e.g. recipes-connectivity)

   * Ref HW
     * 10/15
       * Booting
       * wifi not showing up in lspci, firmware ?, devicetree ?
       * need more info from Panasonic/Mazda
       * working: hdmi, usb2, 
       * not working: audio (device there, likely wireplumber)
     * 11/26
       * Raquel looking into  HDMI-in, need to decide on CAN bus (pins)
         * GPS working

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above
       * 11/26 - Nothing new

New:
  * 11/26
    * Networking/BT race conditions - Scott working on unit dependencies
      * SPEC-3509 
      * SPEC-3518


==== November 12, 2020 ====
Attendees: Walt, Jan-Simon, Thomas, Scott, Kurokawa, Tanikawa


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.
   * 11/12 - No update

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 
       * 11/12 - Looked at options for remote CAN support via [[https://github.com/mguentner/cannelloni | Cannelloni]]

   * Ref HW
     * 10/15
       * Booting
       * wifi not showing up in lspci, firmware ?, devicetree ?
       * need more info from Panasonic/Mazda
       * working: hdmi, usb2, 
       * not working: audio (device there, likely wireplumber)

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above

New:

  * 


==== Oct 29, 2020 ====
**Canceled due to Yocto Project Summit**


==== Oct 15, 2020 ====
Attendees: Walt, Jan-Simon, Michael, Thomas, Nomoto-san, Scott, Tanikawa-san

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
   * 9/17 - No update.
   * 10/15 - No update.

   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 

   * Ref HW
     * 10/15
       * Booting
       * wifi not showing up in lspci, firmware ?, devicetree ?
       * need more info from Panasonic/Mazda
       * working: hdmi, usb2, 
       * not working: audio (device there, likely wireplumber)

   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above

New:

  * 



==== Oct 1, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Thomas, Nimoto, Kimura


   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 

   * 9/17 - No update.




   * Vehicle Signaling

       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)
       * 10/1 - Thomas back from holidays and crunch-time and is starting to look at the new version of the low-can generator. 




   * New radio/ tuner architecture (SPEC-3310)
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above


New:

  * 




==== Sept 17, 2020 ====
Attendees: Jan-Simon, Scott, Michael, Furuta, Nomoto, Kimura, Kusakabe   

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
   * 4/30 - Review a little of the platform vs. app breakdown provided by Scott. Toyota will review off-line for the next meeting, Nomoto-san is working on sequence charts based on their work for the next meeting, Scott is concerned that trying to put the Denso-Ten API into AGL does not fit the application framework model and switching over to the Denso-Ten API would be a radical change for the AGL architecture. So we would like a statement of what the goal of using the Denso-Ten API is.  Ideally we would have a short presentation from Toyota and Denso-Ten on what the goals of the effort are and whether they intend to use the AGL App FW and turn in another direction. 
   * 5/12 - Nomoto-san presented two documents. One with a [[https://jira.automotivelinux.org/secure/attachment/13116/20200514_BTFunctionRequirementPlan.pptx | plan for Bluetooth development]] and [[https://jira.automotivelinux.org/secure/attachment/13117/20200514_SequenceDiagram.xlsx | one document]] with sequence diagrams with a discussion of the Denso Ten API.  A lot of feedback was provided on the need for having the Denso API added with an additional middleware layer that does not seem to add any benefit to the AGL implementation. Toyota and Denso Ten will discuss internally before the next meeting. Kusakabe-san verified that there is no code that will be shared by Denso Ten as part of the implementation. 
   * 6/11 - Toyota presented a revised version of their plan.   The concern with the Toyota proposal is that it will introduce extra complexity without any real benefit towards meeting their use cases. Also, there is no code included from Denso-Ten so everything except the API would be implemented from scratch. It was agreed to review the Konsulko proposal from earlier this year regarding improvements to the BT binding and implementation as well as their analysis of the Toyota use cases. Hanaoka-san's concern is that we meet the roadmap approved by the AB and SC. 
   * 6/25 - Reviewed the presentation from Walt to summarize the current status of the EG. Kimura-san would like to review the proposal from Konsulko and propose a reduced API set. Kimura-san clarified that the implementation of the API uses a proprietary third-party Bluetooth stack and cannot be open sourced due to contract restrictions. 
   * 7/9 - Toyota and Denso-Ten agreed to the proposal that we have Konsulko work through the priority list and propose an abstraction layer to allow BlueZ to be easily replaced by a proprietary stack. Konsulko will propose an initial plan in two weeks at the next Connectivity EG including identifying any upstream BlueZ or ofono work that may impact the schedule. 
   * 8/6 - Discussed the impact of the new Product Readiness effort on the Bluetooth and Tuner updates since the App Framework will most likely be replaced and the Bluetooth and Tuner work greatly depends on the binder implementation.  Toyota and Denso Ten will come back with some new ideas on how to proceed within the Connectivity EG in the next month or so. 
   * 8/20 - Decided with the Steering Committee to push out the Bluetooth and Radio API work until some decisions are made regarding the future direction of the App FW in the Production Readiness profile. 
   * 9/17 - No update.

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 
     * 23/7 - Units to be shipped soon.
     * 17/9


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 
       * 4/30 - No updates
       * 5/14 - Thomas hopes to have the converter for the CAN messages in the next two weeks. 
       * 7/9 - Thomas is back working on the project.
       * 7/23 - Thomas has issues with the low-can binding wrt adding own messages: https://lists.automotivelinux.org/g/agl-dev-community/message/8528
         * It is undocumented how to produce the new plugin scheme for the messages
         * Scott will compare the documentation vs. the codebase
         * Thomas works on https://github.com/walzert/agl-js-api/tree/master/src 
       * 8/6 - Scott asked about plan to use CAN in the Trial version of Production Readiness plan. Nomoto-san confirmed that it includes continuing to use the existing AGL can-low-level service. 
       * 8/20 - Scott uploaded some fixes to the low-can-service to fix auto detect issues with J1939. 
       * 9/17 - Jira ticket open for the low-can binding generator not in sync with binding (SPEC-3551)

   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio
     * 9/17 
         * Fix for signaling wrt ofono signalling (phone call), bluez-alsa might need a fix (otherwise we need to check pipewire/wireplumber)
         * tests added using pyagl to gerrit (signal-composer, bt, audiomixer, can)
         * radio binding has a 'null' driver if there is no hardware attached 


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 



   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 
     * 5/14 - No update from Kusakabe-san. 
     * 6/11 - Kimura-san taking over from Kusakabe-san. Will prepare something for the next call. 
     * 6/25 - Reviewed the presentation in SPEC-3310. Scott proposed V4L2 as a possible API for AGL to use to the tuner since Konsulko has some experience integrating V4L2 as a tuner interface with other customers. Denso-Ten will review some more and make another proposal. 
       * Thomas showed the [[Monkey Board | https://www.monkeyboard.org/products/85-developmentboard/80-dab-fm-digital-radio-development-board]] as another option for hardware integration,. 
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above


New:

  * 



==== August 20, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Li, Furuta, Tanikawa, Kurokawa, Nomoto, Kimura, Venkata RPT    

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
   * 4/30 - Review a little of the platform vs. app breakdown provided by Scott. Toyota will review off-line for the next meeting, Nomoto-san is working on sequence charts based on their work for the next meeting, Scott is concerned that trying to put the Denso-Ten API into AGL does not fit the application framework model and switching over to the Denso-Ten API would be a radical change for the AGL architecture. So we would like a statement of what the goal of using the Denso-Ten API is.  Ideally we would have a short presentation from Toyota and Denso-Ten on what the goals of the effort are and whether they intend to use the AGL App FW and turn in another direction. 
   * 5/12 - Nomoto-san presented two documents. One with a [[https://jira.automotivelinux.org/secure/attachment/13116/20200514_BTFunctionRequirementPlan.pptx | plan for Bluetooth development]] and [[https://jira.automotivelinux.org/secure/attachment/13117/20200514_SequenceDiagram.xlsx | one document]] with sequence diagrams with a discussion of the Denso Ten API.  A lot of feedback was provided on the need for having the Denso API added with an additional middleware layer that does not seem to add any benefit to the AGL implementation. Toyota and Denso Ten will discuss internally before the next meeting. Kusakabe-san verified that there is no code that will be shared by Denso Ten as part of the implementation. 
   * 6/11 - Toyota presented a revised version of their plan.   The concern with the Toyota proposal is that it will introduce extra complexity without any real benefit towards meeting their use cases. Also, there is no code included from Denso-Ten so everything except the API would be implemented from scratch. It was agreed to review the Konsulko proposal from earlier this year regarding improvements to the BT binding and implementation as well as their analysis of the Toyota use cases. Hanaoka-san's concern is that we meet the roadmap approved by the AB and SC. 
   * 6/25 - Reviewed the presentation from Walt to summarize the current status of the EG. Kimura-san would like to review the proposal from Konsulko and propose a reduced API set. Kimura-san clarified that the implementation of the API uses a proprietary third-party Bluetooth stack and cannot be open sourced due to contract restrictions. 
   * 7/9 - Toyota and Denso-Ten agreed to the proposal that we have Konsulko work through the priority list and propose an abstraction layer to allow BlueZ to be easily replaced by a proprietary stack. Konsulko will propose an initial plan in two weeks at the next Connectivity EG including identifying any upstream BlueZ or ofono work that may impact the schedule. 
   * 8/6 - Discussed the impact of the new Product Readiness effort on the Bluetooth and Tuner updates since the App Framework will most likely be replaced and the Bluetooth and Tuner work greatly depends on the binder implementation.  Toyota and Denso Ten will come back with some new ideas on how to proceed within the Connectivity EG in the next month or so. 
   * 8/20 - Decided with the Steering Committee to push out the Bluetooth and Radio API work until some decisions are made regarding the future direction of the App FW in the Production Readiness profile. 

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 
     * 23/7 - Units to be shipped soon.
       *  


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 
       * 4/30 - No updates
       * 5/14 - Thomas hopes to have the converter for the CAN messages in the next two weeks. 
       * 7/9 - Thomas is back working on the project.
       * 7/23 - Thomas has issues with the low-can binding wrt adding own messages: https://lists.automotivelinux.org/g/agl-dev-community/message/8528
         * It is undocumented how to produce the new plugin scheme for the messages
         * Scott will compare the documentation vs. the codebase
         * Thomas works on https://github.com/walzert/agl-js-api/tree/master/src 
       * 8/6 - Scott asked about plan to use CAN in the Trial version of Production Readiness plan. Nomoto-san confirmed that it includes continuing to use the existing AGL can-low-level service. 
       * 8/20 - Scott uploaded some fixes to the low-can-service to fix auto detect issues with J1939. 


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 
     * 5/14 - No update from Kusakabe-san. 
     * 6/11 - Kimura-san taking over from Kusakabe-san. Will prepare something for the next call. 
     * 6/25 - Reviewed the presentation in SPEC-3310. Scott proposed V4L2 as a possible API for AGL to use to the tuner since Konsulko has some experience integrating V4L2 as a tuner interface with other customers. Denso-Ten will review some more and make another proposal. 
       * Thomas showed the [[Monkey Board | https://www.monkeyboard.org/products/85-developmentboard/80-dab-fm-digital-radio-development-board]] as another option for hardware integration,. 
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/6 - See Bluetooth discussion above
       * 8/20 - See Bluetooth discussion above


New:




==== August 6, 2020 ====
Attendees: Walt, Scott, Li, Thomas, Kurokawa, Furuta, Kimura, Nomoto, Monden, Michael

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
   * 4/30 - Review a little of the platform vs. app breakdown provided by Scott. Toyota will review off-line for the next meeting, Nomoto-san is working on sequence charts based on their work for the next meeting, Scott is concerned that trying to put the Denso-Ten API into AGL does not fit the application framework model and switching over to the Denso-Ten API would be a radical change for the AGL architecture. So we would like a statement of what the goal of using the Denso-Ten API is.  Ideally we would have a short presentation from Toyota and Denso-Ten on what the goals of the effort are and whether they intend to use the AGL App FW and turn in another direction. 
   * 5/12 - Nomoto-san presented two documents. One with a [[https://jira.automotivelinux.org/secure/attachment/13116/20200514_BTFunctionRequirementPlan.pptx | plan for Bluetooth development]] and [[https://jira.automotivelinux.org/secure/attachment/13117/20200514_SequenceDiagram.xlsx | one document]] with sequence diagrams with a discussion of the Denso Ten API.  A lot of feedback was provided on the need for having the Denso API added with an additional middleware layer that does not seem to add any benefit to the AGL implementation. Toyota and Denso Ten will discuss internally before the next meeting. Kusakabe-san verified that there is no code that will be shared by Denso Ten as part of the implementation. 
   * 6/11 - Toyota presented a revised version of their plan.   The concern with the Toyota proposal is that it will introduce extra complexity without any real benefit towards meeting their use cases. Also, there is no code included from Denso-Ten so everything except the API would be implemented from scratch. It was agreed to review the Konsulko proposal from earlier this year regarding improvements to the BT binding and implementation as well as their analysis of the Toyota use cases. Hanaoka-san's concern is that we meet the roadmap approved by the AB and SC. 
   * 6/25 - Reviewed the presentation from Walt to summarize the current status of the EG. Kimura-san would like to review the proposal from Konsulko and propose a reduced API set. Kimura-san clarified that the implementation of the API uses a proprietary third-party Bluetooth stack and cannot be open sourced due to contract restrictions. 
   * 7/9 - Toyota and Denso-Ten agreed to the proposal that we have Konsulko work through the priority list and propose an abstraction layer to allow BlueZ to be easily replaced by a proprietary stack. Konsulko will propose an initial plan in two weeks at the next Connectivity EG including identifying any upstream BlueZ or ofono work that may impact the schedule. 
   * 8/6 - Discussed the impact of the new Product Readiness effort on the Bluetooth and Tuner updates since the App Framework will most likely be replaced and the Bluetooth and Tuner work greatly depends on the binder implementation.  Toyota and Denso Ten will come back with some new ideas on how to proceed within the Connectivity EG in the next month or so. 
 

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 
     * 23/7 - Units to be shipped soon.
       *  


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 
       * 4/30 - No updates
       * 5/14 - Thomas hopes to have the converter for the CAN messages in the next two weeks. 
       * 7/9 - Thomas is back working on the project.
       * 7/23 - Thomas has issues with the low-can binding wrt adding own messages: https://lists.automotivelinux.org/g/agl-dev-community/message/8528
         * It is undocumented how to produce the new plugin scheme for the messages
         * Scott will compare the documentation vs. the codebase
         * Thomas works on https://github.com/walzert/agl-js-api/tree/master/src 
       * 8/6 - Scott asked about plan to use CAN in the Trial version of Production Readiness plan. Nomoto-san confirmed that it includes continuing to use the existing AGL can-low-level service. 


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 
     * 5/14 - No update from Kusakabe-san. 
     * 6/11 - Kimura-san taking over from Kusakabe-san. Will prepare something for the next call. 
     * 6/25 - Reviewed the presentation in SPEC-3310. Scott proposed V4L2 as a possible API for AGL to use to the tuner since Konsulko has some experience integrating V4L2 as a tuner interface with other customers. Denso-Ten will review some more and make another proposal. 
       * Thomas showed the [[Monkey Board | https://www.monkeyboard.org/products/85-developmentboard/80-dab-fm-digital-radio-development-board]] as another option for hardware integration,. 
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 
       * 8/8 - See Bluetooth discussion above


New:



==== July 23, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Thomas, Li

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
   * 4/30 - Review a little of the platform vs. app breakdown provided by Scott. Toyota will review off-line for the next meeting, Nomoto-san is working on sequence charts based on their work for the next meeting, Scott is concerned that trying to put the Denso-Ten API into AGL does not fit the application framework model and switching over to the Denso-Ten API would be a radical change for the AGL architecture. So we would like a statement of what the goal of using the Denso-Ten API is.  Ideally we would have a short presentation from Toyota and Denso-Ten on what the goals of the effort are and whether they intend to use the AGL App FW and turn in another direction. 
   * 5/12 - Nomoto-san presented two documents. One with a [[https://jira.automotivelinux.org/secure/attachment/13116/20200514_BTFunctionRequirementPlan.pptx | plan for Bluetooth development]] and [[https://jira.automotivelinux.org/secure/attachment/13117/20200514_SequenceDiagram.xlsx | one document]] with sequence diagrams with a discussion of the Denso Ten API.  A lot of feedback was provided on the need for having the Denso API added with an additional middleware layer that does not seem to add any benefit to the AGL implementation. Toyota and Denso Ten will discuss internally before the next meeting. Kusakabe-san verified that there is no code that will be shared by Denso Ten as part of the implementation. 
   * 6/11 - Toyota presented a revised version of their plan.   The concern with the Toyota proposal is that it will introduce extra complexity without any real benefit towards meeting their use cases. Also, there is no code included from Denso-Ten so everything except the API would be implemented from scratch. It was agreed to review the Konsulko proposal from earlier this year regarding improvements to the BT binding and implementation as well as their analysis of the Toyota use cases. Hanaoka-san's concern is that we meet the roadmap approved by the AB and SC. 
   * 6/25 - Reviewed the presentation from Walt to summarize the current status of the EG. Kimura-san would like to review the proposal from Konsulko and propose a reduced API set. Kimura-san clarified that the implementation of the API uses a proprietary third-party Bluetooth stack and cannot be open sourced due to contract restrictions. 
   * 7/9 - Toyota and Denso-Ten agreed to the proposal that we have Konsulko work through the priority list and propose an abstraction layer to allow BlueZ to be easily replaced by a proprietary stack. Konsulko will propose an initial plan in two weeks at the next Connectivity EG including identifying any upstream BlueZ or ofono work that may impact the schedule. 
 

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 
     * 23/7 - Units to be shipped soon.
       *  


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 
       * 4/30 - No updates
       * 5/14 - Thomas hopes to have the converter for the CAN messages in the next two weeks. 
       * 7/9 - Thomas is back working on the project.
       * 7/23 - Thomas has issues with the low-can binding wrt adding own messages: https://lists.automotivelinux.org/g/agl-dev-community/message/8528
         * It is undocumented how to produce the new plugin scheme for the messages
         * Scott will compare the documentation vs. the codebase
         * Thomas works on https://github.com/walzert/agl-js-api/tree/master/src 


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 
     * 5/14 - No update from Kusakabe-san. 
     * 6/11 - Kimura-san taking over from Kusakabe-san. Will prepare something for the next call. 
     * 6/25 - Reviewed the presentation in SPEC-3310. Scott proposed V4L2 as a possible API for AGL to use to the tuner since Konsulko has some experience integrating V4L2 as a tuner interface with other customers. Denso-Ten will review some more and make another proposal. 
       * Thomas showed the [[Monkey Board | https://www.monkeyboard.org/products/85-developmentboard/80-dab-fm-digital-radio-development-board]] as another option for hardware integration,. 
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 


New:


==== July 9, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Kimura, Nomoto, Monden, Thomas, Tanikawa, Magnus Damm (Renesas), Michael, Kurokawa, Kusakabel, Li

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
   * 4/30 - Review a little of the platform vs. app breakdown provided by Scott. Toyota will review off-line for the next meeting, Nomoto-san is working on sequence charts based on their work for the next meeting, Scott is concerned that trying to put the Denso-Ten API into AGL does not fit the application framework model and switching over to the Denso-Ten API would be a radical change for the AGL architecture. So we would like a statement of what the goal of using the Denso-Ten API is.  Ideally we would have a short presentation from Toyota and Denso-Ten on what the goals of the effort are and whether they intend to use the AGL App FW and turn in another direction. 
   * 5/12 - Nomoto-san presented two documents. One with a [[https://jira.automotivelinux.org/secure/attachment/13116/20200514_BTFunctionRequirementPlan.pptx | plan for Bluetooth development]] and [[https://jira.automotivelinux.org/secure/attachment/13117/20200514_SequenceDiagram.xlsx | one document]] with sequence diagrams with a discussion of the Denso Ten API.  A lot of feedback was provided on the need for having the Denso API added with an additional middleware layer that does not seem to add any benefit to the AGL implementation. Toyota and Denso Ten will discuss internally before the next meeting. Kusakabe-san verified that there is no code that will be shared by Denso Ten as part of the implementation. 
   * 6/11 - Toyota presented a revised version of their plan.   The concern with the Toyota proposal is that it will introduce extra complexity without any real benefit towards meeting their use cases. Also, there is no code included from Denso-Ten so everything except the API would be implemented from scratch. It was agreed to review the Konsulko proposal from earlier this year regarding improvements to the BT binding and implementation as well as their analysis of the Toyota use cases. Hanaoka-san's concern is that we meet the roadmap approved by the AB and SC. 
   * 6/25 - Reviewed the presentation from Walt to summarize the current status of the EG. Kimura-san would like to review the proposal from Konsulko and propose a reduced API set. Kimura-san clarified that the implementation of the API uses a proprietary third-party Bluetooth stack and cannot be open sourced due to contract restrictions. 
   * 7/9 - Toyota and Denso-Ten agreed to the proposal that we have Konsulko work through the priority list and propose an abstraction layer to allow BlueZ to be easily replaced by a proprietary stack. Konsulko will propose an initial plan in two weeks at the next Connectivity EG including identifying any upstream BlueZ or ofono work that may impact the schedule. 
 

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 
       * 4/30 - No updates
       * 5/14 - Thomas hopes to have the converter for the CAN messages in the next two weeks. 
       * 7/9 - Thomas is back working on the project.


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 
     * 5/14 - No update from Kusakabe-san. 
     * 6/11 - Kimura-san taking over from Kusakabe-san. Will prepare something for the next call. 
     * 6/25 - Reviewed the presentation in SPEC-3310. Scott proposed V4L2 as a possible API for AGL to use to the tuner since Konsulko has some experience integrating V4L2 as a tuner interface with other customers. Denso-Ten will review some more and make another proposal. 
       * Thomas showed the [[Monkey Board | https://www.monkeyboard.org/products/85-developmentboard/80-dab-fm-digital-radio-development-board]] as another option for hardware integration,. 
       * 7/7 - Denso-Ten is interested in learning more about V4L2 implementation for tuner. Kimura-san said that at the next call Denso-Ten could prepare a use case document like Toyota did for Bluetooth that we can review as the basis for the work going forward. 


New:



==== June 25, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Kimura (Denso-Ten), Nomoto, Monden (ADIT), Hanaoka, Thomas, Tanikawa, Magnus Damm (Renesas), Michael, Kurokawa

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
   * 4/30 - Review a little of the platform vs. app breakdown provided by Scott. Toyota will review off-line for the next meeting, Nomoto-san is working on sequence charts based on their work for the next meeting, Scott is concerned that trying to put the Denso-Ten API into AGL does not fit the application framework model and switching over to the Denso-Ten API would be a radical change for the AGL architecture. So we would like a statement of what the goal of using the Denso-Ten API is.  Ideally we would have a short presentation from Toyota and Denso-Ten on what the goals of the effort are and whether they intend to use the AGL App FW and turn in another direction. 
   * 5/12 - Nomoto-san presented two documents. One with a [[https://jira.automotivelinux.org/secure/attachment/13116/20200514_BTFunctionRequirementPlan.pptx | plan for Bluetooth development]] and [[https://jira.automotivelinux.org/secure/attachment/13117/20200514_SequenceDiagram.xlsx | one document]] with sequence diagrams with a discussion of the Denso Ten API.  A lot of feedback was provided on the need for having the Denso API added with an additional middleware layer that does not seem to add any benefit to the AGL implementation. Toyota and Denso Ten will discuss internally before the next meeting. Kusakabe-san verified that there is no code that will be shared by Denso Ten as part of the implementation. 
   * 6/11 - Toyota presented a revised version of their plan.   The concern with the Toyota proposal is that it will introduce extra complexity without any real benefit towards meeting their use cases. Also, there is no code included from Denso-Ten so everything except the API would be implemented from scratch. It was agreed to review the Konsulko proposal from earlier this year regarding improvements to the BT binding and implementation as well as their analysis of the Toyota use cases. Hanaoka-san's concern is that we meet the roadmap approved by the AB and SC. 
   * 6/25 - Reviewed the presentation from Walt to summarize the current status of the EG. Kimura-san would like to review the proposal from Konsulko and propose a reduced API set. Kimura-san clarified that the implementation of the API uses a proprietary third-party Bluetooth stack and cannot be open sourced due to contract restrictions. 
 

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 
       * 4/30 - No updates
       * 5/14 - Thomas hopes to have the converter for the CAN messages in the next two weeks. 


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 
     * 5/14 - No update from Kusakabe-san. 
     * 6/11 - Kimura-san taking over from Kusakabe-san. Will prepare something for the next call. 
     * 6/25 - Reviewed the presentation in SPEC-3310. Scott proposed V4L2 as a possible API for AGL to use to the tuner since Konsulko has some experience integrating V4L2 as a tuner interface with other customers. Denso-Ten will review some more and make another proposal. 
       * Thomas showed the [[Monkey Board | https://www.monkeyboard.org/products/85-developmentboard/80-dab-fm-digital-radio-development-board]] as another option for hardware integration,. 


New:



==== June 11, 2020 ====
Attendees: Walt, Scott, Kimura (Denso-Ten), Nomoto, Moden (ADIT), Hanaoka, Li, Tanikawa,

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
   * 4/30 - Review a little of the platform vs. app breakdown provided by Scott. Toyota will review off-line for the next meeting, Nomoto-san is working on sequence charts based on their work for the next meeting, Scott is concerned that trying to put the Denso-Ten API into AGL does not fit the application framework model and switching over to the Denso-Ten API would be a radical change for the AGL architecture. So we would like a statement of what the goal of using the Denso-Ten API is.  Ideally we would have a short presentation from Toyota and Denso-Ten on what the goals of the effort are and whether they intend to use the AGL App FW and turn in another direction. 
   * 5/12 - Nomoto-san presented two documents. One with a [[https://jira.automotivelinux.org/secure/attachment/13116/20200514_BTFunctionRequirementPlan.pptx | plan for Bluetooth development]] and [[https://jira.automotivelinux.org/secure/attachment/13117/20200514_SequenceDiagram.xlsx | one document]] with sequence diagrams with a discussion of the Denso Ten API.  A lot of feedback was provided on the need for having the Denso API added with an additional middleware layer that does not seem to add any benefit to the AGL implementation. Toyota and Denso Ten will discuss internally before the next meeting. Kusakabe-san verified that there is no code that will be shared by Denso Ten as part of the implementation. 
   * 6/11 - Toyota presented a revised version of their plan.   The concern with the Toyota proposal is that it will introduce extra complexity without any real benefit towards meeting their use cases. Also, there is no code included from Denso-Ten so everything except the API would be implemented from scratch. It was agreed to review the Konsulko proposal from earlier this year regarding improvements to the BT binding and implementation as well as their analysis of the Toyota use cases. Hanaoka-san's concern is that we meet the roadmap approved by the AB and SC. 
 

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 
       * 4/30 - No updates
       * 5/14 - Thomas hopes to have the converter for the CAN messages in the next two weeks. 


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 
     * 5/14 - No update from Kusakabe-san. 
     * 6/11 - Kimura-san taking over from Kusakabe-san. Will prepare something for the next call. 


New:


==== May 28, 2020 ====
** Meeting Canceled **

==== May 14, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Ohiwa, Thomas, Nomoto, Kusakabe

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
   * 4/30 - Review a little of the platform vs. app breakdown provided by Scott. Toyota will review off-line for the next meeting, Nomoto-san is working on sequence charts based on their work for the next meeting, Scott is concerned that trying to put the Denso-Ten API into AGL does not fit the application framework model and switching over to the Denso-Ten API would be a radical change for the AGL architecture. So we would like a statement of what the goal of using the Denso-Ten API is.  Ideally we would have a short presentation from Toyota and Denso-Ten on what the goals of the effort are and whether they intend to use the AGL App FW and turn in another direction. 
   * 5/12 - Nomoto-san presented two documents. One with a [[https://jira.automotivelinux.org/secure/attachment/13116/20200514_BTFunctionRequirementPlan.pptx | plan for Bluetooth development]] and [[https://jira.automotivelinux.org/secure/attachment/13117/20200514_SequenceDiagram.xlsx | one document]] with sequence diagrams with a discussion of the Denso Ten API.  A lot of feedback was provided on the need for having the Denso API added with an additional middleware layer that does not seem to add any benefit to the AGL implementation. Toyota and Denso Ten will discuss internally before the next meeting. Kusakabe-san verified that there is no code that will be shared by Denso Ten as part of the implementation. 
 

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 
       * 4/30 - No updates
       * 5/14 - Thomas hopes to have the converter for the CAN messages in the next two weeks. 


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 
     * 5/14 - No update from Kusakabe-san. 


New:



==== April 30, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Ohiwa, Thomas, Nomoto, Swapnil

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
   * 4/30 - Review a little of the platform vs. app breakdown provided by Scott. Toyota will review off-line for the next meeting, Nomoto-san is working on sequence charts based on their work for the next meeting, Scott is concerned that trying to put the Denso-Ten API into AGL does not fit the application framework model and switching over to the Denso-Ten API would be a radical change for the AGL architecture. So we would like a statement of what the goal of using the Denso-Ten API is.  Ideally we would have a short presentation from Toyota and Denso-Ten on what the goals of the effort are and whether they intend to use the AGL App FW and turn in another direction. 
 

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 
       * 4/30 - No updates


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 


New:





==== April 16, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Ohiwa, Thomas, Nomoto, Parth

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback. 
   * 4/16 - Nomoto-san reviewed the remaining use cases in the spreadsheet which was uploaded to SPEC-3283. Scott and Matt will add columns to the spreadsheet to respond with what should already be supported in the platform (and needs a UI update) vs what is new platform work. 
 

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.
       * 4/16 - Nothing to report from Scott, Thomas is working on a conversion tool from Canoe DBC to AGL JSON and has had some success with the first message. 


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 


New:



==== April 2, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Thomas, Nomoto, Kusakabe, Ohiwa, Michael, Tanikawa 

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases
   * 4/2 - Nomoto-san presented updated use cases and got feedback.  

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607
       * 4/2 - Scott received from new hardware, but has been busy with dunfell upgrade.


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio
     * 4/2 - No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * New radio/ tuner architecture (SPEC-3310)
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 
     * 4/2 - Kusakabe-san reviewed a document that was posted in [[https://jira.automotivelinux.org/browse/SPEC-3311 | SPEC-3311]] that defines an example radio hardware block diagram. 


New:



==== March 19, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Thomas, Nomoto, Abe, Kusakabe, Matt, Ohiwa, Ron Persky, Kurokawa, 

   * [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Toyota Bluetooth Presentation by Nomoto-san. 
     * SPEC-3283 created as an epic to track all of the use cases.  Nomoto-san or Ohiwa-san will add new Jira tickets for each use case and link them to the epic. We can start to review off-line and review in the next connectivity meeting. 
     * Link to presentation
     * Reviewed the registration use cases

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 


   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)
       * 3/19 - Scott investigating CAN lock ups that are seen in the green machine demo unit. 
         * Some USB CAN Adapters 
           * Thomas is using https://www.fischl.de/usbtin/
           * Scott is using https://www.digikey.ca/product-detail/en/APGDT002/APGDT002-ND/2217607


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 


   * We will look for a way to have Kusakabe-san present the Tuner API proposal he was going to make at the AMM using another format (Zoom?) in the near future.
     * 3/19 - Kusakabe-san has been busy with another hot project. Will wait another two weeks. 


New:



==== March 5, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Li, Kusakabe, Marat, Andrey, Leonid, Mikhail, Thomas

   * Reviewed and updated the [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 
     * 3/5 - Scott's testing revealed that the TI chip does not work and would require effort to get audio working, In light of that the SC decided to build the reference hardware with the Qualcomm chip and use the existing dongles for the initial development while we work with QC on a way to redistribute the firmware. 

   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update
       * 3/5 - Romain not on the call. Would like the CANOE DBC to JSON tool upstreamed or more fully developed for AGL (SPEC-3257)


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 
     * 3/5- No update on audio


   * Telematics requirements and reference device 
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback
     * 03/05 - Work stopped until additional requirements are received or someone makes additional contributions, 

New:
   * We will look for a way to have Kusakabe-san present the Tuner API proposal he was going to make at the AMM using another format (Zoom?) in the near future.


==== February 20, 2020 ====
Attendees: Walt, Jan-Simon, Scott, Sekine, Tanikawa, Michael, Romain, Li, Fujiwara, Kusakabe, Kurokawa

   * Reviewed and updated the [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Discussed RHSA proposal to re-use the TI BT/Wifi chip from the KF board rather than the Qualcomm chip
     * TI chip has not worked well on the KF board and we have disabled it on the M3 and have not used it for H3 in months. 
     * BT HFP - SCO audio not properly supported over UART on the WiLink 7/8. It uses PCM which is not generally supported. We have not tried to make a call using the KF BT due to these issues.  We are not sure if PipeWire will work, but we do know for sure that PulseAudio will not work. 
     * Antenna in KF design is terrible. The signal strength drops off even two feet away to be not usable. The antenna part of the KF design needs to be redesigned  if we use it in the RHSA board. 
     * Scott will try out making calls using the KF BT chip to see if PipeWire works today on KF. 

   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 

   * Telematics reference device 
     * 01/23
       * No update
     * 2/6 - No update

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback

New:




==== February 6, 2020 ====
Attendees: Walt, Jan-Simon, Thomas, Scott, Kusakabe, Michael

   * Reviewed and updated the [[:agl-roadmap#from_connectivity_eg|2020 Roadmap]] for Connectivity EG

   * Vehicle Signaling

       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update
       * 2/6 - No update


   * Bluetooth and Wifi Updates

     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)
     * 2/6 - Updated the roadmap. 

   * Telematics reference device 
     * 01/23
       * No update
     * 2/6 - No update

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback
     * 02/06 - No feedback

New:
  * Thomas showed us some of the work his students having doing with setting up a driving simulator to use AGL. Got some feedback on their usage of CAN and Bluetooth.  
  * Michael asked about the latest status of the LIN driver. Since the driver is working well they will close any open issues in Jira. 



==== January 23, 2020 ====
Attendees: Jan-Simon, Michael, Sharath, Li, George 

   * Review [[:agl-roadmap#from_connectivity_eg|2019 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 7/11 - J1939 merged. Writing to CAN bus will be ready shortly. Icefish planning needs to be done. Will have an idea for next meeting. Candidates include SPEC-1381 and SPEC-2498. 
       * 7/25 - For Icefish
         * Continue to improve J1939. 
         * Maybe - Possible to change to the CAN message dictionary post-build time mand add those message to the low level CAN bus. Need to investigate to determine how much time is needed to do the work and whether it should be included as a requirement for the next SOW. 
         * Add general multi-packet message features to CAN. Already included in J1939, but might need to be added to general CAN messages. 
       * 8/22 
         * low can low-level API might change a little (decoder/encoder functions)
       * 9/5
         * Microchip adding a new LIN bus controller for the steering wheel and may need support for adding the signals. 
         * Romain and team working to integrate improved J1939 and multi-packet support for CAN. 
       * 10/3
         * Discussed how to add steering wheel/ LIN support to Low CAN binding. Need 100 msec polling mechanism which is not generally supported. Whatever we do for CES will probably be non-generic hack. 
         * [[http://carla.org | CARLA]] (Toyota simulator) - plan is for Denso-Ten to get it working for AGL. Kusakabe is asking Toyota for information on what needs to be done. 
         * Multi-packet support has been merged. Need to check on writing to CAN. 
       * 10/17 
         * Discussed LIN interface (see below)
         * CAN writing ok. 
         * CARLA simulator - no new information. 
       * 11/28
         * CARLA (postponed for AMM)
         * halibut: low-level-can binding sync for halibut with master codebase
           * https://jira.automotivelinux.org/browse/SPEC-2976
         * master: plugin-infra and code fixes to be pushed soon. Target is morning of Dec 4th.
         * Comment from Scott: CANFD support - vcar sample changed to FD, non of the current demo HW is FD, so we might have to (partially) revert to non-FD. 
           * https://git.automotivelinux.org/apps/agl-service-can-low-level/tree/examples/agl-vcar/signals.json?h=master#n101
           * Scott will create JIRA, Romain will do fix in next patch round
       * 01/23
         * https://carla.readthedocs.io/en/latest/how_to_build_on_linux/
         * Otherwise no update


   * Bluetooth and Wifi Updates
     * 7/25 - Taking a look at LG Bluetooth implementation.  Looking at multi-connection support in Conman for telematics use cases. Looking at forcing IP address with an ethernet connection. 
     * 8/22 - No update  
     * 9/5 - Bluetooth audio still an issue for 8.0.1.  
     * 10/3 - George has something working, but getting a lot of warnings. Debug in progress.
     * 11/28 
       * bt-pbap has a race condition
       * persistence service (all platform services) have an issue with the selected WORKDIR set to /tmp which means the persistence service will loose its file over reboot. 
       * Matt Ranostay is looking at those
     * 01/23
       * Bluetooth/audio (George)
         * Mediaplayer working (audio via bluetooth)
         * Phone needs work, issues with multiple mic inputs
         * bluetooth is a client in pw currently. better would be an integrated handling for bluetooth.
         * preference of a mic(/speaker) can be declared as property, need to think about alias names (be it 'zones' or $name)

   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 
     * 8/22 - No update
     * 11/28 -No update
     * 01/23 - No update

   * Telematics reference device 
     * 7/25 - Scott showed the telematics reference at ALS during his presentation. Conti showed interest in telematics at ALS. 
     * 8/22 - No update
     * 9/5 - Discussed Connman feasibility  study and ideas for a Connman plug-in versus replacement or other ideas from Tier Ones. Added to Berlin F2F agenda. 
     * 11/28
       * telematic demo platform ftbs on bbe (do_image_wic)
     * 01/23
       * No update

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback
     * 01/23 - No feedback

   * LIN Controller for Steering wheel. 
     * 7/25 - Steering wheel received at Microchip this week. 
     * 8/22 - Waiting for info about connector from Suzuki
     * 9/5 - LIN controller software almost complete at Microchip. Waiting on connector. 
     * 10/3 - See update above. 
     * 10/17 - Scott has a plan for driving the LIN controller that uses the LIN config utility.  Longer term would like to drive it via the Low CAN interface. Works ok in Scott's set up at home, but did not work as well in the green machine, Will poke around the hardware next week in Monte Carlo to start to debug the hardware.
     * 11/28 - Events being generated, low-can part on its way, signal-compose and apps pending 
     * 01/23 - All but one button is now routed into the CES demo 
       * volume, cruise control, speech 
       * only todo: check all patches made it into master
       * declare victory - Tnx: Michael, Scott

New:
  * 

-------

==== October 17, 2019 ====
Attendees: Walt, Jan-Simon, Scott, Romain, Kusakabe

   * Review [[:agl-roadmap#from_connectivity_eg|2019 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 7/11 - J1939 merged. Writing to CAN bus will be ready shortly. Icefish planning needs to be done. Will have an idea for next meeting. Candidates include SPEC-1381 and SPEC-2498. 
       * 7/25 - For Icefish
         * Continue to improve J1939. 
         * Maybe - Possible to change to the CAN message dictionary post-build time mand add those message to the low level CAN bus. Need to investigate to determine how much time is needed to do the work and whether it should be included as a requirement for the next SOW. 
         * Add general multi-packet message features to CAN. Already included in J1939, but might need to be added to general CAN messages. 
       * 8/22 
         * low can low-level API might change a little (decoder/encoder functions)
       * 9/5
         * Microchip adding a new LIN bus controller for the steering wheel and may need support for adding the signals. 
         * Romain and team working to integrate improved J1939 and multi-packet support for CAN. 
       * 10/3
         * Discussed how to add steering wheel/ LIN support to Low CAN binding. Need 100 msec polling mechanism which is not generally supported. Whatever we do for CES will probably be non-generic hack. 
         * [[http://carla.org | CARLA]] (Toyota simulator) - plan is for Denso-Ten to get it working for AGL. Kusakabe is asking Toyota for information on what needs to be done. 
         * Multi-packet support has been merged. Need to check on writing to CAN. 
       * 10/17 
         * Discussed LIN interface (see below)
         * CAN writing ok. 
         * CARLA simulator - no new information. 
       * 11/28
         * CARLA (postponed for AMM)
         * halibut: low-level-can binding sync for halibut with master codebase
           * https://jira.automotivelinux.org/browse/SPEC-2976
         * master: plugin-infra and code fixes to be pushed soon. Target is morning of Dec 4th.
         * Comment from Scott: CANFD support - vcar sample changed to FD, non of the current demo HW is FD, so we might have to (partially) revert to non-FD. 
           * https://git.automotivelinux.org/apps/agl-service-can-low-level/tree/examples/agl-vcar/signals.json?h=master#n101
           * Scott will create JIRA, Romain will do fix in next patch round


   * Bluetooth and Wifi Updates
     * 7/25 - Taking a look at LG Bluetooth implementation.  Looking at multi-connection support in Conman for telematics use cases. Looking at forcing IP address with an ethernet connection. 
     * 8/22 - No update  
     * 9/5 - Bluetooth audio still an issue for 8.0.1.  
     * 10/3 - George has something working, but getting a lot of warnings. Debug in progress.
     * 11/28 
       * bt-pbap has a race condition
       * persistence service (all platform services) have an issue with the selected WORKDIR set to /tmp which means the persistence service will loose its file over reboot. 
       * Matt Ranostay is looking at those

   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 
     * 8/22 - No update
     * 11/28 -No update

   * Telematics reference device 
     * 7/25 - Scott showed the telematics reference at ALS during his presentation. Conti showed interest in telematics at ALS. 
     * 8/22 - No update
     * 9/5 - Discussed Connman feasibility  study and ideas for a Connman plug-in versus replacement or other ideas from Tier Ones. Added to Berlin F2F agenda. 
     * 11/28
       * telematic demo platform ftbs on bbe (do_image_wic)

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update
     * 11/28 - No feedback

   * LIN Controller for Steering wheel. 
     * 7/25 - Steering wheel received at Microchip this week. 
     * 8/22 - Waiting for info about connector from Suzuki
     * 9/5 - LIN controller software almost complete at Microchip. Waiting on connector. 
     * 10/3 - See update above. 
     * 10/17 - Scott has a plan for driving the LIN controller that uses the LIN config utility.  Longer term would like to drive it via the Low CAN interface. Works ok in Scott's set up at home, but did not work as well in the green machine, Will poke around the hardware next week in Monte Carlo to start to debug the hardware.
     * 11/28 - Events being generated, low-can part on its way, signal-compose and apps pending 

New Business:
   * Discussion on how to relay incoming lin signal into new can message


-------

==== October 17, 2019 ====
Attendees: Walt, Jan-Simon, Scott, Romain, Michael, Kusakabe, Ashvinid

   * Review [[:agl-roadmap#from_connectivity_eg|2019 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 7/11 - J1939 merged. Writing to CAN bus will be ready shortly. Icefish planning needs to be done. Will have an idea for next meeting. Candidates include SPEC-1381 and SPEC-2498. 
       * 7/25 - For Icefish
         * Continue to improve J1939. 
         * Maybe - Possible to change to the CAN message dictionary post-build time mand add those message to the low level CAN bus. Need to investigate to determine how much time is needed to do the work and whether it should be included as a requirement for the next SOW. 
         * Add general multi-packet message features to CAN. Already included in J1939, but might need to be added to general CAN messages. 
       * 8/22 
         * low can low-level API might change a little (decoder/encoder functions)
       * 9/5
         * Microchip adding a new LIN bus controller for the steering wheel and may need support for adding the signals. 
         * Romain and team working to integrate improved J1939 and multi-packet support for CAN. 
       * 10/3
         * Discussed how to add steering wheel/ LIN support to Low CAN binding. Need 100 msec polling mechanism which is not generally supported. Whatever we do for CES will probably be non-generic hack. 
         * [[http://carla.org | CARLA]] (Toyota simulator) - plan is for Denso-Ten to get it working for AGL. Kusakabe is asking Toyota for information on what needs to be done. 
         * Multi-packet support has been merged. Need to check on writing to CAN. 
       * 10/17 
         * Discussed LIN interface (see below)
         * CAN writing ok. 
         * CARLA simulator - no new information. 


   * Bluetooth and Wifi Updates
     * 7/25 - Taking a look at LG Bluetooth implementation.  Looking at multi-connection support in Conman for telematics use cases. Looking at forcing IP address with an ethernet connection. 
     * 8/22 - No update  
     * 9/5 - Bluetooth audio still an issue for 8.0.1.  
     * 10/3 - George has something working, but getting a lot of warnings. Debug in progress. 

   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 
     * 8/22 - No update

   * Telematics reference device 
     * 7/25 - Scott showed the telematics reference at ALS during his presentation. Conti showed interest in telematics at ALS. 
     * 8/22 - No update
     * 9/5 - Discussed Connman feasibility  study and ideas for a Connman plug-in versus replacement or other ideas from Tier Ones. Added to Berlin F2F agenda. 

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update

   * LIN Controller for Steering wheel. 
     * 7/25 - Steering wheel received at Microchip this week. 
     * 8/22 - Waiting for info about connector from Suzuki
     * 9/5 - LIN controller software almost complete at Microchip. Waiting on connector. 
     * 10/3 - See update above. 
     * 10/17 - Scott has a plan for driving the LIN controller that uses the LIN config utility.  Longer term would like to drive it via the Low CAN interface. Works ok in Scott's set up at home, but did not work as well in the green machine, Will poke around the hardware next week in Monte Carlo to start to debug the hardware. 

New Business:



==== October 3, 2019 ====
Attendees: Walt, Jan-Simon, Scott, Romain, George, Kusakabe

   * Review [[:agl-roadmap#from_connectivity_eg|2019 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 7/11 - J1939 merged. Writing to CAN bus will be ready shortly. Icefish planning needs to be done. Will have an idea for next meeting. Candidates include SPEC-1381 and SPEC-2498. 
       * 7/25 - For Icefish
         * Continue to improve J1939. 
         * Maybe - Possible to change to the CAN message dictionary post-build time mand add those message to the low level CAN bus. Need to investigate to determine how much time is needed to do the work and whether it should be included as a requirement for the next SOW. 
         * Add general multi-packet message features to CAN. Already included in J1939, but might need to be added to general CAN messages. 
       * 8/22 
         * low can low-level API might change a little (decoder/encoder functions)
       * 9/5
         * Microchip adding a new LIN bus controller for the steering wheel and may need support for adding the signals. 
         * Romain and team working to integrate improved J1939 and multi-packet support for CAN. 
       * 10/3
         * Discussed how to add steering wheel/ LIN support to Low CAN binding. Need 100 msec polling mechanism which is not generally supported. Whatever we do for CES will probably be non-generic hack. 
         * [[http://carla.org | CARLA]] (Toyota simulator) - plan is for Denso-Ten to get it working for AGL. Kusakabe is asking Toyota for information on what needs to be done. 
         * Multi-packet support has been merged. Need to check on writing too CAN. 


   * Bluetooth and Wifi Updates
     * 7/25 - Taking a look at LG Bluetooth implementation.  Looking at multi-connection support in Conman for telematics use cases. Looking at forcing IP address with an ethernet connection. 
     * 8/22 - No update  
     * 9/5 - Bluetooth audio still an issue for 8.0.1.  
     * 10/3 - George has something working, but getting a lot of warnings. Debug in progress. 

   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 
     * 8/22 - No update

   * Telematics reference device 
     * 7/25 - Scott showed the telematics reference at ALS during his presentation. Conti showed interest in telematics at ALS. 
     * 8/22 - No update
     * 9/5 - Discussed Connman feasibility  study and ideas for a Connman plug-in versus replacement or other ideas from Tier Ones. Added to Berlin F2F agenda. 

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update

   * LIN Controller for Steering wheel. 
     * 7/25 - Steering wheel received at Microchip this week. 
     * 8/22 - Waiting for info about connector from Suzuki
     * 9/5 - LIN controller software almost complete at Microchip. Waiting on connector. 
     * 10/3 - See update above. 

New Business:


==== September 6, 2019 ====
Attendees: Walt, Jan-Simon, Scott, Romain

   * Review [[:agl-roadmap#from_connectivity_eg|2019 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 7/11 - J1939 merged. Writing to CAN bus will be ready shortly. Icefish planning needs to be done. Will have an idea for next meeting. Candidates include SPEC-1381 and SPEC-2498. 
       * 7/25 - For Icefish
         * Continue to improve J1939. 
         * Maybe - Possible to change to the CAN message dictionary post-build time mand add those message to the low level CAN bus. Need to investigate to determine how much time is needed to do the work and whether it should be included as a requirement for the next SOW. 
         * Add general multi-packet message features to CAN. Already included in J1939, but might need to be added to general CAN messages. 
       * 8/22 
         * low can low-level API might change a little (decoder/encoder functions)
       * 9/5
         * Microchip adding a new LIN bus controller for the steering wheel and may need support for adding the signals. 
         * Romain and team working to integrate improved J1939 and multi-packet support for CAN. 


   * Bluetooth and Wifi Updates
     * 7/25 - Taking a look at LG Bluetooth implementation.  Looking at multi-connection support in Conman for telematics use cases. Looking at forcing IP address with an ethernet connection. 
     * 8/22 - No update  
     * 9/5 - Bluetooth audio still an issue for 8.0.1.  

   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 
     * 8/22 - No update

   * Telematics reference device 
     * 7/25 - Scott showed the telematics reference at ALS during his presentation. Conti showed interest in telematics at ALS. 
     * 8/22 - No update
     * 9/5 - Discussed Connman feasibility  study and ideas for a Connman plug-in versus replacement or other ideas from Tier Ones. Added to Berlin F2F agenda. 

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update
     * 9/5 - No update

   * LIN Controller for Steering wheel. 
     * 7/25 - Steering wheel received at Microchip this week. 
     * 8/22 - Waiting for info about connector from Suzuki
     * 9/5 - LIN controller software almost complete at Microchip. Waiting on connector. 

New Business:


==== August 22, 2019 ====
Attendees: Jan-Simon, Romain, Michael
 * Review [[:agl-roadmap#from_connectivity_eg|2019 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 7/11 - J1939 merged. Writing to CAN bus will be ready shortly. Icefish planning needs to be done. Will have an idea for next meeting. Candidates include SPEC-1381 and SPEC-2498. 
       * 7/25 - For Icefish
         * Continue to improve J1939. 
         * Maybe - Possible to change to the CAN message dictionary post-build time mand add those message to the low level CAN bus. Need to investigate to determine how much time is needed to do the work and whether it should be included as a requirement for the next SOW. 
         * Add general multi-packet message features to CAN. Already included in J1939, but might need to be added to general CAN messages. 
       * 8/22 
         * low can low-level API might change a little (decoder/encoder functions)


   * Bluetooth and Wifi Updates
     * 7/25 - Taking a look at LG Bluetooth implementation.  Looking at multi-connection support in Conman for telematics use cases. Looking at forcing IP address with an ethernet connection. 
     * 8/22 - No update  

   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 
     * 8/22 - No update

   * Telematics reference device 
     * 7/25 - Scott showed the telematics reference at ALS during his presentation. Conti showed interest in telematics at ALS. 
     * 8/22 - No update

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 
     * 8/22 - No update

   * LIN Controller for Steering wheel. 
     * 7/25 - Steering wheel received at Microchip this week. 
     * 8/22 - Waiting for info about connector from Suzuki

New Business:

==== July 25, 2019 ====
Attendees: Walt, Jan-Simon, Romain, Scott, Kusakabe

 * Review [[:agl-roadmap#from_connectivity_eg|2019 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 7/11 - J1939 merged. Writing to CAN bus will be ready shortly. Icefish planning needs to be done. Will have an idea for next meeting. Candidates include SPEC-1381 and SPEC-2498. 
       * 7/25 - For Icefish
         * Continue to improve J1939. 
         * Maybe - Possible to change to the CAN message dictionary post-build time mand add those message to the low level CAN bus. Need to investigate to determine how much time is needed to do the work and whether it should be included as a requirement for the next SOW. 
         * Add general multi-packet message features to CAN. Already included in J1939, but might need to be added to general CAN messages. 


   * Bluetooth and Wifi Updates
     * 7/25 - Taking a look at LG Bluetooth implementation.  Looking at multi-connection support in Conman for telematics use cases. Looking at forcing IP address with an ethernet connection. 
  
   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 

   * Telematics reference device 
     * 7/25 - Scott showed the telematics reference at ALS during his presentation. Conti showed interest in telematics at ALS. 


   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 

   * LIN Controller for Steering wheel. 
     * 7/25 - Steering wheel received at Microchip this week. 

New Business:


==== July 11, 2019 ====
Attendees: Walt, Jan-Simon, Scott, Romain, Kusakabe, Michael,

 * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 4/4 
         * J1939 work continues. Plan is to make the HH release. Team is looking for J1939 CAN data for playback and testing. 
       * 4/18
         * J1939 work continues. Subscription to J1939 in Low Level CAN binder is in progress. First drop RC1 or RC2 for HH. 
         * SPEC-2312 work in progress. Bug found in GG. 
       * 5/16
         * J1939 work is in a sandbox, but not pushed to master yet. Requires kernel version 4.19 so testing has been taking place using QEMU. Need to check the kernel version that will be available with Renesas BSP version 3.19. Will need to make J1939 an optional feature prior to merging the sandbox due to the kernel issue. 
         * Romain pointed us to http://docs.automotivelinux.org/docs/en/master/apis_services/reference/signaling/3-Usage.html#write-on-can-buses for documentation on how to write to the CAN bus. 
       * 6/27 - J1939 ready to be merged. Will be done for RC2. Bug fixes, improvements, and documentation are continuing for the next RC. 
       * 7/11 - J1939 merged. Writing to CAN bus will be ready shortly. Icefish planning needs to be done. Will have an idea for next meeting. Candidates include SPEC-1381 and SPEC-2498. 


   * Bluetooth and Wifi Updates
     * 2/7 - rewrite of the bindings is complete
     * 2/21 - New conmann being backported by Matt to fix the excessive scanning issues. 
     * 3/21 - Backport of connman complete. Working on Bluetooth pairing issue and making it more robust. Raquel looking at adding IP addresses to settings app.  
     * 4/18 - Raquel working on settings app. Matt looking at MAP support and messaging app. MAP not very well supported within Bluez. 
     * 5/16 - Raquel in progress on settings app. Waiting on Walt for an icon. Matt has an initial version MAP working. 
     * 6/13 - Raquel has been working on static IP address and ethernet address updates. Also noticed that Wifi signal strength was not working correctly. Will be uploading changes to gerrit for HH. 
     * 6/25 - Pretty much merged, except the UI change. 
     * 7/11 - Everything merged except UI change. Some bugs open that Raquel is looking at. 
  
   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 

   * Telematics reference device using built in modem support
     * Minimal image being tested
     * 3/21 - On hold due to thud uprev
     * 4/4 - On hold for thud uprev. 
     * 4/18 - Scott is populating repos for both guppy and master. Looking at different modems. 
     * 5/16 - Scott testing telematics on guppy 7.0.2. Looking into Bluez and ophono support for multiple simultaneous connections. Probably will not work out of the box.  
     * 6/13 - Scott ordered new CAN adapters that should work better since they have drivers built into the kernel. Matt and Scott are working on a report of the issues that will be encountered using Bluez and ofono since there is a lot of work required to get them working for a wired modem as well as with the multiple phone use cases. Before we start on that work we really want to know if any Tier Ones or OEMs plan to use that architecture in production. 
     * 6/25 - Nothing to report. Scott busy with Pipewire and non-root updates to master. 
     * 7/11 - Scott bringing the demo set up to ALS next week. Will show in the booth. Looking at size reduction changes. Report on issues with Bluez and ofono will be ready for Tuesday's F2F meeting. 

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 


New Business:
   * Michael needs to get the steering wheel from Suzuki to Karlsruhe. Should be easy to add to the existing LIN controller for HVAC. 

==== June 27, 2019 ====
Attendees: Walt, Jan-Simon, Scott, Romain, Kusakabe, George, Kurokawa

 * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 4/4 
         * J1939 work continues. Plan is to make the HH release. Team is looking for J1939 CAN data for playback and testing. 
       * 4/18
         * J1939 work continues. Subscription to J1939 in Low Level CAN binder is in progress. First drop RC1 or RC2 for HH. 
         * SPEC-2312 work in progress. Bug found in GG. 
       * 5/16
         * J1939 work is in a sandbox, but not pushed to master yet. Requires kernel version 4.19 so testing has been taking place using QEMU. Need to check the kernel version that will be available with Renesas BSP version 3.19. Will need to make J1939 an optional feature prior to merging the sandbox due to the kernel issue. 
         * Romain pointed us to http://docs.automotivelinux.org/docs/en/master/apis_services/reference/signaling/3-Usage.html#write-on-can-buses for documentation on how to write to the CAN bus. 
       * 6/27 - J1939 ready to be merged. Will be done for RC2. Bug fixes, improvements, and documentation are continuing for the next RC. 


   * Bluetooth and Wifi Updates
     * 2/7 - rewrite of the bindings is complete
     * 2/21 - New conmann being backported by Matt to fix the excessive scanning issues. 
     * 3/21 - Backport of connman complete. Working on Bluetooth pairing issue and making it more robust. Raquel looking at adding IP addresses to settings app.  
     * 4/18 - Raquel working on settings app. Matt looking at MAP support and messaging app. MAP not very well supported within Bluez. 
     * 5/16 - Raquel in progress on settings app. Waiting on Walt for an icon. Matt has an initial version MAP working. 
     * 6/13 - Raquel has been working on static IP address and ethernet address updates. Also noticed that Wifi signal strength was not working correctly. Will be uploading changes to gerrit for HH. 
     * 6/25 - Pretty much merged, except the UI change. 
  
   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 

   * Telematics reference device using built in modem support
     * Minimal image being tested
     * 3/21 - On hold due to thud uprev
     * 4/4 - On hold for thud uprev. 
     * 4/18 - Scott is populating repos for both guppy and master. Looking at different modems. 
     * 5/16 - Scott testing telematics on guppy 7.0.2. Looking into Bluez and ophono support for multiple simultaneous connections. Probably will not work out of the box.  
     * 6/13 - Scott ordered new CAN adapters that should work better since they have drivers built into the kernel. Matt and Scott are working on a report of the issues that will be encountered using Bluez and ofono since there is a lot of work required to get them working for a wired modem as well as with the multiple phone use cases. Before we start on that work we really want to know if any Tier Ones or OEMs plan to use that architecture in production. 
     * 6/25 - Nothing to report. Scott busy with Pipewire and non-root updates to master. 

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 


New Business:

==== June 13, 2019 ====
Attendees: Walt, Scott, Kusakabe, George, Michael, Kurokawa

 * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 4/4 
         * J1939 work continues. Plan is to make the HH release. Team is looking for J1939 CAN data for playback and testing. 
       * 4/18
         * J1939 work continues. Subscription to J1939 in Low Level CAN binder is in progress. First drop RC1 or RC2 for HH. 
         * SPEC-2312 work in progress. Bug found in GG. 
       * 5/16
         * J1939 work is in a sandbox, but not pushed to master yet. Requires kernel version 4.19 so testing has been taking place using QEMU. Need to check the kernel version that will be available with Renesas BSP version 3.19. Will need to make J1939 an optional feature prior to merging the sandbox due to the kernel issue. 
         * Romain pointed us to http://docs.automotivelinux.org/docs/en/master/apis_services/reference/signaling/3-Usage.html#write-on-can-buses for documentation on how to write to the CAN bus. 


   * Bluetooth and Wifi Updates
     * 2/7 - rewrite of the bindings is complete
     * 2/21 - New conmann being backported by Matt to fix the excessive scanning issues. 
     * 3/21 - Backport of connman complete. Working on Bluetooth pairing issue and making it more robust. Raquel looking at adding IP addresses to settings app.  
     * 4/18 - Raquel working on settings app. Matt looking at MAP support and messaging app. MAP not very well supported within Bluez. 
     * 5/16 - Raquel in progress on settings app. Waiting on Walt for an icon. Matt has an initial version MAP working. 
     * 6/13 - Raquel has been working on static IP address and ethernet address updates. Also noticed that Wifi signal strength was not working correctly. Will be uploading changes to gerrit for HH. 
  
   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 

   * Telematics reference device using built in modem support
     * Minimal image being tested
     * 3/21 - On hold due to thud uprev
     * 4/4 - On hold for thud uprev. 
     * 4/18 - Scott is populating repos for both guppy and master. Looking at different modems. 
     * 5/16 - Scott testing telematics on guppy 7.0.2. Looking into Bluez and ophono support for multiple simultaneous connections. Probably will not work out of the box.  
     * 6/13 - Scott ordered new CAN adapters that should work better since they have drivers built into the kernel. Matt and Scott are working on a report of the issues that will be encountered using Bluez and ofono since there is a lot of work required to get them working for a wired modem as well as with the multiple phone use cases. Before we start on that work we really want to know if any Tier Ones or OEMs plan to use that architecture in production. 

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 


New Business:

==== May 30, 2019 ====
Canceled due to holiday. 

==== May 16, 2019 ====
Attendees: Walt, Romain, Scott, Michael, Chris, Jana

 * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG

   * Vehicle Signaling
       * 4/4 
         * J1939 work continues. Plan is to make the HH release. Team is looking for J1939 CAN data for playback and testing. 
       * 4/18
         * J1939 work continues. Subscription to J1939 in Low Level CAN binder is in progress. First drop RC1 or RC2 for HH. 
         * SPEC-2312 work in progress. Bug found in GG. 
       * 5/16
         * J1939 work is in a sandbox, but not pushed to master yet. Requires kernel version 4.19 so testing has been taking place using QEMU. Need to check the kernel version that will be available with Renesas BSP version 3.19. Will need to make J1939 an optional feature prior to merging the sandbox due to the kernel issue. 
         * Romain pointed us to http://docs.automotivelinux.org/docs/en/master/apis_services/reference/signaling/3-Usage.html#write-on-can-buses for documentation on how to write to the CAN bus. 


   * Bluetooth and Wifi Updates
     * 2/7 - rewrite of the bindings is complete
     * 2/21 - New conmann being backported by Matt to fix the excessive scanning issues. 
     * 3/21 - Backport of connman complete. Working on Bluetooth pairing issue and making it more robust. Raquel looking at adding IP addresses to settings app.  
     * 4/18 - Raquel working on settings app. Matt looking at MAP support and messaging app. MAP not very well supported within Bluez. 
     * 5/16 - Raquel in progress on settings app. Waiting on Walt for an icon. Matt has an initial version MAP working. 
  
   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 

   * Telematics reference device using built in modem support
     * Minimal image being tested
     * 3/21 - On hold due to thud uprev
     * 4/4 - On hold for thud uprev. 
     * 4/18 - Scott is populating repos for both guppy and master. Looking at different modems. 
     * 5/16 - Scott testing telematics on guppy 7.0.2. Looking into Bluez and ophono support for multiple simultaneous connections. Probably will not work out of the box.  

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 


New Business:


==== May 2, 2019 ====
Meeting canceled due to holidays 

==== April 18, 2019 ====
Attendees: Walt, Jan-Simon, Romain, Scott, Shrikanth

  * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
       * 4/4 
         * J1939 work continues. Plan is to make the HH release. Team is looking for J1939 CAN data for playback and testing. 
       * 4/18
         * J1939 work continues. Subscription to J1939 in Low Level CAN binder is in progress. First drop RC1 or RC2 for HH. 
         * SPEC-2312 work in progress. Bug found in GG. 


   * Bluetooth and Wifi Updates
     * 2/7 - rewrite of the bindings is complete
     * 2/21 - New conmann being backported by Matt to fix the excessive scanning issues. 
     * 3/21 - Backport of connman complete. Working on Bluetooth pairing issue and making it more robust. Raquel looking at adding IP addresses to settings app.  
     * 4/18 - Raquel working on settings app. Matt looking at MAP support and messaging app. MAP not very well supported within Bluez. 
  
   * NFC - Use of NFC for user identification. 
     * 4/18 - Nothing to report. T-Systems looking at identity binding and using NFC more extensively. 

   * Telematics reference device using built in modem support
     * Minimal image being tested
     * 3/21 - On hold due to thud uprev
     * 4/4 - On hold for thud uprev. 
     * 4/18 - Scott is populating repos for both guppy and master. Looking at different modems. 

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 


New Business:



==== April 4, 2019 ====
Attendees: Walt, Jan-Simon, Eric, Jana Thodeti (Panasonic), Julian (Collabora), George, Michael, Chris, Shrikanth (Panasonic), Romain, Sebastien, 

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * 1/24
         * CANFD completed and added in gerrit for GG.
         * Plans for HH
           * Adding multiframe capability 
           * Reference CAN message set
           * J1939 support
           * Signal composer improvements TBD 
           * Messaging sending optimizations - one shot versus constant messages
       * 2/7 
         * Walt spoke to Paul Thieme of Purdue University who is working on agriculture projects and they are interested promoting AGL for ISO 11783 based on J1939 and displaying data to farm tractor operators. 
         * J1939 implementation is currently in development. Relies on multi-frame support for CAN. Investigating whether this can be completed for HH. 
         * Discussed how to send CAN data using the Signal Composer and Low Level CAN binding. Walt will create a JIRA ticket to document the use cases. 
         * Kusakabe talked about how Denso-Ten will make additional use of the Signal Composer and Low Level CAN binding this year in their work on AGL. 
       * 2/21 
         * J1939 support underway. Will support J1939 multi-frame use case. General multi-frame can wait for additional requirements from OEMs or other protocols.
       * 3/21
         * Romain just returned from vacation. J1939 work continues. 
       * 4/4 
         * J1939 work continues. Plan is to make the HH release. Team is looking for J1939 CAN data for playback and testing. 


   * Bluetooth and Wifi Updates
     * 2/7 - rewrite of the bindings is complete
     * 2/21 - New conmann being backported by Matt to fix the excessive scanning issues. 
     * 3/21 - Backport of connman complete. Working on Bluetooth pairing issue and making it more robust. Raquel looking at adding IP addresses to settings app.  
  
   * NFC - Use of NFC for user identification. 
     * 1/24 - Reading the cards is ok. Still some issues with writing the tags with neard. Close to finishing this off once Scott get her the latest Identity agent changes. 
     * 2/7 - Raquel has the latest identity agent changes from Scott and fixing open issues.  
     * 2/21 - Identity agent changes tested and submitted to gerrit. 
     * 3/21 - NFC complete complete for now. Raquel documented some potential changes we can do in the event we get further requirements for changes in the future. Need to document how to create cards. 
     * 4/4 - Nothing to report. 

   * Telematics reference device using built in modem support
     * Minimal image being tested
     * 3/21 - On hold due to thud uprev
     * 4/4 - On hold for thud uprev. 

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 
     * Jana clarified the potential requirements for a silver box that there is the possibility for multiple network connections in a telematics device. Could be hardwired modem + Bluetooth telephony from a personal device + Wifi at the same time. 
     * Also possible for IVI system to have multiple Bluetooth phones connected to a silver box or IVI system and have to support multiple phone books (for one or separate users). 
     * Encryption of personal user data. 
     * Panasonic will think about reference hardware that can use for Telematics reference hardware. 


New Business:


==== March 21, 2019 ====
Attendees: Walt, Jan-Simon, Scott, George, Clement, Sebastien

Roadmap for 2019 

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * 1/24
         * CANFD completed and added in gerrit for GG.
         * Plans for HH
           * Adding multiframe capability 
           * Reference CAN message set
           * J1939 support
           * Signal composer improvements TBD 
           * Messaging sending optimizations - one shot versus constant messages
       * 2/7 
         * Walt spoke to Paul Thieme of Purdue University who is working on agriculture projects and they are interested promoting AGL for ISO 11783 based on J1939 and displaying data to farm tractor operators. 
         * J1939 implementation is currently in development. Relies on multi-frame support for CAN. Investigating whether this can be completed for HH. 
         * Discussed how to send CAN data using the Signal Composer and Low Level CAN binding. Walt will create a JIRA ticket to document the use cases. 
         * Kusakabe talked about how Denso-Ten will make additional use of the Signal Composer and Low Level CAN binding this year in their work on AGL. 
       * 2/21 
         * J1939 support underway. Will support J1939 multi-frame use case. General multi-frame can wait for additional requirements from OEMs or other protocols.
       * 3/21
         * Romain just returned from vacation. J1939 work continues. 


   * Bluetooth and Wifi Updates
     * 2/7 - rewrite of the bindings is complete
     * 2/21 - New conmann being backported by Matt to fix the excessive scanning issues. 
     * 3/21 - Backport of connman complete. Working on Bluetooth pairing issue and making it more robust. Raquel looking at adding IP addresses to settings app.  
  
   * NFC - Use of NFC for user identification. 
     * 1/24 - Reading the cards is ok. Still some issues with writing the tags with neard. Close to finishing this off once Scott get her the latest Identity agent changes. 
     * 2/7 - Raquel has the latest identity agent changes from Scott and fixing open issues.  
     * 2/21 - Identity agent changes tested and submitted to gerrit. 
     * 3/21 - NFC complete complete for now. Raquel documented some potential changes we can do in the event we get further requirements for changes in the future. Need to document how to create cards. 

   * Instrument Cluster 
     * Nothing to report. Some minor issues to fix with GG on the back burner due to thud uprev. 
     * 3/21 - Moved to Instrument Cluster EG

   * Telematics reference device using built in modem support
     * Minimal image being tested
     * 3/21 - On hold due to thud uprev

   * Telematics requirements
     * Is there a use case for simultaneous connection of a hardwired phone and a Bluetooth phone? Need to check with OEMs on their system architecture.  If so presents and architecture complication that needs to be thought through. 


New Business:

==== March 7, 2019 ====
Meeting canceled due to AMM

==== February 21, 2019 ====
Attendees: Walt, Jan-Simon, Sebastien, Scott, Romain, Kusakabe, Michael

Roadmap for 2019 

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * 1/24
         * CANFD completed and added in gerrit for GG.
         * Plans for HH
           * Adding multiframe capability 
           * Reference CAN message set
           * J1939 support
           * Signal composer improvements TBD 
           * Messaging sending optimizations - one shot versus constant messages
       * 2/7 
         * Walt spoke to Paul Thieme of Purdue University who is working on agriculture projects and they are interested promoting AGL for ISO 11783 based on J1939 and displaying data to farm tractor operators. 
         * J1939 implementation is currently in development. Relies on multi-frame support for CAN. Investigating whether this can be completed for HH. 
         * Discussed how to send CAN data using the Signal Composer and Low Level CAN binding. Walt will create a JIRA ticket to document the use cases. 
         * Kusakabe talked about how Denso-Ten will make additional use of the Signal Composer and Low Level CAN binding this year in their work on AGL. 
       * 2/21 
         * J1939 support underway. Will support J1939 multi-frame use case. General multi-frame can wait for additional requirements from OEMs or other protocols.


   * Bluetooth and Wifi Updates
     * 2/7 - rewrite of the bindings is complete
     * 2/21 - New conmann being backported by Matt to fix the excessive scanning issues. 
  
   * NFC - Use of NFC for user identification. 
     * 1/24 - Reading the cards is ok. Still some issues with writing the tags with neard. Close to finishing this off once Scott get her the latest Identity agent changes. 
     * 2/7 - Raquel has the latest identity agent changes from Scott and fixing open issues.  
     * 2/21 - Identity agent changes tested and submitted to gerrit. 

   * Instrument Cluster 
     * Nothing to report. Some minor issues to fix with GG on the back burner due to thud uprev. 

   * Telematics reference device using built in modem support
     * Minimal image being tested

New Business:


==== February 7, 2019 ====
Attendees: Walt, Jan-Simon, Sebastien, Scott, Romain, Kusakabe

Roadmap for 2019 

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 
     * 9/20 
       * No Update
     * 10/4
      * adapting low-level CAN binder to handle CAN FD frames. 
      * Test cases are complete for low level CAN binder and Signal Composer
     * 11/1 
       * No update
     * 11/15
       * No update
     * 12/13
       * Romain pushed CANFD capability to the low level CAN binder. See https://gerrit.automotivelinux.org/gerrit/#/q/status:open+project:apps/agl-service-can-low-level+branch:master+topic:canfd
     * 1/24
         * CANFD completed and added in gerrit for GG.
         * Plans for HH
           * Adding multiframe capability 
           * Reference CAN message set
           * J1939 support
           * Signal composer improvements TBD 
           * Messaging sending optimizations - one shot versus constant messages
       * 2/7 
         * Walt spoke to Paul Thieme of Purdue University who is working on agriculture projects and they are interested promoting AGL for ISO 11783 based on J1939 and displaying data to farm tractor operators. 
         * J1939 implementation is currently in development. Relies on multi-frame support for CAN. Investigating whether this can be completed for HH. 
         * Discussed how to send CAN data using the Signal Composer and Low Level CAN binding. Walt will create a JIRA ticket to document the use cases. 
         * Kusakabe talked about how Denso-Ten will make additional use of the Signal Composer and Low Level CAN binding this year in their work on AGL. 


   * Bluetooth and Wifi Updates
     * 2/7 - rewrite of the bindings is complete
  
   * NFC - Use of NFC for user identification. 
     * 1/24 - Reading the cards is ok. Still some issues with writing the tags with neard. Close to finishing this off once Scott get her the latest Identity agent changes. 
     * 2/7 - Raquel has the latest identity agent changes from Scott and fixing open issues.  
 
New Business:
     * Telematics reference device using built in modem support
       * Newer version of ofono required (1.25 being tested) than we have in FF or GG. 


==== January 13 and 24, 2019 ====
Attendees: Walt, Jan-Simon, Sebastien, Michael, Romain, Chris, Scott

Roadmap for 2019 

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 
     * 9/20 
       * No Update
     * 10/4
      * adapting low-level CAN binder to handle CAN FD frames. 
      * Test cases are complete for low level CAN binder and Signal Composer
     * 11/1 
       * No update
     * 11/15
       * No update
     * 12/13
       * Romain pushed CANFD capability to the low level CAN binder. See https://gerrit.automotivelinux.org/gerrit/#/q/status:open+project:apps/agl-service-can-low-level+branch:master+topic:canfd
       * 1/24
         * CANFD completed and added in gerrit for GG.
         * Plans for HH
           * Adding multiframe capability 
           * Reference CAN message set
           * J1939 support
           * Signal composer improvements TBD 
           * Messaging sending optimizations - one shot versus constant messages

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 
     * 9/6 - Bluetooth binding still in progress
     * 11/1 
       * Need to follow-up on https://jira.automotivelinux.org/browse/SPEC-1801
     * 11/15
       * Matt R's rewrite of Bluetooth binding progressing. Stoyan will test the latest batch of patches merged in gerrit. Then these will be backported to FF. 
     * 11/29 - Bluetooth binding rewrite being tested in Karlsruhe this week on FF as well as master. Looks good so far. 

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". SPEC-1683 assigned to Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
     * 9/6 - SPEC-1683 resolved. 
     * 11/1 had issues in Dresden with service (fixed by https://gerrit.automotivelinux.org/gerrit/#/c/17249/ )
     * 11/15 - Raquel removed libnfc dependency and has a good handle on how to finish it off. Should be ready for Karlsruhe. 
     * 11/29 - Raquel's changes look good in testing. Need to get a handle on programming tags to match the identity in the current tags. Loic is getting the schema to enable local identity handling without requiring going to the Forgerock server. 
     * 12/13 - Raquel's changes available. Programming the cards is a little wonky. 
     * 1/24 - Reading the cards is ok. Still some issues with writing the tags with neard. Close to finishing this off once Scott get her the latest Identity agent changes. 
 
New Business:
     * Telematics reference device using built in modem support
       * Newer version of ofono required (1.25 being tested) than we have in FF or GG. 


==== December 13, 2018 ====
Attendees: Walt, Jan-Simon, Sebastien, Michael, Romain

   * HVAC actuator in green machine #1 (from Japan) is not working correctly. Discussed debug possibilities. Michael confirmed that both demo units have updated hardware and firmware. Will create a video and share with Michael. 
   * No Bluetooth audio on flounder or master. Need help from Thierry. Sent him an email asking for support at 6 pm. 


   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 
     * 9/20 
       * No Update
     * 10/4
      * adapting low-level CAN binder to handle CAN FD frames. 
      * Test cases are complete for low level CAN binder and Signal Composer
     * 11/1 
       * No update
     * 11/15
       * No update
     * 12/13
       * Romain pushed CANFD capability to the low level CAN binder. See https://gerrit.automotivelinux.org/gerrit/#/q/status:open+project:apps/agl-service-can-low-level+branch:master+topic:canfd
       * 1/24
         * CANFD completed and added in gerrit for GG.
         * Plans for HH
           * Adding multiframe capability 
           * Reference CAN message set
           * J1939 support
           * Signal composer improvements TBD 
           * Messaging sending optimizations - one shot versus constant messages

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 
     * 9/6 - Bluetooth binding still in progress
     * 11/1 
       * Need to follow-up on https://jira.automotivelinux.org/browse/SPEC-1801
     * 11/15
       * Matt R's rewrite of Bluetooth binding progressing. Stoyan will test the latest batch of patches merged in gerrit. Then these will be backported to FF. 
     * 11/29 - Bluetooth binding rewrite being tested in Karlsruhe this week on FF as well as master. Looks good so far. 

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". SPEC-1683 assigned to Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
     * 9/6 - SPEC-1683 resolved. 
     * 11/1 had issues in Dresden with service (fixed by https://gerrit.automotivelinux.org/gerrit/#/c/17249/ )
     * 11/15 - Raquel removed libnfc dependency and has a good handle on how to finish it off. Should be ready for Karlsruhe. 
     * 11/29 - Raquel's changes look good in testing. Need to get a handle on programming tags to match the identity in the current tags. Loic is getting the schema to enable local identity handling without requiring going to the Forgerock server. 
     * 12/13 - Raquel's changes available. Programming the cards is a little wonky. 
     * 1/24 - Reading the cards is ok. Still some issues with writing the tags with neard. Close to finishing this off once Scott get her the latest Identity agent changes. 
 
New Business:
     * Telematics reference device using built in modem support
       * Newer version of ofono required (1.25 being tested) than we have in FF or GG. 



==== November 29, 2018 ====
Attendees: Walt, Jan-Simon, Scott, Matt R, Sebastien, Romain

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 
     * 9/20 
       * No Update
     * 10/4
      * adapting low-level CAN binder to handle CAN FD frames. 
      * Test cases are complete for low level CAN binder and Signal Composer
     * 11/1 
       * No update
     * 11/15
       * No update

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 
     * 9/6 - Bluetooth binding still in progress
     * 11/1 
       * Need to follow-up on https://jira.automotivelinux.org/browse/SPEC-1801
     * 11/15
       * Matt R's rewrite of Bluetooth binding progressing. Stoyan will test the latest batch of patches merged in gerrit. Then these will be backported to FF. 
     * 11/29 - Bluetooth binding rewrite being tested in Karlsruhe this week on FF as well as master. Looks good so far. 

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". SPEC-1683 assigned to Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
     * 9/6 - SPEC-1683 resolved. 
     * 11/1 had issues in Dresden with service (fixed by https://gerrit.automotivelinux.org/gerrit/#/c/17249/ )
     * 11/15 - Raquel removed libnfc dependency and has a good handle on how to finish it off. Should be ready for Karlsruhe. 
     * 11/29 - Raquel's changes look good in testing. Need to get a handle on programming tags to match the identity in the current tags. Loic is getting the schema to enable local identity handling without requiring going to the Forgerock server. 
 
New Business:
     * Setting time on the M3 issue - Jan-Simon got an RTC working with KF+M3

     * Got an update from Scott on the work for the IC reference. 


==== November 15, 2018 ====
Attendees: Walt, Jan-Simon, Scott, Kusakabe, Romain, Michael, Chris

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 
     * 9/20 
       * No Update
     * 10/4
      * adapting low-level CAN binder to handle CAN FD frames. 
      * Test cases are complete for low level CAN binder and Signal Composer
     * 11/1 
       * No update
     * 11/15
       * No update

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 
     * 9/6 - Bluetooth binding still in progress
     * 11/1 
       * Need to follow-up on https://jira.automotivelinux.org/browse/SPEC-1801
     * 11/15
       * Matt R's rewrite of Bluetooth binding progressing. Stoyan will test the latest batch of patches merged in gerrit. Then these will be backported to FF. 

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". SPEC-1683 assigned to Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
     * 9/6 - SPEC-1683 resolved. 
     * 11/1 had issues in Dresden with service (fixed by https://gerrit.automotivelinux.org/gerrit/#/c/17249/ )
     * 11/15 - Raquel removed libnfc dependency and has a good handle on how to finish it off. Should be ready for Karlsruhe. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 
     * 7/26 - No update

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates
     * 7/26
       * New lin kernel module pending for rc3
     * 11/1 
       * Pending in gerrit: https://gerrit.automotivelinux.org/gerrit/#/c/17615/
       * Todo: systemd unit and hvac app can device rename
     * 11/15
       * Done

New Business:
     * Setting time on the M3 issue
     * Got an update from Scott on the work for the IC reference. 

==== November 1, 2018 ====
Attendees: Jan-Simon, Tom

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 
     * 9/20 
       * No Update
     * 10/4
      * adapting low-level CAN binder to handle CAN FD frames. 
      * Test cases are complete for low level CAN binder and Signal Composer
     * 11/1 
       * No update

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 
     * 9/6 - Bluetooth binding still in progress
     * 11/1 
       * Need to follow-up on https://jira.automotivelinux.org/browse/SPEC-1801

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". SPEC-1683 assigned to Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
     * 9/6 - SPEC-1683 resolved. 
     * 11/1 had issues in Dresden with service (fixed by https://gerrit.automotivelinux.org/gerrit/#/c/17249/ )
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 
     * 7/26 - No update

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates
     * 7/26
       * New lin kernel module pending for rc3
     * 11/1 
       * Pending in gerrit: https://gerrit.automotivelinux.org/gerrit/#/c/17615/
       * Todo: systemd unit and hvac app can device rename

New Business:
     * 



==== October 18, 2018 ====
Canceled due to Dresden AMM

==== October 4, 2018 ====
Attendees: Walt, Jan-Simon, Romain, Scott, Stephane, Michael

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 
     * 9/20 
       * No Update
     * 10/4
      * adapting low-level CAN binder to handle CAN FD frames. 
      * Test cases are complete for low level CAN binder and Signal Composer

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 
     * 9/6 - Bluetooth binding still in progress


   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". SPEC-1683 assigned to Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
     * 9/6 - SPEC-1683 resolved. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 
     * 7/26 - No update

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates
     * 7/26
       * New lin kernel module pending for rc3

New Business:


==== September  20, 2018 ====
Attendees: Walt, Jan-Simon, Scott

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 
     * 9/20 
       * No Update

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 
     * 9/6 - Bluetooth binding still in progress


   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". SPEC-1683 assigned to Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
     * 9/6 - SPEC-1683 resolved. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 
     * 7/26 - No update

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates
     * 7/26
       * New lin kernel module pending for rc3

New Business:


==== September 6, 2018 ====
Attendees: Walt, Matt, Sebastien, Romain

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 
     * 9/6 - Bluetooth binding still in progress


   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". SPEC-1683 assigned to Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
     * 9/6 - SPEC-1683 resolved. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 
     * 7/26 - No update

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates
     * 7/26
       * New lin kernel module pending for rc3

New Business:


==== September 6, 2018 ====
Attendees: Walt, Matt, Sebastien, Romain

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG
     * 9/6
       * Not much to update 

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 
     * 9/6 - Bluetooth binding still in progress


   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". SPEC-1683 assigned to Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
     * 9/6 - SPEC-1683 resolved. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 
     * 7/26 - No update

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates
     * 7/26
       * New lin kernel module pending for rc3

New Business:


==== August 23, 2018 ====
Attendees: Walt, Jan-Simon, Romain, Matt, Sebastien

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 
     * 8/23
       * Signal composer and low-level CAN binder unit test cases were merged today. Still a little bit of integration for FF, but it should be ready for the release. 
       * Bug fixes from unit test output will be next task.
       * J1939 investigation and V2C metric collection planned for GG
       * Tool in progress to convert from Vektor CAN files to OpenXC/ JSON
       * Conversion to API V3 in progress for GG 

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542
     * 8/23 - all of the wifi updates are in and the old wifi binding has been removed. Bluetooth rewrite based on the network binding lessons learned in progress for GG. 

   * Telephony Updates
     * PBAP and Contact app in progress. 
    * 7/12
       * Done. Need icons. Will submit ticket

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update
     * 8/23 
       * On hold. Jan-Simon noted that the systemd units for NFC are failing when no NFC hardware is present. Need to fail "gracefully". Need a Jira ticket and will assign Matt R. 
       * http://lava.baylibre.com:10080/scheduler/job/37897#L3037
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 
     * 7/26 - No update

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates
     * 7/26
       * New lin kernel module pending for rc3

New Business:



==== August 9, 2018 ====
Attendees: Walt, Michael, Chris, Romain

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling
     * 8/9 
       * Performance issue considered closed. 
       * Metadata handling improvement considered closed
       * Signal composer unit test coverage improvements in progress. 

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542

   * Telephony Updates
     * PBAP and Contact app in progress. 
    * 7/12
       * Done. Need icons. Will submit ticket

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.
     * 4/19 - Still working on binder and a command line test app. Should be feature complete in next week or so and ready for review. 
     * 5/3 - Sandbox is functionally complete and Pantellis has started integrating with libqtappfw.  Should push sandbox to master so we can more widely review and test it. Will add issues as subtasks for the continuing work.  
     * 5/17 - Still in-flight. Pantellis is somewhat blocked by Matt's work. Looks like RC2.
     * 5/31 - WIP for RC2.
     * 6/14 - On track for RC2
     * 6/28 - Still on track RC2
     * 7/12 - See above
     * 7/26 - All merged for rc2
 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 
     * 7/26 - No update

   * Discussed test methodology and packaging for CIAT tests.  Schedule a separate a call to discuss with IoT.bzh and Konsulko. Tentatively May 15 after the dev call. Scott, Matt, Matt, Sebastien, Jose, Jonathan should be invited. 
     * Had call on 5/29. Working on Build Types and deployment of wgt(s) within AppFw.
     * 7/12
       * Discussed using Yocto ptests as method for calling and packaging tests
         * https://wiki.yoctoproject.org/wiki/Ptest
         * http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-support/attr/files/run-ptest

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates
     * 7/26
       * New lin kernel module pending for rc3

New Business:


==== July 26, 2018 ====
Attendees: Jan-Simon, Romain, Christian, Michael, 

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing
     * 7/26
       * Performance issue: Romain could reproduce and fix (down to 5% CPU), Kusakabe-san reported it to be fine
       * Improvement on metadata handling

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 
     * 7/26 - network binding in gerrit/merged and now settings UI being converted over (patches in gerrit) tracked under SPEC-1542

   * Telephony Updates
     * PBAP and Contact app in progress. 
    * 7/12
       * Done. Need icons. Will submit ticket

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 
     * 7/26
       * No update


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.
     * 4/19 - Still working on binder and a command line test app. Should be feature complete in next week or so and ready for review. 
     * 5/3 - Sandbox is functionally complete and Pantellis has started integrating with libqtappfw.  Should push sandbox to master so we can more widely review and test it. Will add issues as subtasks for the continuing work.  
     * 5/17 - Still in-flight. Pantellis is somewhat blocked by Matt's work. Looks like RC2.
     * 5/31 - WIP for RC2.
     * 6/14 - On track for RC2
     * 6/28 - Still on track RC2
     * 7/12 - See above
     * 7/26 - All merged for rc2
 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 
     * 7/26 - No update

   * Discussed test methodology and packaging for CIAT tests.  Schedule a separate a call to discuss with IoT.bzh and Konsulko. Tentatively May 15 after the dev call. Scott, Matt, Matt, Sebastien, Jose, Jonathan should be invited. 
     * Had call on 5/29. Working on Build Types and deployment of wgt(s) within AppFw.
     * 7/12
       * Discussed using Yocto ptests as method for calling and packaging tests
         * https://wiki.yoctoproject.org/wiki/Ptest
         * http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-support/attr/files/run-ptest

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates
     * 7/26
       * New lin kernel module pending for rc3

New Business:
  * Wrt: most driver - re-enabled with https://gerrit.automotivelinux.org/gerrit/#/c/15773/1



==== July 12, 2018 ====
Attendees: Walt, Jan-Simon, Sebastien, Matt, Romain

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section.  
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  
     * 7/12
       * Reviewed roadmap and updated
       * Ask Kusakabe to create a JIRA issue based on his ALS 2018 presentation and include the method for reproducing his findings. Use that to document performance improvements. 
       * FF effort is now testing and bug-fixing

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 
     * 7/11 - Testing for FF release in progress. Bluetooth Interoperability testing in progress. Finding issues with specific devices. Switch over to new network binding from the old Wifi binding in progress. Switchover will be ready for RC3 including removal of old Wifi binding. 

   * Telephony Updates
     * PBAP and Contact app in progress. 
    * 7/12
       * Done. Need icons. Will submit ticket.

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on
     * 7/12 
       * Matt R cranking along. 


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.
     * 4/19 - Still working on binder and a command line test app. Should be feature complete in next week or so and ready for review. 
     * 5/3 - Sandbox is functionally complete and Pantellis has started integrating with libqtappfw.  Should push sandbox to master so we can more widely review and test it. Will add issues as subtasks for the continuing work.  
     * 5/17 - Still in-flight. Pantellis is somewhat blocked by Matt's work. Looks like RC2.
     * 5/31 - WIP for RC2.
     * 6/14 - On track for RC2
     * 6/28 - Still on track RC2
     * 7/12 - See above
 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 

   * Discussed test methodology and packaging for CIAT tests.  Schedule a separate a call to discuss with IoT.bzh and Konsulko. Tentatively May 15 after the dev call. Scott, Matt, Matt, Sebastien, Jose, Jonathan should be invited. 
     * Had call on 5/29. Working on Build Types and deployment of wgt(s) within AppFw.
     * 7/12
       * Discussed using Yocto ptests as method for calling and packaging tests
         * https://wiki.yoctoproject.org/wiki/Ptest
         * http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-support/attr/files/run-ptest

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.
     * 7/12
       * No updates

New Business:


==== June 28, 2018 ====
Attendees: Walt, Romain, Matt P, Kusakabe, Sebastien, Stephane

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section. 
     * 3/22
       * SPEC-1339 - Jonathan working on stabilization of low level CAN binding - merged in gerrit
       * SPEC-1347 - Adding "EngineOn" to low level CAN binding
       * New binding in progress to store metrics on vehicle bus. Could be used for supervision, remote diagnostics or black box use cases.
       * SPEC-1344 - Check with Jan-Simon
     * 4/5 
       * SPEC-1344 - Done
       * SPEC-1347 - Jonathan almost finished. 
       * SPEC-1381 - Next up for Jonathan - Adding vehicle message dictionaries to low-level CAN
       * Test cases - Start with CAN low-level services. 
     * 4/19
       * Discussions with Oliver Hartkopp went well last week in Karlsruhe.
       * Jonathan still chugging along. 
       * Romain - add namespace usage based on discussion with Oliver probably after FF. Requires kernel 4.12 or later. 
     * 5/3
       * SPEC-1419 - Romain working on changing the signal composer to a more flexible meta-data storage model. Need Jira ticket. 
       * Jonathan working on testing the low level CAN. See discussion below about creating reusable test plans. 
     * 5/17
       * SPEC-1419 - Will not be available until the end of June. Romain on vacation the next three weeks. 
       * SPEC-1407 - Data collection for V2C use cases. Most likely a demo for AMM and targeted for Grumpy Guppy. 
       * Jonathan continuing with test plans and procedures for low-level CAN. (Need Jira)
     * 5/31
       * Progress on signal-composer using openxc, code on github, to be submitted when Romain is back.
       * SPEC-1419 and SPEC-1407 WIP
       * Jonathan worked on tests for the low-can service, Romain started to integrate these into a test binding (using lua scripts to test low-can).
         * https://github.com/iotbzh/afb-test
         * https://github.com/iotbzh/afb-test/blob/master/conf.d/project/lua.d/low-can-tests.lua
     * 6/14 
       * Signal composer changes will be pushed ASAP by Romain now that he is bacl
       * Romain working on lua scripts for low level can tests. Should be ready next week. 
     * 6/28
       * Signal composer changes to be pushed today or tomorrow. Will get into FF RC2.
       * Low-level CAN tests to be pushed today.  

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 4/19 - Matt R. posted patches to rework the Bluetooth settings app 
     * 5/4 - Matt R. still hammering away it. A bunch of patches were merged. 
     * 5/17 - Matt R. back ports to eel have been submitted. Testing these because it looks like there have been some regressions on eel. Not sure if this is related to the backports or something else. 
       * Asynchronous disconnect and reconnect of Bluetooth devices is not being handled correctly by the binding. Matt P. working on fixes for that. 
     * 5/31 - Matt R sent all fixes to Eel. Matt R also tested in 'real life' environment.
     * 6/14 - Set for ALS on Eel 
     * 6/28 - Matt P. working on wifi binding to update to use generic network service. Wifi binding will be deprecated. 

   * Telephony Updates
     * PBAP and Contact app in progress. 
     * 4/5 
       * SPEC-1382 - PBAB and Contact App - Binding ready. Integration in progress. 
     * 4/19 
       * SPEC-1382 - Rewrite of the phone app to include tabs for phone book, missed call lists, etc. in progress. May need some more art work from LF designer. 
     * 5/3
       * SPEC-1382 - In sandbox and testing. Matt adding some error handling before pushing to master. 
     * 5/17 
       * SPEC-1382 - Matt working through the subtasks listed in the ticket. Coming together for FF RC1. 
     * 5/31
       * SPEC-1382 - UI related subtasks done, on-track for binding backend for RC1.
     * 6/14 
       * SPEC-1382 - Coming together. First parts submitted. Waiting for repo creation for binding. 
     * 6/28 
       * SPEC-1382 - Submitted. Ready for RC1

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into
     * 6/28 
       * Matt R still working on


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.
     * 4/19 - Still working on binder and a command line test app. Should be feature complete in next week or so and ready for review. 
     * 5/3 - Sandbox is functionally complete and Pantellis has started integrating with libqtappfw.  Should push sandbox to master so we can more widely review and test it. Will add issues as subtasks for the continuing work.  
     * 5/17 - Still in-flight. Pantellis is somewhat blocked by Matt's work. Looks like RC2.
     * 5/31 - WIP for RC2.
     * 6/14 - On track for RC2
     * 6/28 - Still on track RC2
   
   * User profiles to allow authorized users to configure Wifi and BT
   * Support for additional wifi dongles and modes. Currently station mode only. Post-FF.
   * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 

   * Discussed test methodology and packaging for CIAT tests.  Schedule a separate a call to discuss with IoT.bzh and Konsulko. Tentatively May 15 after the dev call. Scott, Matt, Matt, Sebastien, Jose, Jonathan should be invited. 
     * Had call on 5/29. Working on Build Types and deployment of wgt(s) within AppFw.

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 5/17 - Michael working on a replacement to the HVAC firmware. Should be finished next week. Soya is working with Kusakabe in Japan to get this working.  
     * 5/31 
       * New HVAC firmware done (Michael / MCHP). New hardware/new firmware for HVAC controller board.
       * Kusakabe-san: Kingfisher + LIN works.
     * 6/14 
       * Kusakabe successfully integrated new LIN transceiver into ALS demo. 
       * Microchip successfully integrated new firmware for the HVAC controller board into the ALS demo. 
     * 6/28 
       * Kusakabe pushing new LIN kernel module and HVAC application into master next week.
       * Next will look at haptic devices.

New Business:


==== June 14, 2018 ====
Attendees: Walt,  Jan-Simon, Matt Porter, Sebastien, Romain, Ronan

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section. 
     * 3/22
       * SPEC-1339 - Jonathan working on stabilization of low level CAN binding - merged in gerrit
       * SPEC-1347 - Adding "EngineOn" to low level CAN binding
       * New binding in progress to store metrics on vehicle bus. Could be used for supervision, remote diagnostics or black box use cases.
       * SPEC-1344 - Check with Jan-Simon
     * 4/5 
       * SPEC-1344 - Done
       * SPEC-1347 - Jonathan almost finished. 
       * SPEC-1381 - Next up for Jonathan - Adding vehicle message dictionaries to low-level CAN
       * Test cases - Start with CAN low-level services. 
     * 4/19
       * Discussions with Oliver Hartkopp went well last week in Karlsruhe.
       * Jonathan still chugging along. 
       * Romain - add namespace usage based on discussion with Oliver probably after FF. Requires kernel 4.12 or later. 
     * 5/3
       * SPEC-1419 - Romain working on changing the signal composer to a more flexible meta-data storage model. Need Jira ticket. 
       * Jonathan working on testing the low level CAN. See discussion below about creating reusable test plans. 
     * 5/17
       * SPEC-1419 - Will not be available until the end of June. Romain on vacation the next three weeks. 
       * SPEC-1407 - Data collection for V2C use cases. Most likely a demo for AMM and targeted for Grumpy Guppy. 
       * Jonathan continuing with test plans and procedures for low-level CAN. (Need Jira)
     * 5/31
       * Progress on signal-composer using openxc, code on github, to be submitted when Romain is back.
       * SPEC-1419 and SPEC-1407 WIP
       * Jonathan worked on tests for the low-can service, Romain started to integrate these into a test binding (using lua scripts to test low-can).
         * https://github.com/iotbzh/afb-test
         * https://github.com/iotbzh/afb-test/blob/master/conf.d/project/lua.d/low-can-tests.lua
     * 6/14 
       * Signal composer changes will be pushed ASAP by Romain now that he is bacl
       * Romain working on lua scripts for low level can tests. Should be ready next week. 

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 4/19 - Matt R. posted patches to rework the Bluetooth settings app 
     * 5/4 - Matt R. still hammering away it. A bunch of patches were merged. 
     * 5/17 - Matt R. back ports to eel have been submitted. Testing these because it looks like there have been some regressions on eel. Not sure if this is related to the backports or something else. 
       * Asynchronous disconnect and reconnect of Bluetooth devices is not being handled correctly by the binding. Matt P. working on fixes for that. 
     * 5/31 - Matt R sent all fixes to Eel. Matt R also tested in 'real life' environment.
     * 6/14 - Set for ALS on Eel 

   * Telephony Updates
     * PBAP and Contact app in progress. 
     * 4/5 
       * SPEC-1382 - PBAB and Contact App - Binding ready. Integration in progress. 
     * 4/19 
       * SPEC-1382 - Rewrite of the phone app to include tabs for phone book, missed call lists, etc. in progress. May need some more art work from LF designer. 
     * 5/3
       * SPEC-1382 - In sandbox and testing. Matt adding some error handling before pushing to master. 
     * 5/17 
       * SPEC-1382 - Matt working through the subtasks listed in the ticket. Coming together for FF RC1. 
     * 5/31
       * SPEC-1382 - UI related subtasks done, on-track for binding backend for RC1.
     * 6/14 
       * SPEC-1382 - Coming together. First parts submitted. Waiting for repo creation for binding. 

   * NFC - Use of NFC for user identification. 
     * On-hold
     * 6/14 
       * Matt R started digging into


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.
     * 4/19 - Still working on binder and a command line test app. Should be feature complete in next week or so and ready for review. 
     * 5/3 - Sandbox is functionally complete and Pantellis has started integrating with libqtappfw.  Should push sandbox to master so we can more widely review and test it. Will add issues as subtasks for the continuing work.  
     * 5/17 - Still in-flight. Pantellis is somewhat blocked by Matt's work. Looks like RC2.
     * 5/31 - WIP for RC2.
     * 6/14 - On track for RC2
   
   * User profiles to allow authorized users to configure Wifi and BT
   * Support for additional wifi dongles and modes. Currently station mode only. Post-FF.
   * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 

   * Discussed test methodology and packaging for CIAT tests.  Schedule a separate a call to discuss with IoT.bzh and Konsulko. Tentatively May 15 after the dev call. Scott, Matt, Matt, Sebastien, Jose, Jonathan should be invited. 
     * Had call on 5/29. Working on Build Types and deployment of wgt(s) within AppFw.

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 5/17 - Michael working on a replacement to the HVAC firmware. Should be finished next week. Soya is working with Kusakabe in Japan to get this working.  
     * 5/31 
       * New HVAC firmware done (Michael / MCHP). New hardware/new firmware for HVAC controller board.
       * Kusakabe-san: Kingfisher + LIN works.
     * 6/14 
       * Kusakabe successfully integrated new LIN transceiver into ALS demo. 
       * Microchip successfully integrated new firmware for the HVAC controller board into the ALS demo. 

New Business:


==== May 31, 2018 ====
Attendees: Jan-Simon, Jonathan Aillet, Matt Porter, Kusakabe-san, 

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section. 
     * 3/22
       * SPEC-1339 - Jonathan working on stabilization of low level CAN binding - merged in gerrit
       * SPEC-1347 - Adding "EngineOn" to low level CAN binding
       * New binding in progress to store metrics on vehicle bus. Could be used for supervision, remote diagnostics or black box use cases.
       * SPEC-1344 - Check with Jan-Simon
     * 4/5 
       * SPEC-1344 - Done
       * SPEC-1347 - Jonathan almost finished. 
       * SPEC-1381 - Next up for Jonathan - Adding vehicle message dictionaries to low-level CAN
       * Test cases - Start with CAN low-level services. 
     * 4/19
       * Discussions with Oliver Hartkopp went well last week in Karlsruhe.
       * Jonathan still chugging along. 
       * Romain - add namespace usage based on discussion with Oliver probably after FF. Requires kernel 4.12 or later. 
     * 5/3
       * SPEC-1419 - Romain working on changing the signal composer to a more flexible meta-data storage model. Need Jira ticket. 
       * Jonathan working on testing the low level CAN. See discussion below about creating reusable test plans. 
     * 5/17
       * SPEC-1419 - Will not be available until the end of June. Romain on vacation the next three weeks. 
       * SPEC-1407 - Data collection for V2C use cases. Most likely a demo for AMM and targeted for Grumpy Guppy. 
       * Jonathan continuing with test plans and procedures for low-level CAN. (Need Jira)
     * 5/31
       * Progress on signal-composer using openxc, code on github, to be submitted when Romain is back.
       * SPEC-1419 and SPEC-1407 WIP
       * Jonathan worked on tests for the low-can service, Romain started to integrate these into a test binding (using lua scripts to test low-can).
         * https://github.com/iotbzh/afb-test
         * https://github.com/iotbzh/afb-test/blob/master/conf.d/project/lua.d/low-can-tests.lua

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 4/19 - Matt R. posted patches to rework the Bluetooth settings app 
     * 5/4 - Matt R. still hammering away it. A bunch of patches were merged. 
     * 5/17 - Matt R. back ports to eel have been submitted. Testing these because it looks like there have been some regressions on eel. Not sure if this is related to the backports or something else. 
       * Asynchronous disconnect and reconnect of Bluetooth devices is not being handled correctly by the binding. Matt P. working on fixes for that. 
     * 5/31 - Matt R sent all fixes to Eel. Matt R also tested in 'real life' environment.

   * Telephony Updates
     * PBAP and Contact app in progress. 
     * 4/5 
       * SPEC-1382 - PBAB and Contact App - Binding ready. Integration in progress. 
     * 4/19 
       * SPEC-1382 - Rewrite of the phone app to include tabs for phone book, missed call lists, etc. in progress. May need some more art work from LF designer. 
     * 5/3
       * SPEC-1382 - In sandbox and testing. Matt adding some error handling before pushing to master. 
     * 5/17 
       * SPEC-1382 - Matt working through the subtasks listed in the ticket. Coming together for FF RC1. 
     * 5/31
       * SPEC-1382 - UI related subtasks done, on-track for binding backend for RC1.

   * NFC - Use of NFC for user identification. 
     * On-hold


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.
     * 4/19 - Still working on binder and a command line test app. Should be feature complete in next week or so and ready for review. 
     * 5/3 - Sandbox is functionally complete and Pantellis has started integrating with libqtappfw.  Should push sandbox to master so we can more widely review and test it. Will add issues as subtasks for the continuing work.  
     * 5/17 - Still in-flight. Pantellis is somewhat blocked by Matt's work. Looks like RC2.
     * 5/31 - WIP for RC2.
   
   * User profiles to allow authorized users to configure Wifi and BT
   * Support for additional wifi dongles and modes. Currently station mode only. Post-FF.
   * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 

   * Discussed test methodology and packaging for CIAT tests.  Schedule a separate a call to discuss with IoT.bzh and Konsulko. Tentatively May 15 after the dev call. Scott, Matt, Matt, Sebastien, Jose, Jonathan should be invited. 
     * Had call on 5/29. Working on Build Types and deployment of wgt(s) within AppFw.

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 5/17 - Michael working on a replacement to the HVAC firmware. Should be finished next week. Soya is working with Kusakabe in Japan to get this working.  
     * 5/31 
       * New HVAC firmware done (Michael / MCHP). New hardware/new firmware for HVAC controller board.
       * Kusakabe-san: Kingfisher + LIN works.

New Business:
  * 5/31


==== May 17, 2018 ====
Attendees: Walt, Sebastien, Michael, Stephane, Romain, Jonathan, Matt, Tiejun


   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section. 
     * 3/22
       * SPEC-1339 - Jonathan working on stabilization of low level CAN binding - merged in gerrit
       * SPEC-1347 - Adding "EngineOn" to low level CAN binding
       * New binding in progress to store metrics on vehicle bus. Could be used for supervision, remote diagnostics or black box use cases.
       * SPEC-1344 - Check with Jan-Simon
     * 4/5 
       * SPEC-1344 - Done
       * SPEC-1347 - Jonathan almost finished. 
       * SPEC-1381 - Next up for Jonathan - Adding vehicle message dictionaries to low-level CAN
       * Test cases - Start with CAN low-level services. 
     * 4/19
       * Discussions with Oliver Hartkopp went well last week in Karlsruhe.
       * Jonathan still chugging along. 
       * Romain - add namespace usage based on discussion with Oliver probably after FF. Requires kernel 4.12 or later. 
     * 5/3
       * SPEC-1419 - Romain working on changing the signal composer to a more flexible meta-data storage model. Need Jira ticket. 
       * Jonathan working on testing the low level CAN. See discussion below about creating reusable test plans. 
     * 5/17
       * SPEC-1419 - Will not be available until the end of June. Romain on vacation the next three weeks. 
       * SPEC-1407 - Data collection for V2C use cases. Most likely a demo for AMM and targeted for Grumpy Guppy. 
       * Jonathan continuing with test plans and procedures for low-level CAN. (Need Jira)

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 4/19 - Matt R. posted patches to rework the Bluetooth settings app 
     * 5/4 - Matt R. still hammering away it. A bunch of patches were merged. 
     * 5/17 - Matt R. back ports to eel have been submitted. Testing these because it looks like there have been some regressions on eel. Not sure if this is related to the backports or something else. 
       * Asynchronous disconnect and reconnect of Bluetooth devices is not being handled correctly by the binding. Matt P. working on fixes for that. 

   * Telephony Updates
     * PBAP and Contact app in progress. 
     * 4/5 
       * SPEC-1382 - PBAB and Contact App - Binding ready. Integration in progress. 
     * 4/19 
       * SPEC-1382 - Rewrite of the phone app to include tabs for phone book, missed call lists, etc. in progress. May need some more art work from LF designer. 
     * 5/3
       * SPEC-1382 - In sandbox and testing. Matt adding some error handling before pushing to master. 
     * 5/17 
       * SPEC-1382 - Matt working through the subtasks listed in the ticket. Coming together for FF RC1. 

   * NFC - Use of NFC for user identification. 
     * On-hold


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.
     * 4/19 - Still working on binder and a command line test app. Should be feature complete in next week or so and ready for review. 
     * 5/3 - Sandbox is functionally complete and Pantellis has started integrating with libqtappfw.  Should push sandbox to master so we can more widely review and test it. Will add issues as subtasks for the continuing work.  
     * 5/17 - Still in-flight. Pantellis is somewhat blocked by Matt's work. Looks like RC2.

   * User profiles to allow authorized users to configure Wifi and BT
   * Support for additional wifi dongles and modes. Currently station mode only. 
   * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the code incorporated into kernel. 

   * Discussed test methodology and packaging for CIAT tests.  Schedule a separate a call to discuss with IoT.bzh and Konsulko. Tentatively May 15 after the dev call. Scott, Matt, Matt, Sebastien, Jose, Jonathan should be invited. 

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. 
     * 5/17 - Michael working on a replacement to the HVAC firmware. Should be finished next week. Soya is working with Kusakabe in Japan to get this working.  

New Business:



==== May 3, 2018 ====
Attendees: Walt, Jan-Simon, Romain, Michael, Matt, Sebastien, Jonathan

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section. 
     * 3/22
       * SPEC-1339 - Jonathan working on stabilization of low level CAN binding - merged in gerrit
       * SPEC-1347 - Adding "EngineOn" to low level CAN binding
       * New binding in progress to store metrics on vehicle bus. Could be used for supervision, remote diagnostics or black box use cases.
       * SPEC-1344 - Check with Jan-Simon
     * 4/5 
       * SPEC-1344 - Done
       * SPEC-1347 - Jonathan almost finished. 
       * SPEC-1381 - Next up for Jonathan - Adding vehicle message dictionaries to low-level CAN
       * Test cases - Start with CAN low-level services. 
     * 4/19
       * Discussions with Oliver Hartkopp went well last week in Karlsruhe.
       * Jonathan still chugging along. 
       * Romain - add namespace usage based on discussion with Oliver probably after FF. Requires kernel 4.12 or later. 
     * 5/3
       * SPEC-1419 - Romain working on changing the signal composer to a more flexible meta-data storage model. Need Jira ticket. 
       * Jonathan working on testing the low level CAN. See discussion below about creating reusable test plans. 

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 4/19 - Matt R. posted patches to rework the Bluetooth settings app 
     * 5/4 - Matt R. still hammering away it. A bunch of patches were merged. 

   * Telephony Updates
     * PBAP and Contact app in progress. 
     * 4/5 
       * SPEC-1382 - PBAB and Contact App - Binding ready. Integration in progress. 
     * 4/19 
       * SPEC-1382 - Rewrite of the phone app to include tabs for phone book, missed call lists, etc. in progress. May need some more art work from LF designer. 
     * 5/3
       * SPEC-1382 - In sandbox and testing. Matt adding some error handling before pushing to master. 

   * NFC - Use of NFC for user identification. 


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.
     * 4/19 - Still working on binder and a command line test app. Should be feature complete in next week or so and ready for review. 
     * 5/3 - Sandbox is functionally complete and Pantellis has started integrating with libqtappfw.  Should push sandbox to master so we can more widely review and test it. Will add issues as subtasks for the continuing work.  

   * User profiles to allow authorized users to configure Wifi and BT
   * Support for additional wifi dongles and modes. Currently station mode only. 
   * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the 

New Business:
   * Discussed test methodology and packaging for CIAT tests.  Schedule a separate a call to discuss with IoT.bzh and Konsulko. Tentatively May 15 after the dev call. Scott, Matt, Matt, Sebastien, Jose, Jonathan should be invited. 

   * Kusakabe-san is working to replace the Mocca box with a small LIN transceiver but having some problem with the HVAC hardware. Michael trying to help Kusakabe out, but cannot get in touch with him due to Golden Week in Japan. 


==== April 19, 2018 ====
Attendees:Walt, Jan-Simon, Sebastien, Jonathan, Romain, Michael

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section. 
     * 3/22
       * SPEC-1339 - Jonathan working on stabilization of low level CAN binding - merged in gerrit
       * SPEC-1347 - Adding "EngineOn" to low level CAN binding
       * New binding in progress to store metrics on vehicle bus. Could be used for supervision, remote diagnostics or black box use cases.
       * SPEC-1344 - Check with Jan-Simon
     * 4/5 
       * SPEC-1344 - Done
       * SPEC-1347 - Jonathan almost finished. 
       * SPEC-1381 - Next up for Jonathan - Adding vehicle message dictionaries to low-level CAN
       * Test cases - Start with CAN low-level services. 
     * 4/19
       * Discussions with Oliver Hartkopp went well last week in Karlsruhe.
       * Jonathan still chugging along. 
       * Romain - add namespace usage based on discussion with Oliver probably after FF. Requires kernel 4.12 or later. 

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 
     * 4/19 - Matt R. posted patches to rework the Bluetooth settings app 

   * Telephony Updates
     * PBAP and Contact app in progress. 
     * 4/5 
       * SPEC-1382 - PBAB and Contact App - Binding ready. Integration in progress. 
     * 4/19 
       * SPEC-1382 - Rewrite of the phone app to include tabs for phone book, missed call lists, etc. in progress. May need some more art work from LF designer. 

   * NFC - Use of NFC for user identification. 


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.
     * 4/19 - Still working on binder and a command line test app. Should be feature complete in next week or so and ready for review. 

   * User profiles to allow authorized users to configure Wifi and BT
   * Support for additional wifi dongles and modes. Currently station mode only. 
   * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the 

New:

Code reviewers for EG: Matt, Romain, Kusakabe, Scott, Jonathan


==== April 5, 2018 ====
Attendees: Walt, Jan-Simon, Sebastien, Romain, Dennis, Stephane, Jonathan, Matt, Michael

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section. 
     * 3/22
       * SPEC-1339 - Jonathan working on stabilization of low level CAN binding - merged in gerrit
       * SPEC-1347 - Adding "EngineOn" to low level CAN binding
       * New binding in progress to store metrics on vehicle bus. Could be used for supervision, remote diagnostics or black box use cases.
       * SPEC-1344 - Check with Jan-Simon
     * 4/5 
       * SPEC-1344 - Done
       * SPEC-1347 - Jonathan almost finished. 
       * SPEC-1381 - Next up for Jonathan - Adding vehicle message dictionaries to low-level CAN
       * Test cases - Start with CAN low-level services. 

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 

   * Telephony Updates
     * PBAP and Contact app in progress. 
     * 4/5 
       * SPEC-1382 - PBAB and Contact App - Binding ready. Integration in progress. 

   * NFC - Use of NFC for user identification. 


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress
     * 4/5 - Pantellis still working. Initial prototype should be ready in the next two weeks.

   * User profiles to allow authorized users to configure Wifi and BT
   * Support for additional wifi dongles and modes. Currently station mode only. 
   * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
 
   * SafeRide Proposal - Oshri was emailing Oliver H. about getting the 

New:

Code reviewers for EG: Matt, Romain, Kusakabe, Scott, Stephane


==== March 22, 2018 ====
Attendees: Walt, Romain, Jonathan, Matt

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section. 
     * 3/22
       * SPEC-1339 - Jonathan working on stabilization of low level CAN binding - merged in gerrit
       * SPEC-1347 - Adding "EngineOn" to low level CAN binding
       * New binding in progress to store metrics on vehicle bus. Could be used for supervision, remote diagnostics or black box use cases.
       * SPEC-1344 - Check with Jan-Simon

   * Bluetooth and Wifi Updates
     * Dependent on network connectivity update below. 

   * Telephony Updates
     * PBAP and Contact app in progress. Matt to create Jira ticket. 

   * NFC - Use of NFC for user identification. 


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * SPEC-1274 - In progress

   * User profiles to allow authorized users to configure Wifi and BT
   * Support for additional wifi dongles and modes. Currently station mode only. 
   * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
 
   * SafeRide Proposal 

New:

==== March 8, 2018 ====
Attendees: Walt, Jan-Simon, Michael, Sebastien, Romain, Jonathan

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG
  
   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * Run-time creation of virtual messages has been added to master
       * Documentation at http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/signal-composer-api.html. See "AddObjects" section. 
     * Jonathan working on stabilization of signal composer. Will create a Jira ticket to track the work. 

   * Bluetooth and Wifi Updates

   * Telephony Updates

   * NFC - Use of NFC for user identification. 


   * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
     * User profiles to allow authorized users to configure Wifi and BT
     * Support for additional wifi dongles and modes. Currently station mode only. 
     * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
 

New:
   * SafeRide Proposal 


==== January 25, 2018 ====
Attendees: Walt, Jan-Simon, Sebastien, Stephane, Michael, Christian

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG

   * CES Demo
     * Kingfisher Advanced board proposed to be used. Late  October deliver expected from Shimafuji. IoT.bzh will start looking at their board to verify the in BSP and connectivity to the external modules. 
     * 11/2 - Kingfisher boards arrived in Yokohama. BSP in progress at IoT.bzh, but they are having issues because Cogent did a "proof of concept" BSP that is a fork of an older Renesas BSP and there is no easy way to port if to the current upstream Renesas BSP. 
     * 11/16 - Ongoing work in Yokohama
     * 11/30 - BSP being sorted out. Kingfisher being merged to master in meta-renesas-rcar-gen3 but there are a quite a few (60+) patches to be merged. Konsulko does not have the board, except for Scott. Backup plan to use ULCB with a bunch of USB dongles would still be a problem with BT audio for telephony.  

   * Vehicle Signaling
     * High Level ViWi Service available on github (https://github.com/iotbzh/high-level-viwi-service)
     * 11/2 - Work delayed because Romain was pulled into Window Manager effort. Concern that there is not a set of reference CAN messages or an reference app to make available as part of the release. Walt would like to get the code into EE to encourage people to start using it and we can fix any defects as they are found. 
     * 11/16 - No progress. Romain still working on Window Manager, HMI, XDG, etc effort. 
     * 11/30 - Romain did some work on the signal composer. Need to create a list of features and test apps available for EE. 
     * 12/14 - agl-service-signal-composer repo created. Romain pushed his code there. Need to make a recipe for RC5 to make it available for EE. Documentation will be updated on the web site as well. 

   * Bluetooth and Wifi Updates
     * A2DP, HFP, AVRCP included in DD with reference apps. 
     * EE improvements
       * 11/2 - Matt working on fixing the new UI pushed by ALPS.
       * 11/16 - Bluez/ALSA and ofono/PulseAudio integrations needs to be completed for EE.  
       * 11/30 - Bluetooth audio for telephony is an issue on Renesas Gen3. TI with BT dongle on Eel works for old audio manager, but NOT 4a.  Neither case works for Gen3. 
       * 12/14 - See SPEC-1175 for details on KF board. 

   * Telephony Updates
     * Initial implementation in DD with reference phone app. 
     * EE improvements
       * Move to a standalone service binding
       * Build out feature set for telephony (multipart call, phone book, reliability)
     * Update 10.8.: 
       * Update to v2 and aligning verbs used between bindings. 
       * Work on moving to a standalone binding.
       * Looking into phone book profile
     * Update 8/24
       * Telephone binding now standalone. 
       * Working on verb syntax for bindings. Will discuss at the F2F in Yokohama next week.
       * Phone book and contact database investigations ongoing. Matt P. looking at best practices in other spaces (Android, etc.)
     * 9/7 - No update
     * 9/20 - Looking at regressions introduced in the pyro update to master. 
     * 10/5 - Matt looking at asynchronous events to the telephone QML app. Having issues with the SCO voice connection for HFP so Matt is working with Vayu rather ULCB. 
     * 11/2 - Everything is in except the cleanup to make it standalone. Asynchronous event handing code is in progress. Talked about whether/ how to make it generic in such a way to make it work with GUI toolkits other than Qt, but that is a much bigger job. 
     * 11/16 - Work completed on asynchronous event handling for telephony.
     * 12/14 - SCO issues with KF persist. See SPEC-1175 for any updates. 

   * Roadmap items
     * NFC - Use of NFC for user identification. 
       * 10/5 - Will have binding for EE available. Still working on the exact solution whether it is user space (lib-nfc) or kernel driver (neard). Problems with getting data from "random" chips since there a multitude of different RFID solutions out there. Should be ok for the demo case where we use known chips. 
       * 11/1 - First version released (https://github.com/iotbzh/nfc-binding) See the github page for a list of tags that have been tested. There have been issues with the ARC122U readers. 
       * 11/16 - No update
       * 11/30 - Stephane will push the latest binding to gerrit. Need to get the working reader and tags to Yokohama that will be shipped to Las Vegas. IoT.bzh will provide them. 
       * 12/14 - meta-nfc and other repos were created today. Work is progressing in Yokohama and France.  

     * V2X Connectivity 
       * V2C EG proposed at San Jose F2F. In progress of forming that now. 
       * 10/5 - Want to kick off in Dresden.

     * Bluetooth profiles -
       * Phone book/contacts
         * 10/5 - See above. 
         * 11/1 - On hold. 
         * 11/30 - On hold. 
         * 12/14 - On hold

     * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
       * User profiles to allow authorized users to configure Wifi and BT
       * Support for additional wifi dongles and modes. Currently station mode only. 
       * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 



    * Look at open car for Honda bus information to pull together a steering wheel demo. 

New:


==== February 8, 2018 ====
Attendees: Walt, Jan-Simon, Sebastien, Stephane, Michael, Christian, Romain, 

   * Review [[:agl-roadmap#from_connectivity_eg|2018 Roadmap]] for Connectivity EG

   * Vehicle Signaling
     * 2/8 - Romain and Jonathan investigating adding J1939 to CAN protocol. Demo of the signal composer binding is being planned to be shown later in the year (Apr/Jun). 

   * Bluetooth and Wifi Updates
     * A2DP, HFP, AVRCP included in DD with reference apps. 
     * EE improvements
       * 11/2 - Matt working on fixing the new UI pushed by ALPS.
       * 11/16 - Bluez/ALSA and ofono/PulseAudio integrations needs to be completed for EE.  
       * 11/30 - Bluetooth audio for telephony is an issue on Renesas Gen3. TI with BT dongle on Eel works for old audio manager, but NOT 4a.  Neither case works for Gen3. 
       * 12/14 - See SPEC-1175 for details on KF board. 
       * 2/8 - No update

   * Telephony Updates
     * 2/8 - Ronan working on getting Bluetooth/ Pulseaudio working with 4a. 
 

   * Roadmap items
     * NFC - Use of NFC for user identification. 
       * 2/8 - Will reevaluate support NFC support after rocko update is complete to see if the kernel updates bring better support with it. NFC binder support will move to Konsulko.  

     * V2X Connectivity 
       * V2C EG proposed at San Jose F2F. In progress of forming that now. 
       * 10/5 - Want to kick off in Dresden.

     * Bluetooth profiles -
       * Phone book/contacts
         * 2/8 - Matt now debugging PBAP binding. 

     * General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
       * User profiles to allow authorized users to configure Wifi and BT
       * Support for additional wifi dongles and modes. Currently station mode only. 
       * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. 
       * 2/8 - Assigned to Konsulko

New:


==== January 11, 2018 ====
Attendees: //Upcoming Meeting//
Cancel due to CES. 


==== Pre-2018 Meeting minutes ====

Minutes from meetings prior to 2018 have been [[eg-connectivity:meetings:archive|archived here]].
Automotive Linux Wiki

User Tools

Site Tools

Page Tools
