OPT3101: OPT3101 Development (Invalid frame signature)

Hello Jonel, 

Can you share any system level calculations being done on the raw register reads? (I notice Tmain = -256 so I assume register read is 0 and system computes 0/8-256 = -256) It seems the distance reading would need to come from software somewhere as the direct computation from phase_out would be:

(phase_out/2^16)(c/(2 * F_mod))

Was device previously reporting differently or is this the only result you have seen from these registers?

Is this post calibration and in en_phase ebabled?

What operating mode is device in?

phase_out, amp_out, and Tmain all reset to 0. 

Any additional info would be helpful. 

Thank you, 

Joseph Scherphorn

Hello Joseph,

We've noticed that the device was previously reporting normally with detailed content (see the previous report below). However, approximately one hour later, it began returning invalid frame errors.

Below is the previous reporting.

Question : Is what happen to the device suddenly it gives an invalid frame

Hello Jonel, 

What calculations are being done to get distance and Tmain? 

I am asking because my guess is that the raw sensor output is all 0's for each register being read. This indicates that something is pulling down the bus. 

Can you read any other registers on OPT device and receive non-zero values while this is occurring? 

It is also possible that device is being reset somehow, if there is a large enough voltage sag on Vdd device could be power cycled and registers would read there reset values. 

thank you, 

Joseph Scherphorn

Hello Joseph,

I hope this message finds you well. We are currently working with uncalibrated data received through serial ports and need clarification on how to interpret it. Our development is based on the MSP MCU, which was recommended for use with the EVAL Board.

We've identified a discrepancy between the EVAL Board and our prototype: the EVAL Board features two ports, while our prototype has only one. We have already integrated the OPT3101 SDK into our project.

Could you please provide detailed step-by-step instructions for developing the OPT3101 from scratch? The EVAL Board comes pre-programmed, and despite copying its schematics exactly, we have been unable to replicate its functionality on our prototype.

Thank you for your assistance.

Best regards,

Eval board (OPT3101 EVM)

Prototype

Hi Jonel, 

In OPT3101EVM the MSP430 registers 2 USB COM ports with the PC it is plugged in to. The OPT3101 Control Port is used for sending control commands to the MSP430. This includes reading and writing registers on the OPT3101 and interfacing with the MSP430 flash storage. The OPT3101 Data Port is used only for streaming data from the EVM to the PC. This allows for maximum data rates when receiving real-time data from the OPT3101 during high-speed capture.

First try powering up eval board while all other devices are disconnected from usb. Section 6.1 of the EVM users guide walks through manual driver Installation which would be next trouble shooting step if I am only seeing one USB device 

Also wanted to make sure you are also aware of this tool in adition to SDK: OPT3101CONFIG-SW IDE, configuration, compiler or debugger | TI.com

Thank you, 

Joseph Scherphorn

Hello Joseph,

Good day, Thank you for sharing the guide. We would like to clarify that we have already implemented everything outlined there. Please also note that we do not have any issues with the EVM — it is functioning well and already pre‑programmed, so we don’t require the EVM guide. (Again We don't have any Problem on EVM )

What we are highlighting is the difference in our prototype ( Why we could not duplicate the response of the EVM ) : we have already completed the tools mentioned in the link you provided. That is why we are requesting a more value‑added response rather than just the link, as we may have overlooked something important.

We would greatly appreciate a meaningful answer that could help us move forward. Alternatively, we would prefer if the TI Team could arrange a meeting with us, since we are actively building something that may eventually require large order quantities if successful.

Thank you for your support and understanding.

Hello Jonel, 

All of our current resources for OPT3101 development are available on the product page. 

Please clarify: 

- Is only 1 USB Serial device being recognized with constructed board at all times or were 2 devices recognized when you were receiving expected values?

- MSP device used is MSP430?

I would advise scoping both sets of I2C com lines coming directly from the OPT3101 (sda_s & scl_s, sda_m & scl_m). As said early I believe something is pulling down this bus in one way or another.

Also can you please share how you have configured the 3101 I2C addresses.

Send me an email J-scherphorn@ti.com and I will share the MSP430 firmware used with OPT3101EVM

Thank you, 

Joseph Scherphorn

Hello Joseph,

Good day.

Please clarify: 

- Is only 1 USB Serial device being recognized with constructed board at all times or were 2 devices recognized when you were receiving expected values?

  Ans :  Yes , 1 USB Serial device being recognized with constructed board at all times.

- MSP device used is MSP430?

  Ans: MSP430F5503IRGZ ( We use the same as the EVAL Board )