Nrf connect
Author: f | 2025-04-24
Threads in an nRF Connect SDK application. Complete the following steps using nRF Debug View in nRF Connect for VS Code to find information about the threads in an nRF Connect Installed nRF Command-Line Tools v10.16.0; Installed nRF Connect for Desktop v3.11. Installed Toolchain Manger v1.1.1 from nRF Connect for Desktop; Installed nRF Connect SDK v2.0.0 from Toolchain Manager; Clicked Open in VS Code Installed VS Code extensions; Go to Welcome nRF Connect screen, Quick Setup: nRF Connect SDK: 2.0.0; nRF Connect
nRF Dongle nRF Connect for Desktop hardware
I am trying to get nRF Connect 1.0.0 to bond with my sensor (which uses a nRF52832). This works from several other programs (CySmart on Windows, LightBlue on iPhone), but not with nRF Connect. This is the log I see. I tried both Windows 10 and Mac OS X (El Capitan 10.11.6).The "dongle" is a PCA10040 with the firmware "connectivity_115k2_with_s132_2.0.1.hex". After reading this post I also tried "connectivity_1.0.1_115k2_with_s132_3.0.hex", but this results in nRF Connect throwing errors continuously after connecting to the device (INTERNAL... error).As I understand it nRF Connect is built on top of the pc-ble-driver which I am currently evaluating. We want to be able to make a secure connection (bond) with our sensor like in this post.This is our goal and I would like to use nRF Connect as a reference.Update 2016_12_01 #1The Sensor uses "Just Works" with the following values. I matched these in nRF Connect (and experimented with different ones as well to no avail).sec_param.bond = 1;sec_param.mitm = 0;sec_param.lesc = 1;sec_param.keypress = 0;sec_param.io_caps = SEC_PARAM_IO_CAPABILITIES;sec_param.oob = 0;sec_param.min_key_size = 7;sec_param.max_key_size = 16;sec_param.kdist_own.enc = 1;sec_param.kdist_own.id = 1;sec_param.kdist_peer.enc = 1;sec_param.kdist_peer.id = 1;The log output of nRFConnect is attached: 2016-12-01T19_37_13.857Z-log copy.txt. On the sensor side I receive the following events:BLE_GAP_EVT_CONNECTEDPM_EVT_CONN_SEC_START: peer_id=65535BLE_GAP_EVT_SEC_PARAMS_REQUESTAnd after 30 seconds or so:PM_EVT_CONN_SEC_FAILED: peer_id=65535, error=1BLE_GAP_EVT_AUTH_STATUS: status=0x1 bond=0x0 lv4: 0 kdist_own:0x1 kdist_peer:0x0I'll try the glucose example tomorrow.Update 2016_12_02 #1The "glucose example" has issues as well, but in this case seemingly on the sensor side.Note that it uses different security parameters (MITM, no LESC). I'll try modifying these next, but I am out of time for today.Log from the peripheral side:SDH:INFO:sd_ble_enable: RAM START at 0x20002128APP:INFO:Log level = 4APP:INFO:GLS Starting...!APP:INFO:Fast advertisingAPP:INFO:ConnectedAPP:DEBUG:Start encryptionAPP:INFO:PM_EVT_CONN_SEC_STARTAPP:DEBUG:BLE_GAP_EVT_SEC_PARAMS_REQUESTAPP:INFO:BLE_GAP_EVT_PASSKEY_DISPLAYAPP:INFO:Passkey: 083117APP:INFO:PM_EVT_CONN_SEC_SUCCEEDEDAPP:DEBUG:Link secured. Role: 1. conn_handle: 0, Procedure: 2APP_ERROR:ERROR:FatalSDH:INFO:sd_ble_enable: RAM START at 0x20002128APP:INFO:Log level = 4APP:INFO:GLS Starting...!APP:INFO:Fast advertisingLog from the nRF Connect side (attached).Your help is very much appreciated!Cheers,Dirk
nRF Dongle nRF Connect for Desktop hardware - Nordic
NRF Connect for Mobile is a powerful generic tool that allows you to scan, advertise and explore your Bluetooth Low Energy (BLE) devices and communicate with them. nRF Connect supports number of Bluetooth SIG adopted profiles together with Device Firmware Update profile (DFU) from Nordic Semiconductors and Mcu Manager on Zephyr and Mynewt.Features:- Scans for Bluetooth Low Energy (BLE) devices- Parses advertisement data- Shows RSSI graph, allows export to CSV and Excel formats- Connects to a connectible the Bluetooth LE device- Discoveries and parses services and characteristics- Allows to read and write characteristics- Allows to enable and disable notifications and indications- Supports Reliable Write- Parses number of characteristics adopted by Bluetooth SIG- Bluetooth LE advertising (Android 5+ required)- Read and update PHY (Android 8+ required)- GATT Server configuration- Supports Device Firmware Update (DFU) profile which let the user to upload a new application, SoftDevice or a bootloader over-the-air (OTA)- Supports McuMgr, profile that lets the user control and update Zephyr-based devices- Supports the Nordic UART Service- Allow to record and replay common operations using Macros- Allows to perform automated tests defined in XML file on Bluetooth LE devices.Visit the GitHub page: github.com/NordicSemiconductor/Android-nRF-Connect for more information about automated tests.Note:- Supported on Android version 4.3 or later.- nRF5x Development kits can be ordered from www.nordicsemi.com/eng/Buy-Online.Works well with nRF Logger application, that will store your logs in case something bad happens with nRF Connect.Download nRF Logger from: play.google.com/store/apps/details?id=no.nordicsemi.android.logSPI example for nRF with nRF Connect SDK 2.3.0
Events, Upcoming Events ProMat: March 17-20, 2025 Schedule time to explore Hyper-Intelligent Warehouse Orchestration at ProMat. Book a demo in advance or swing by booths #N8101 and #N8107. Read More Events, Past Events NRF: Jan. 12-14, 2025 Schedule time to see gStore and learn about intelligent inventory at NRF 2025. Meet us at Booth #3974. Read More Webinar Retail Dive Webinar On Demand: How Retailers Can Leverage RFID to Grow the Top Line This webinar with industry experts from Fabletics, Decathlon Canada, RFID Sherpas and GreyOrange will explore: – The current state of RFID technology and its use… Read More Webinar RAC 24 Mobile Robots Session: View On Demand Join industry experts for an interesting virtual mobile robots session during RAC 24. We will explore the lessons learned over the last five years of… Read More Webinar On-Demand Webinar: Boost CX with Accurate Inventory & Omnichannel Fulfillment Join the webinar as experts from Fluent Commerce and GreyOrange share how to surface accurate inventory data and ensure profitable, omnichannel fulfillment. Read More Events, Past Events Future Stores: June 3-5, 2024 Hear from L’Oréal, Macy’s and GreyOrange as we explore “Thoughtful Technology to Adapt to Changing Shopping Behaviors” during Future Stores 2024 in LA. Read More Events, Past Events DELIVER Europe: June 5-6, 2024 Meet with GreyOrange at Booth D66 to discover robotic automation solutions that are driven by results and guaranteed by outcome-specific KPIs. Read More Events, Past Events MODEX: March 11-14, 2024 Schedule time to see our AMRs and learn about results-driven robotics and multiagent orchestration at MODEX 2024. Meet us at Booth #C5692. Read More Events, Upcoming Events ProMat: March 17-20, 2025 Schedule time to explore Hyper-Intelligent Warehouse Orchestration at ProMat. Book a demo in advance or swing by booths #N8101 and #N8107. Read More Events, Past Events NRF: Jan. 12-14, 2025 Schedule time to see gStore and learn about intelligent inventory at NRF 2025. Meet us at Booth #3974. Read More Events, Past Events Future Stores: June 3-5, 2024 Hear from L’Oréal, Macy’s and GreyOrange as we explore “Thoughtful Technology to Adapt to Changing Shopping Behaviors” during Future. Threads in an nRF Connect SDK application. Complete the following steps using nRF Debug View in nRF Connect for VS Code to find information about the threads in an nRF ConnectnRF Connect SDK - nordicsemi.com
A universal asynchronous receiver/transmitter (UART) is the most popular protocol used for talking to a computer device over serial port. What I am talking here is not exactly UART in traditional sense. It's an emulation of serial port over BLE. It's not part of profiles defined by Bluetooth SIG. It's a custom defined service. It's so popular that it has become a standard. It's an equivalent of SPP (Serial Port Profile) in Bluetooth Classic but community defined. Almost all (Nordic, Adafruit, mbed) BLE hardware providers support it. I think since Nordic started it. They defined the UUIDs and details of the service ➡️ Nordic UART Service (UUID: 0x0001). The UUID of the Nordic UART Service is 6E400001-B5A3-F393-E0A9-E50E24DCCA9E. As of now every vendor uses these UUIDs for UART. Nordic's UART Android client is a great application if you like to test your UART implementation. It's Open source and available on Play store.Below is the configuration of the Service and Characteristics that I used on a hardware device (Server or GATT Server) and then I used nRF UART 2.0 Android app (Client) to connect. The service definition below is for GATT Server. Characteristic names are from client's point of view. For testing purpose you could import this into nRF Connect and make it a GATT Server. Then you can use nRF UART 2.0 to connect and then to chat. One can implement custom protocol over that chat. Since the services above are implemented on the GATT Server. The TX Characteristic will have the WRITE permission enabled so a client can write where as a client can only READ from a RX Characteristic1. Essentially two characteristic work like register to which a client can write or read from. The picture below should make it clear. UART over BLEPS1:I am doing lot of experimentsnRF Connect for Desktop - Downloads
I followed the instructions to install the nRF Connect SDK using the automatic method: worked and I was able to build sample applications and run them on the DK. Now I would also like the ability to build from the command line. The instructions say you need to start a new shell from the toolchain manager. This also works. However I cannot build from the shell if I start the shell without using the toolchain manager. How can I do that?It seems my build problems are fixed if I set the environment variable ZEPHYR_SDK_INSTALL_DIR. I noticed this variable is set when I start my shell from the Toolchain Manager but it is not set when I launch a shell normally. ZEPHYR_SDK_INSTALL_DIR=/opt/nordic/ncs/toolchains/v2.1.0/opt/zephyr-sdkSo.. If I start a regular shell (without using toolchain manager) and set this variable the builds are working. Is this a valid way to use the SDK? Let me add some background here. When I started using nRF Connect I chose the automatic installation method. This seems like the best choice to get started quickly. Then I enrolled in the nRF Connect SDK Fundamentals course. So far so good. But now I started using some of the sample projects and they all seem to use the command line to build & flash. This works fine if you open the terminal from the toolchain manager. What is not clear to me is how to switch between command line and VS Code on the same project. For example, some of the example projects use kconfig overlay files which are listed on the build commands. If I switch over to VS Code I guess I need to edit the application setup and add the kconfig file there? This behavior is new to me. I'm used to running 'make' from the command line with no options because all the details are stored in the makefiles. Then your IDE can just run the same make command. In short, I was hoping to learn how to use VS Code and the command line on the same project. In the short term I want to make this work for the sample projects but later I need to get the same behavior working with my own project. Hello,The thing that happens when you start the shell from toolchain manager is that it sets up the environmental variables for a given SDK version.You can add those variables by yourself if desired in your ~/.bashrc file for example.VS Code runs the same west commands under the hood as you would in the terminal. There should be no need to do things differently.When you build in VS Code you should be able to see the exact command used to buildnRF Connect for Desktop - nordicsemi.com
Stores 2024 in LA. Read More Events, Past Events DELIVER Europe: June 5-6, 2024 Meet with GreyOrange at Booth D66 to discover robotic automation solutions that are driven by results and guaranteed by outcome-specific KPIs. Read More Events, Past Events MODEX: March 11-14, 2024 Schedule time to see our AMRs and learn about results-driven robotics and multiagent orchestration at MODEX 2024. Meet us at Booth #C5692. Read More Events, Past Events NRF: Jan 14-16, 2024 Learn about the RFID-enabled store of the future at NRF 2024 Retail’s Big Show. Meet us at Booths #5567 and #6763 or book a live… Read More Events, Past Events Logistics Technology USA: Nov 1-2, 2023 Join us at Reuters Events Logistics Technology 2023, where we’re assembling an elite gathering of over 300 C-suite and senior management executives from North America’s… Read More Events, Past Events How to Transform Logistics with Robotic Automation & AI: Oct 24, 2023 At Logistik & Transport, James Newman, GreyOrange’s Head of EMEA, addresses the importance of fulfillment platforms and how they can transform logistics with robotic automation. Read More Events, Past Events NRF: Jan. 12-14, 2025 Schedule time to see gStore and learn about intelligent inventory at NRF 2025. Meet us at Booth #3974. Read More Events, Past Events Future Stores: June 3-5, 2024 Hear from L’Oréal, Macy’s and GreyOrange as we explore “Thoughtful Technology to Adapt to Changing Shopping Behaviors” during Future Stores 2024 in LA. Read More Events, Past Events DELIVER Europe: June 5-6, 2024 Meet with GreyOrange at Booth D66 to discover robotic automation solutions that are driven by results and guaranteed by outcome-specific KPIs. Read More Events, Past Events MODEX: March 11-14, 2024 Schedule time to see our AMRs and learn about results-driven robotics and multiagent orchestration at MODEX 2024. Meet us at Booth #C5692. Read More Events, Past Events NRF: Jan 14-16, 2024 Learn about the RFID-enabled store of the future at NRF 2024 Retail’s Big Show. Meet us at Booths #5567 and #6763 or book a live… Read More Events, Past Events Logistics Technology USA: Nov 1-2, 2023 Join us at Reuters Events. Threads in an nRF Connect SDK application. Complete the following steps using nRF Debug View in nRF Connect for VS Code to find information about the threads in an nRF Connect Installed nRF Command-Line Tools v10.16.0; Installed nRF Connect for Desktop v3.11. Installed Toolchain Manger v1.1.1 from nRF Connect for Desktop; Installed nRF Connect SDK v2.0.0 from Toolchain Manager; Clicked Open in VS Code Installed VS Code extensions; Go to Welcome nRF Connect screen, Quick Setup: nRF Connect SDK: 2.0.0; nRF ConnectComments
I am trying to get nRF Connect 1.0.0 to bond with my sensor (which uses a nRF52832). This works from several other programs (CySmart on Windows, LightBlue on iPhone), but not with nRF Connect. This is the log I see. I tried both Windows 10 and Mac OS X (El Capitan 10.11.6).The "dongle" is a PCA10040 with the firmware "connectivity_115k2_with_s132_2.0.1.hex". After reading this post I also tried "connectivity_1.0.1_115k2_with_s132_3.0.hex", but this results in nRF Connect throwing errors continuously after connecting to the device (INTERNAL... error).As I understand it nRF Connect is built on top of the pc-ble-driver which I am currently evaluating. We want to be able to make a secure connection (bond) with our sensor like in this post.This is our goal and I would like to use nRF Connect as a reference.Update 2016_12_01 #1The Sensor uses "Just Works" with the following values. I matched these in nRF Connect (and experimented with different ones as well to no avail).sec_param.bond = 1;sec_param.mitm = 0;sec_param.lesc = 1;sec_param.keypress = 0;sec_param.io_caps = SEC_PARAM_IO_CAPABILITIES;sec_param.oob = 0;sec_param.min_key_size = 7;sec_param.max_key_size = 16;sec_param.kdist_own.enc = 1;sec_param.kdist_own.id = 1;sec_param.kdist_peer.enc = 1;sec_param.kdist_peer.id = 1;The log output of nRFConnect is attached: 2016-12-01T19_37_13.857Z-log copy.txt. On the sensor side I receive the following events:BLE_GAP_EVT_CONNECTEDPM_EVT_CONN_SEC_START: peer_id=65535BLE_GAP_EVT_SEC_PARAMS_REQUESTAnd after 30 seconds or so:PM_EVT_CONN_SEC_FAILED: peer_id=65535, error=1BLE_GAP_EVT_AUTH_STATUS: status=0x1 bond=0x0 lv4: 0 kdist_own:0x1 kdist_peer:0x0I'll try the glucose example tomorrow.Update 2016_12_02 #1The "glucose example" has issues as well, but in this case seemingly on the sensor side.Note that it uses different security parameters (MITM, no LESC). I'll try modifying these next, but I am out of time for today.Log from the peripheral side:SDH:INFO:sd_ble_enable: RAM START at 0x20002128APP:INFO:Log level = 4APP:INFO:GLS Starting...!APP:INFO:Fast advertisingAPP:INFO:ConnectedAPP:DEBUG:Start encryptionAPP:INFO:PM_EVT_CONN_SEC_STARTAPP:DEBUG:BLE_GAP_EVT_SEC_PARAMS_REQUESTAPP:INFO:BLE_GAP_EVT_PASSKEY_DISPLAYAPP:INFO:Passkey: 083117APP:INFO:PM_EVT_CONN_SEC_SUCCEEDEDAPP:DEBUG:Link secured. Role: 1. conn_handle: 0, Procedure: 2APP_ERROR:ERROR:FatalSDH:INFO:sd_ble_enable: RAM START at 0x20002128APP:INFO:Log level = 4APP:INFO:GLS Starting...!APP:INFO:Fast advertisingLog from the nRF Connect side (attached).Your help is very much appreciated!Cheers,Dirk
2025-04-13NRF Connect for Mobile is a powerful generic tool that allows you to scan, advertise and explore your Bluetooth Low Energy (BLE) devices and communicate with them. nRF Connect supports number of Bluetooth SIG adopted profiles together with Device Firmware Update profile (DFU) from Nordic Semiconductors and Mcu Manager on Zephyr and Mynewt.Features:- Scans for Bluetooth Low Energy (BLE) devices- Parses advertisement data- Shows RSSI graph, allows export to CSV and Excel formats- Connects to a connectible the Bluetooth LE device- Discoveries and parses services and characteristics- Allows to read and write characteristics- Allows to enable and disable notifications and indications- Supports Reliable Write- Parses number of characteristics adopted by Bluetooth SIG- Bluetooth LE advertising (Android 5+ required)- Read and update PHY (Android 8+ required)- GATT Server configuration- Supports Device Firmware Update (DFU) profile which let the user to upload a new application, SoftDevice or a bootloader over-the-air (OTA)- Supports McuMgr, profile that lets the user control and update Zephyr-based devices- Supports the Nordic UART Service- Allow to record and replay common operations using Macros- Allows to perform automated tests defined in XML file on Bluetooth LE devices.Visit the GitHub page: github.com/NordicSemiconductor/Android-nRF-Connect for more information about automated tests.Note:- Supported on Android version 4.3 or later.- nRF5x Development kits can be ordered from www.nordicsemi.com/eng/Buy-Online.Works well with nRF Logger application, that will store your logs in case something bad happens with nRF Connect.Download nRF Logger from: play.google.com/store/apps/details?id=no.nordicsemi.android.log
2025-03-28A universal asynchronous receiver/transmitter (UART) is the most popular protocol used for talking to a computer device over serial port. What I am talking here is not exactly UART in traditional sense. It's an emulation of serial port over BLE. It's not part of profiles defined by Bluetooth SIG. It's a custom defined service. It's so popular that it has become a standard. It's an equivalent of SPP (Serial Port Profile) in Bluetooth Classic but community defined. Almost all (Nordic, Adafruit, mbed) BLE hardware providers support it. I think since Nordic started it. They defined the UUIDs and details of the service ➡️ Nordic UART Service (UUID: 0x0001). The UUID of the Nordic UART Service is 6E400001-B5A3-F393-E0A9-E50E24DCCA9E. As of now every vendor uses these UUIDs for UART. Nordic's UART Android client is a great application if you like to test your UART implementation. It's Open source and available on Play store.Below is the configuration of the Service and Characteristics that I used on a hardware device (Server or GATT Server) and then I used nRF UART 2.0 Android app (Client) to connect. The service definition below is for GATT Server. Characteristic names are from client's point of view. For testing purpose you could import this into nRF Connect and make it a GATT Server. Then you can use nRF UART 2.0 to connect and then to chat. One can implement custom protocol over that chat. Since the services above are implemented on the GATT Server. The TX Characteristic will have the WRITE permission enabled so a client can write where as a client can only READ from a RX Characteristic1. Essentially two characteristic work like register to which a client can write or read from. The picture below should make it clear. UART over BLEPS1:I am doing lot of experiments
2025-04-09I followed the instructions to install the nRF Connect SDK using the automatic method: worked and I was able to build sample applications and run them on the DK. Now I would also like the ability to build from the command line. The instructions say you need to start a new shell from the toolchain manager. This also works. However I cannot build from the shell if I start the shell without using the toolchain manager. How can I do that?It seems my build problems are fixed if I set the environment variable ZEPHYR_SDK_INSTALL_DIR. I noticed this variable is set when I start my shell from the Toolchain Manager but it is not set when I launch a shell normally. ZEPHYR_SDK_INSTALL_DIR=/opt/nordic/ncs/toolchains/v2.1.0/opt/zephyr-sdkSo.. If I start a regular shell (without using toolchain manager) and set this variable the builds are working. Is this a valid way to use the SDK? Let me add some background here. When I started using nRF Connect I chose the automatic installation method. This seems like the best choice to get started quickly. Then I enrolled in the nRF Connect SDK Fundamentals course. So far so good. But now I started using some of the sample projects and they all seem to use the command line to build & flash. This works fine if you open the terminal from the toolchain manager. What is not clear to me is how to switch between command line and VS Code on the same project. For example, some of the example projects use kconfig overlay files which are listed on the build commands. If I switch over to VS Code I guess I need to edit the application setup and add the kconfig file there? This behavior is new to me. I'm used to running 'make' from the command line with no options because all the details are stored in the makefiles. Then your IDE can just run the same make command. In short, I was hoping to learn how to use VS Code and the command line on the same project. In the short term I want to make this work for the sample projects but later I need to get the same behavior working with my own project. Hello,The thing that happens when you start the shell from toolchain manager is that it sets up the environmental variables for a given SDK version.You can add those variables by yourself if desired in your ~/.bashrc file for example.VS Code runs the same west commands under the hood as you would in the terminal. There should be no need to do things differently.When you build in VS Code you should be able to see the exact command used to build
2025-04-02NRF Util (nrfutil) functionality is provided through installable and upgradeable commands that are served on a central package registry on the Internet. nRF Util can be downloaded through the Download tab at the bottom of the page. To see the complete list of functionalities offered by nRF Util, type nrfutil help.The nRF Util supports several commands, including:nrfutil nrf5sdk-tools commandThe nRF Util nrf5sdk-tools command provides all functionality available in previous versions of nrfutil ( nRF5 SDK device firmware update (DFU) package generation. Cryptographic key generation, management, and storage. nRF5 SDK Bootloader settings generation. nRF5 SDK DFU procedure over the following transports: Bluetooth Low Energy. Serial over UART. Serial over USB. Thread unicast. Thread multicast. Zigbee. To install the nrf5sdk-tools command type: nrfutil install nrf5sdk-tools. To see the complete list of functionalities offered by this command, type nrfutil nrf5sdk-tools --helpnrfutil device commandThe nRF Util device command can list, program, recover, erase, and do various operations on Nordic devices. It supports MCUboot and J-Link. To install the device command type: nrfutil install device. To see the complete list of functionalities offered by this command, type nrfutil device --help.nrfutil completion commandThe nRF Utilcompletion command makes it easier for users to interact with nrfutil and find available commands, subcommands, and flags.It can be installed by typing nrfutil install completion, followed by nrfutil completion install bash | powershell | zsh, and the user is then provided the necessary steps to complete setup. Pressing Tab or Ctrl+space will invoke menus and auto-completion, including values such as serial
2025-03-30Experience the AI-Powered Modern Store at NRF 2025 at NRF 2025!Join us from January 12-14 in NYC at Booth 3303, where we unveil cutting-edge AI and machine learning solutions designed to revolutionize retail. Discover how our integrated hardware and software solutions transform workflows, enhance inventory management, connect frontline workers, and drive intelligent automation.Zebra’s integrated AI solutions are transforming the retail landscape across the entire retail value stream to Elevate the Customer Experience, Optimize Inventory and Engage Associates.Hear from our customers on how Zebra empowers the Modern Store in these Big Ideas Sessions:Rack Room Shoes: Walking the Talk With Effective Task Management. Monday, Jan 13, 1:30 PM – 2:00 PMExpo Level 3, Stage 3Exploring The Future of Retail with Generative AI – Presented by Target, Google Cloud & Qualcomm Technologies. Monday, Jan 13, 2:15 PM - 3:00 PMExpo Level 3, Stage 3Explore Our Latest Solutions on a Booth TourGenAI Frontline SolutionsTask Management and Employee CommunicationWorkforce ManagementNext-Gen Checkout SolutionsFrictionless Returns & Self-Service SolutionsTheft Detection & Shrink PreventionAI-powered Demand Forecasting and Lifecycle PricingBOPIS Order FulfillmentIntelligent Back of Store AutomationIn addition to the integrated AI solutions above, other solutions being highlighted in the Zebra booth include:Self-Service Kiosk Solutions Mobile Wallet and Payment Personal Shopping & Scan & Go SolutionsConnected Fitting Room SolutionsRetail Media Platforms Workforce ManagementSupply Chain Visibility Intelligent Back of Store AutomationTo register for the Big Ideas Sessions or to request a customer meeting and/or booth tour, fill out the form under "I'm interested in"
2025-03-27