[Audesse Team]

in reply to: HSO and LSO Feedbacks #21497

Hi Tom,

It sounds like it isn’t behaving as expected and is likely a software configuration issue. Can you share your sample code for us to test on our end?

Audesse team.

[Audesse Team]

in reply to: HSO and LSO Feedbacks #21495

Hi Tom,

Can you take a look at the DO guide, especially the section on feedback and let me know what you’re seeing with respect to the expected values under certain conditions. It is difficult to tell if/what the issue is based on your current description. The chip may be functioning as designed. I’ve linked it below for your reference.

Digital IO Guide

Best,

Audesse team.

[Audesse Team]

in reply to: Flexcase and Rockchip for telematics #21450

Hi Sagar,

I wanted to follow up with some important context regarding those modules. It is important to note that while the mounting slots for the Rockchip and Whitebeet modules are indeed the same, the assembly and mating process is not something we generally permit users to do by hand. This level of integration is precision work that must be sent back to the factory to be completed via an RMA or a formal work order to ensure it is done correctly.

At this stage, it is likely that the board you were working on has been permanently damaged. Even if the module were to be assembled correctly now, the board would probably still fail to function and would likely cause immediate damage to the Whitebeet module itself. Our recommendation is as was previously mentioned, an RMA.

[Audesse Team]

in reply to: Flexcase and Rockchip for telematics #21441

Hi Sagar,

I am sorry to hear about the issues you are experiencing with your hardware integration. Based on your description, here is an initial assessment of the situation:

Technical Assessment:

The presence of smoke indicates that at least one component has suffered a catastrophic failure. Once a component reaches the point of emitting smoke, that specific part is dead and cannot be recovered.

The continuous power cycling of the FS chip suggests that the system is detecting a short circuit or a severe overcurrent condition. The chip is likely entering a protection loop to prevent further damage to the FlexCase-E mainboard.

This type of failure often stems from incorrect assembly or physical misalignment when mating the Rockchip module to the board. If the pins were damaged or bridged during insertion, it would cause the thermal runaway and electrical shorts you described.

Troubleshooting Steps:

To isolate the failure, please remove the Rockchip module entirely and power on the FlexCase-E board alone. If the FlexCase-E works correctly without the module, the issue is isolated to the Rockchip module itself, and the E-board should function properly for other tasks. However, if the FlexCase-E continues to cycle or fails to power, the mainboard may have sustained permanent damage.

Next Steps and RMA:

Since the hardware has sustained physical damage, these units likely cannot be used further. To begin the replacement process, you can find the RMA form on our website. Please complete the form and send it to our team via email to start the RMA process.

[Audesse Team]

in reply to: FlexCase-E (SSH Login / Hostname Issue) #21381

Hello Shweta,

Please see my answers below:

