更新客户需求
This has greatly impact on customer demand, below is customer requirement , please speed up and work out your updated plan.
------------------
询问替代料是否可用
For attached crystal(use I DCU and NCU), as the P/N for Asia and America is different ,please kindly advise if we can use the alternative ? thank you !
ES3448-01 ,we current use the component . Crystal - SMD 16MHz 10pf +/-10ppm 3.2x2.5mm - Detail Info. : 7M-16.000MEEQ-T ,TXC ,Location:Y1
Crystal- alternative ,please help to confirm if can use
---------------
we appreciate TI’s understanding of the urgency and importance of resolving this
我们感谢TI对解决这个问题的紧迫性和重要性的理解
--------------
Excuse me, In order to avoid align with connector pin ,we have put white oil on the PCB board , as shown below, can you please accept this change ？
---------------------------
Recently, we found the RF signal generator used for NCU tests is not very stable, it affects production efficiency, so can you provide 1 or 2 more to us for replacement? Or is
’t orderable in the market?
-----------------
Please push relative guys to sign IQC report to release those parts from Epictor system within today. Now system is shows in OPEN status.
请推动相关人员签署IQC报告，以便在今天将这些部件从表内系统中释放出来。现在系统显示为开放状态。
----------------
Attached please find the PSI report for the captioned order.
Please kindly check and advise your comments. Thanks!
--------------
The standby by current seems extremely high – can you check this? I was expecting <0.01mA Patrick/JP maybe you can advise?
Also, has this screw been included? Can’t see it in the photos
Done a quick test on an Acronym heater remote. We measured 50mA operating and between 4-20uA (0.02mA) for standby. Software revision 2.3
I remember there was not requirement to test the standby current
How has this value ended up in the PSI. Is the information in the PSI wrong? I do not want to me delaying this shipment however a stand by current of 26mA would be a major issue
The purpose of measuring the standby current is to check that the batteries will not run out quickly when the remote control is not in use.
Standby by current of 26.94mA would mean the batteries would run out very fast. On previous shipments of the black remote control, the standby current was measured at 0.01mA
which is normal
Can you advise how to test the sleep current?
I assume that we are using different method for the testing considering the huge difference
Can you provide the standby current specification/limit for all involved products which require sampling test? Because seems the standby current are not same for different
model. Thank you!
---询问进度----------------
It’s fine, I just want to remind to avoid the ball drops somehow. Thanks anyway!
I am sorry, we haven’t been in a position to give this task priority. I am not sure when we will be able to do this.
Would you please advise the status of the 920MHz version tools to read the actual SN of the device? We need such tool to improve testing process and avoiding mistake during
production, thank you!
-----描述测试过程----------
Your instruction below is very clear, we tried on few samples, standby current we measured are all below 20uA, test is simple, power on, the remote searching product(about
17mA), then wait about 1min, screen shows “No prod”，then screen off, the current drops to ~20uA. Is’t correct?
Sorry for that seems the inspection guy using the wrong method when sample check, screen is not off when he checking the standby current…
----休假-----
I'm out of the office and will be back to work until next Wednesday( July/25) , will reply your email as soon as possible after back. for urgent issues, pls call my mobile phone
----回复软件测试问题-------
Sorry for my delayed answer. The error codes are created by combining the codes below. I’ll update the “How to test” document accordigly in the next release.
SUCCESS = 0,
RTC_SELFTEST_FAILED = 1, // RTC failed, time reset to default (but would be corrected by healthCheck)
SYSTIME_SELFTEST_FAILED = 2, // sysTime not working... time probably won't run at all
CRYPTO_SELFTEST_FAILED = 4, // CryptoChip init failed
STORAGE_SELFTEST_FAILED = 8, // settings cleared
WIFI_SELFTEST_FAILED = 16, // Wifi init failed
BT_SELFTEST_FAILED = 32, // BT init failed
META_SELFTEST_FAILED = 64, // Device meta data unavailable (such as GDID)
RU_SELFTEST_FAILED = 128, // RU selfTest or config failed (FATAL error as SW version is unknown)
RU_NOT_COMPATIBLE = 256 // RU-variant not recognized as HPRU.
So for 100 you have 64 + 32 + 4, which means ECC508 module failed, Bluetooth init failed, and init of device persistent meta data failed.
For 101 the RTC self test also failed (this is not critical as it might happen when time hasn’t been properly set).
-----让客户确认-------------
It’s under processing now, meanwhile, would you please share us the customer’s confirmation about this change, it’s better keep that as supporting for future reference.
-----------------
A:
Looking at the attached pictures the QR code is very good. It is exactly what we want. But we have not received any parcel yet. Do you have a tracking number?
B:
We got the improved label from supplier, it looks better than previous ones we applied on EP4114 modules we sent to GD, attached please find the photos for your reference,
please let us know if you have further concerns, thank you!
A：
Sorry that we still not yet got the appropriate label from supplier at this moment , so we only apply the QR labels on the PCB like attached for your reference firstly, we will
correct it for asap, please advise your concerns, thank you!
B:
We would like to get 2-3 samples of the QR Code attached to the EP4114 Bluetooth module. It would be very useful for us to accelerate the Finished Goods Tester development.
Could you send 2-3 samples of QR Code attached to the EP4114?
If you don’t have any spare EP4114 modules, could you send just the QR Code? Or make a few photos of how the products should look like before the shipment (to see the QR Code
printed and attached)?
---------------------------
A：
Noted, and ,yes, the LED changes between green and red when press “Back” button.
Besides, we are developing tester for compact heater, will you have a final version software to us before production run?
B：
The reset of the device hasn’t been implemented yet.
During boot when all display LEDs are turned on the RGB LED should have all inputs activated, so it should be close to white. It might be green briefly *before* all display LEDs
are turned on.
After the device boot is finished, if you press the “Back” button (the left one with an arrow), does the LED change between green and red?
I would like to apologize that we made a mistake when soldering, the crystal was not soldered well… Now the sample works fine after re-soldering, the only thing is the RGB
LED looks like green instead of white during power up. Please check it at you side, is’t ok?
Besides, is’t possible to reset the device? Because the sample is now finally shows temperature somehow by touching the buttons.
B：
That is very strange. What happens when the buttons are released? Does the dashes ---- still show, or does something else happen?
If the dashes ares still there it is because at least one of the buttons are registered as “not released”. I am actually not sure how that could happen. If another screen is
shown, but not the SW version I am even more confused. Have you tested on more than one unit?
Regarding the “Er 2”, there is also a possibility that some of the components surrounding the Real-Time Clock is faulty or mounted with incorrect orientation. Pay espescially
attention to diode D40.
A：
Thanks for you quick reply! I will try the following.
Yes, when pressing and holding the buttons for a while, “- - - -“ is shown, but no software version is shown after release buttons.
B:
The Err2 means the device has not been able to retrieve system time from the onboard RealTimeClock. If you have started the device and set the time, and then turned it quickly
off again then the backup battery might not be properly charged. The next time you power-up again the time would be regarded as lost.
You may try one of the following:
1.Reprogram the device, then you should go straight to the screen showing 24Hr blinking without error.
2.After Er 2 has disappeared try saving the time (press the V button until the setpoint temperature is shown). If you leave the heater on for a while (for example an hour), then
turn it off, wait 5 seconds and turn on. Then the heater should boot without errors and go straight to showing the setpoint temperature again.
When pressing and holding the buttons for a while, is the “- - - -“ shown? If not the reason must be that the sensitivity of the buttons are slightly too low. This might be
because the PCBA isn’t properly fitted in the plastic housing, so there is too much gap between PCBA and the housing.
A:
We tried the functional test manually for compact heater, we are not sure it works fine due to below 2 steps fails according to you test spec, please help review and advise,
thank you!
Step 3.An error codes “Er 2” is shown, what’s the meaning of it?
Step 5.No software version is shown in the display after release buttons
B:
I hope all is well.
I have uploaded a folder to your FTP server now. The folder is called “TestSpecs_TestFW_2018-06-05”. It includes test requirements and test SW tools for Compact Heater, HPRU
and ECU-2Rw (wifi). You may use these to review the test requirements and might try to include the test tools in your own system. The SW tools are similar to what you received
for NCU2Te/ECU-2Te.
Please note that the SW included is *NOT* approved for production yet.
I hope you can help me in forwarding this information to your employees/co-workers.
-----------------------------
A：
Great! That’s should be ok, we will further check this when available, thank you
B：
OK, I’ll look into it.
I can add another parameter/argument -w which is taken to mean “do not wait for removal”. Would that be OK?
We tried, but it also requires “remove NCU-2R’ whatever we using “-o argument” or “-t argument”, “—serial argument”, we need to cancel the closed loop continuity
while we using Labview calling “Program_ncu_2r.exe”…
Anyway, for short term, we have to speed up the tester setup to catch up the schedule, so we will do programming and test by manual enter the serial numbers… but for long term,
we still need your help to improve continuity production.
Since the test process is different from the existing production of NCU-2R (868MHz version), it actually a more complex task for ATE than we preliminary estimated early… the
testing engineer still need few more days to complete software developing. Please update the schedule to customer when necessary, thank you!
Finally, the production is running smoothly with the new FW, no any issues so far…Many thanks for your efforts about this.
So, would you please send back the 2 PCBAs and 8 pcs MCU samples to us? We need return to production asap, thank you!
After evaluated with PIE and ATE, it saves about 10s per unit test after modified the tester, assumes the tester output is 120 pcs per hour currently, then after tester
modification, the tester output per hour to be raised about 50%. So it should be possible to stop the testing only on production line for 1~2days for ATE modifying the tester
and without any shipment delay, what do you think?
在用派和ATE进行评估后，在修改了测试器之后，它可以节省大约10 s的单元测试，假设测试人员的输出是每小时120个pc，然后在测试人员修改之后，每小时的测试人员输出大约是50%。因此，应该有可
能在生产线上停止测试1 2天，因为对测试人员进行了修改，没有任何延误，你怎么看？
Based on these samples that are specially modulated (frequency offset turned to around -75kHz), the power is slightly increase or reduces, which is uncontrollable. The control
power has been selected to be within max 10dBm (at 3V measurement), and the officially produced goods do not need to be a specially modulated. And the original module, we
checked the RF power also between 7~10dBm.
The rest of 3 samples range test, we hopes to be carried out today, because it depends on the weather, too hot or rainy days can’t be
do it. Please understand this situation. Thank you~
根据这些被特别调制的样品（频率偏移转到-75 kHz），功率略有增加或减少，这是无法控制的。控制电源被选择在最大10 dBm（3V测量）内，而官方生产的产品不需要经过特别调制。而原来的模块，我
们检查了射频功率也在7。10dBm之间。
其余的3个样本范围测试，我们希望今天能进行，因为这取决于天气，太热或多雨的日子是不可能的。请理解这种情况。谢谢你~
For the crystal mounting issue mentioned below, we would like to know what’s the reason that “NO solder on the crystal cover” while the soldering pads of the crystal on both
ECU-2RW and compact heat PCB were designed with a “body pad”, would you mind to advise?
对于下面提到的水晶安装问题，我们想知道“在晶振地上没有焊锡”的原因是什么，而在ECU-2RW和紧凑的热PCB上的水晶焊垫都是用“身体垫”设计的，你介意给我建议吗？
Can this question wait until Monday when Kjell Arne is back from vacation?
-----------------------
We normally do not share schematics, and actually I don’t have access to them myself (I primarily work with SW). For the tolerance I have to check with our HW engineers but
they are out of office returning Monday.
Would you mind share me the schematic both for HPRU and RU? We want to check the VCC difference between them, Barry found some HPRU boards(Rev.E PCB) failed the test by using
the existing RU tester due to the VCC of HPRU is a little bit higher(there is a VCC monitor built inside the RU tester), what’s the tolerance of the VCC output of HPRU and RU?
The unit we are using for test behaves as normal, but I’ll have to look into it more closely later. According to my colleague who made the changes to the new testSW for NCU-ER
says that the changes are related to handling of pot.meter settings. Since HPRU has no pot.meter it should be OK.
Ok, we will use the old test sw until new version available.
I think the HPRU is good because it works fine with both Ncu-2Rw and Ncu-ER(older test SW), is’t possible has a problem with the new test software? Berry used the newest
test-SW “NCUERRUtest_hex_flash.a90” you provided on 2018/7/12 for NCU-ER when testing HRPU, but it failed somehow, only D5 Green on, have you tried this at your side?
I did investigation on this, and I found that the internal pullup is enabled on the NTC ADC pin and affecting the ADC reading. That is why in reality it requires a lower
resistance to pass the test.
Thank you very much for finding this issue. Please continue the production with a lower resistance. I will check with product team if the software has to be updated.
---邮寄地址----
Please send the device to our Hong Kong office , attn. to our engineer . Thanks.
XXX
-----解释软件不良--------这里有些病句------
V02 was released by the customer in early July and used in the old 1X5 of ST1 480pcs and PCB. There was no motor test at that time and it was manually tested. There was no
problem of poor touch found in the test.
Customer after receiving the samples, this version layout design has a problem, so temporary add capacitance is put forward, and on July 25 updated Bom (Rev9) and Gerber version
(I), the customer issued on August 9th V0.3 version, for the ST2, ST2 in order to use the old material, chose the old idea of Bom and add capacitance, but using the test motor
test, only appear during PCBA assembly problem, not a software problem.
Instead of doing the EP first, the whole process was followed by ES doing ST four times, then adding EP (with the latest normal imposition) to the last ST.
-------回复问题进度------------
There is a solution to use this component in short term for urgent orders
I will get back to you soon about the solution
-----回复样品测试问题--------
Sorry that I was on leave and just back today and our team haven’t caught up to send you details on the test result. Our ENG & QA had field test the sample of AE02 #7 on our
factory site, and it achieved 100m this time, referring to attached video & pic. As we tested all the hardware that we can do it on hand (radiated functional test RX & TX, TX
data deviation test) and all are normal. We believe the previous failure is caused by RF interference jamming, and we would suggest Siemen also can have a one more trial on this
unit again.
