Automotive Linux Wiki

Meetings of the Connectivity EG are held every other Thursday. The upcoming schedule can be found on the 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 meeting minutes for details.

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.

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.

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:

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:

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:

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:

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:

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:

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:

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:

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:

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

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

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 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

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 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

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 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:

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 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:

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 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 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 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 ICCOM to AGL.
• Eric mentioned ErikaOS ( github and https://www.erika-enterprise.com/website) as a possible open source Implementation of Autosar in the future.

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 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 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 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:

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 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 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:

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 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 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.

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 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 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:

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 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:

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:

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:

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 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 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:

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 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 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:

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 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 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:

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 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 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:

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 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

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 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

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 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

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 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:

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 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.

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 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

Attendees: Walt, Jan-Simon, Scott, Richard

• 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 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:

Attendees: Walt, Scott, Thomas,

• 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 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 EG feature list.

Attendees: Walt, Jan-Simon, Scott, Thomas, Richard, Kurokawa

• 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 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 EG feature list.

Attendees: Walt, Jan-Simon, Scott, Thomas, Richard E

• 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 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:

Attendees: Walt, Jan-Simon, Scott, Thomas, Richard E

• 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 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:

Attendees: Walt, Jan-Simon, Scott, Tanikawa, Thomas, Richard E

• 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 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:

Attendees: Walt, Jan-Simon, Scott, Tanikawa

• 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 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:

Attendees: Walt, Jan-Simon, Scott, Thomas, Sekine, Tanikawa, Li

• 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 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:

Attendees: Jan-Simon, Scott, Thomas, Dennis

• 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 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.

Attendees: Jan-Simon, Scott, Thomas,

• 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 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

Attendees: Walt, Jan-Simon, Thomas, Scott, Kurokawa, Tanikawa

• 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 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:

Canceled due to Yocto Project Summit

Attendees: Walt, Jan-Simon, Michael, Thomas, Nomoto-san, Scott, Tanikawa-san

• 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:

Attendees: Walt, Jan-Simon, Scott, Thomas, Nimoto, Kimura

• 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:

Attendees: Jan-Simon, Scott, Michael, Furuta, Nomoto, Kimura, Kusakabe

• 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 plan for Bluetooth development and 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 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 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:

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

• 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 plan for Bluetooth development and 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 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 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:

Attendees: Walt, Scott, Li, Thomas, Kurokawa, Furuta, Kimura, Nomoto, Monden, Michael

• 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 plan for Bluetooth development and 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 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 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:

Attendees: Walt, Jan-Simon, Scott, Thomas, Li

• 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 plan for Bluetooth development and 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 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 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:

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

• 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 plan for Bluetooth development and 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 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 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:

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

• 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 plan for Bluetooth development and 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 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 https://www.monkeyboard.org/products/85-developmentboard/80-dab-fm-digital-radio-development-board as another option for hardware integration,.

New:

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

• 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 plan for Bluetooth development and 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 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:

Meeting Canceled

Attendees: Walt, Jan-Simon, Scott, Ohiwa, Thomas, Nomoto, Kusakabe

• 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 plan for Bluetooth development and 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 SPEC-3311 that defines an example radio hardware block diagram.
  • 5/14 - No update from Kusakabe-san.

New:

Attendees: Walt, Jan-Simon, Scott, Ohiwa, Thomas, Nomoto, Swapnil

• 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 SPEC-3311 that defines an example radio hardware block diagram.

New:

Attendees: Walt, Jan-Simon, Scott, Ohiwa, Thomas, Nomoto, Parth

• 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 SPEC-3311 that defines an example radio hardware block diagram.

New:

Attendees: Walt, Jan-Simon, Scott, Thomas, Nomoto, Kusakabe, Ohiwa, Michael, Tanikawa

• 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 SPEC-3311 that defines an example radio hardware block diagram.

New:

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

• 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:

Attendees: Walt, Jan-Simon, Scott, Li, Kusakabe, Marat, Andrey, Leonid, Mikhail, Thomas

• Reviewed and updated the 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.

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

• Reviewed and updated the 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:

Attendees: Walt, Jan-Simon, Thomas, Scott, Kusakabe, Michael

• Reviewed and updated the 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.

Attendees: Jan-Simon, Michael, Sharath, Li, George

• Review 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.
    • 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:

Attendees: Walt, Jan-Simon, Scott, Romain, Kusakabe

• Review 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.
    • 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

Attendees: Walt, Jan-Simon, Scott, Romain, Michael, Kusakabe, Ashvinid

• Review 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.
    • 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.