I tried connecting with the usb port as well but my pc is not detecting any connection (the usb I have is data cable) and the usb wifi interface is not visible in the ipconfigs and network connections as well.
-Our SSH guide (https://www.audesseinc.com/resources/sshconnection/) in combination with the datasheet for pinout should explain how to initiate an SSH connection to the device.

Also, if wifi is enabled by default then how can I connect to the wifi module ? we don’t know any credentials for connecting to wifi yet and when I power on the rockchip module the the rockchip wifi SSID should be visible but it is not visible in the network vicinity.
-Again, the SSH guide provides guidance on how to do this and includes the default credential details.

The SSH connection page talks about the wifi and usb options being available but exactly what steps need to be followed in order to get the rockchip module and my laptop on the same network is not mentioned.

Also, I have read about the involvement of Bonjour for scanning the network and finding the devices nearby,but I am not very sure about how can I use it to my benefit. Is it really necessary?
-We don’t typically use Bonjour for the FlexCase E, but you may find it helpful in your case.

If you are still having issues, you may want to consider an RMA (https://www.audesseinc.com/resources/forum/) as we can inspect the unit to ensure there is nothing wrong with it. Alternatively, you may purchase engineering support hours for someone to help you work through this issue.

Best,

Rhyse

[Audesse Team]

in reply to: FlexCase-E (SSH Login / Hostname Issue) #21369

Hello Shweta,

The Eth+ and Eth- are “MCU” Ethernet, not MPU Ethernet. You will not be able to connect to the MPU through that interface.

The FlexCase E typically uses the USB or Wifi interfaces to establish an SSH connection, as explained in the SSH guide.

Best,

Rhyse

[Audesse Team]

in reply to: FlexCase-E (SSH Login / Hostname Issue) #21342

Hello Shweta,

Thanks for the information and noted on you establishing ethernet connection. I’ll assume the ethernet connection is done correctly.

Our devices have been shipped with SSH enabled, one you are on the same network (wired/wireless) you should be able to SSH into the device using the same approach. https://www.audesseinc.com/resources/sshconnection/

For WiFi AP mode, I recommend you look up the resources for that particular module. The model number should be on the MPU itself. For our recommended approach, please read the guide in the link above.

SSH is the recommended approach for working with the MPU.If there is anything unclear about the guide link posted, please let me know as that should provide you with all the information you need.

Best,

Rhyse

[Audesse Team]

in reply to: FlexCase-S (Raspberry Pi OS Flashing + 32-bit / 64-bit) #21341

Hi Shweta,

We do not have a formal list of supported dongles. Your best bet would be to look up the supported chipsets based on the OS/Kernel present on the device. For the most likely success I would target an older chipset, which is popular. I’d probably target something USB2.0/fast Ethernet.

Best,

Rhyse

[Audesse Team]

in reply to: FlexCase-S (Raspberry Pi OS Flashing + 32-bit / 64-bit) #21183

Hi Shweta,

Thank you for providing those clarifications regarding the FlexCase-S platform’s flashing procedures and its current lifecycle status.

I recommend that you look at the Compute Module 3+ (CM3+) datasheet for details on the operational characteristics and expectations for the CM3+ within the unit. A good starting point might be examining the power consumption as a first clue to understanding its operational status.

Regarding device interfacing, SSH is the recommended way to interface with the module.

I believe you have an S32K1 chip, as we have never shipped the CM3+ variant with the K3 processor. The SSH access details, which are the recommended interface for that module, were included on the pamphlet provided when the device was shipped if the default passwords are not working.

If the passwords are not working, and you are unable to access the device via SSH, you will most likely need to reflash the operating system.

Rhyse

[Audesse Team]

in reply to: FlexCase-E (SSH Login / Hostname Issue) #21182

Hello Shweta,

Thank you for your follow-up questions.

FlexCase-E Data Workflow
• GPS/GNSS Data: Accessing the Quectel module and GPS data is handled (to begin with) through a modem manager script that is pre-included with the FlexCase-E device. This script allows you to manage the modem and access the GPS information as needed.
• Sending Telemetry Data to the Cloud: For the workflow on sending data to the cloud, please refer to our developer introductory page: https://www.audesseinc.com/resources/flexconnect-developer-intro/
We provide guidance on connecting to FlexConnect, as developers are permitted to use a number of different methods.

Regarding your question about the “expected bring-up flow” or sequence, could you please clarify what specifically you are looking for? If you have any additional questions after reviewing the developer introductory page, please feel free to reach out.

Rhyse

[Audesse Team]

in reply to: FlexCase-S (Raspberry Pi OS Flashing + 32-bit / 64-bit) #21169

Hi Shweta,

Thank you for reaching out with your questions regarding the FlexCase-S platform. I can certainly clarify the flashing procedures and the current status of OTA capabilities for this variant.

1. Raspberry Pi OS Flashing & Architecture

Regarding the flashing method via the micro-USB connection, this functions similarly to how standard development units work for the specific microprocessors used on the FlexCase-S.

However, please note that everything should already be pre-installed on the unit, so you generally should not need to change anything or choose between 32-bit/64-bit architectures manually.

Clarification needed: Could you let us know why you are looking to reflash the processor? Understanding your specific use case will help us determine if a manual reflash is actually necessary or if there is a different configuration solution.

2. OTA Capabilities & FlexCase-S Lifecycle

Regarding your second post about OTA updates, it is important to mention that the FlexCase-S is not recommended for new developments for FlexConnect.

The firmware on the S-variant is older.

It will not be receiving the same updates and support as the newer FlexCase-E and FlexCase-G models.

OTA Support Levels: The OTA support available is very similar to the tools and processes we provide for in-person flashing.

Supported: Application-level updates and configuration tools.

Not Supported: We generally do not provide firmware-level customization unless it is part of a larger enterprise deal.

Next Steps & Required Information

To help us guide you toward the right hardware and software strategy, could you please provide the following details?

Deployment Plan: What is your plan for deployment regarding the location, the total number of units, and your target time frame?

OTA Pipeline: Regarding the “Device → Telematics → Backend” workflow, could you clarify what specific parts are unclear based on the FlexConnect overview page (https://www.audesseinc.com/products/flexconnect/)? Knowing exactly what guidance you are missing will help us fill in the gaps.

Best regards,

Rhyse

[Audesse Team]

in reply to: Demo request for Flexcase – E telematics controls #21112

Hi Kantesh,

Assuming you have a unit with a modem, some example code is typically provided on the home folder of your MPU. We also have some resources in the guides section of the website (FlexConnect>Developer Intro).

We don’t yet have a public repo to update your code. I will reach out via email to check.

Rhyse

[Audesse Team]

in reply to: FCE2.0 Pins Short to Ground #20843

Hi Xuanlang,

Can you describe your problem more? Those voltage rails aren’t available thorough the header, which suggests that you have opened the case. If this is the scenario, you make have accidentally short circuited the board.

Was the unit working previously? When did you encounter this issue.

Best,

Rhyse

[Audesse Team]

in reply to: Unstable VHUI #19931

Hi craigbeal,

For VHUI, we haven’t seen many stability issues as you’ve described them. My go to recommendation would be some standard windows trial and error:
-Try a different PC
-Try a different network configuration

If you’re over Wifi, that could also cause issues depending on signal strength, so try a wired connection.

Let me know how those tests go.

Rhyse

[Audesse Team]

in reply to: Correct wiring for H-bridge configuration on FCG #19697

Thanks for confirming.

Best,

Rhyse

[Author]

Posts