Hello,
on NetDCUA9 under WEC2013 all files for debugging included into the image. You have to start "conmanclient3" and "cmaccept3".
On NetDCUA9 under WEC7 you have to start "conmanclient2" (not "clientshutdown") and "cmaccept".
The files must be copied to the board (also TcpConnectionA.dll, eDbgTL.dll, clientshutdown.exe).
If it does still not work and you disabled explorer from autostart try to "start explorer" first.
Commands:
Ok, thanks for this information.
FYI:
we never had any issues while operation with this touch chip/touch driver. If so, I assume there must be big spikes on the power supply.
While power on we do HW reset the touch chip. While we do this the power supply must be stable.
Hello Martin,
as far as I see you already test: HKEY_LOCAL_MACHINE\Services\<Service Name>\Keep=DWORD:1. Does this not work? According the docs it should work! At least "services start FWS0:" should work (it may be case sensitive).
Think we can ignore Flags|=0x10, it only means the service it loaded into the user mode.
PS: concerning "autostart" I found following in the source code. This should work:
// Read registry setting for Autostart Firewall Service
// [HKEY_LOCAL_MACHINE\COMM\TCPIP\FIREWALL]
// "FWSAutoStart"=dword:0
// ; 0 - AutoStart Firewall Service Disabaled/ Default
// ; 1.- AutoStart Firewall Service Enabled at boot time..
Please check also your power supply.
The reason for this behavior may be spikes while power on or during operation!
Hello Dirk,
please try if the problem persist if you enable the additional SW Reset via Registry:
reg open \drivers\builtin\netdcua5\touch_tsc2004
reg set value SWReset dword 1
reg save
In the meanwhile I will check if we have some more options via Registry.
Hello, yes you are right, I edit my previous post yesterday; "[EDIT] ok think following is nonsense:("!
Hello thanks, for you detailed explanation and hint.
[EDIT] ok think following is nonsense:(
Anyway, a short comment to your "CreateProcess" above. Netstat is not a command it is an executeable, so maybe following works without showing console:
BOOL bResult = CreateProcess(T("netstat"), T("-n > NetScan.log"), ...
Right, this is WEC7. I had NetDCU11 in mind.
So you can install latest WEC2013 on a NetDCUA9 and check if it is really the OS.
I test with kernel WEC2013 for imx6 V3.4.
Thanks for this information.
Seems to be a "WCE6 bug". I test it under WEC2013 but I await same notation should work under WCE6 too!
Hello, please check the following (if any issues you may use finally the copy command):
Hello, test following on the cmd shell, it works : (I modify the "echo" sample from here Redirect )
Hello,
please check the firewall option, assume hints will be found here and on linked pages: Firewall Registry Settings.
Think we don't have any other chance to do this.
Hello,
you can disable the "Broadcast Driver" via Registry to prevent this: [HKLM\Drivers\Drivers\Builtin\BCSend\Flags=DWORD:4].
The boradcast is send so that a remote PC which runs FS Device Spy tool can detect devices.
You can also short time and number of broadcasts send by Registry, for more details refer FSIMX6 Device Driver chapter 19.
From your previous answers:
>> All devices arer configured the same way at production
>> AutoDST is set to '1'
I can't believe this. If this is right you should have problems world wide. For example DST date in europe and US are different also some states does not have DST at all! But all devices are in the same time zone. So for me it is obvoius you do anything in Registry or code.
>> but I do not have access to these devices in Japan :-(.
<< Is it possibel to reproduce the issue in your office? What happens when you do several transitions from "Nov 2nd or 3rd Nov" to later date? While power and power off.
Hello, why you do not contact Plexlog? They should know what is to do.
The four devices which swiched on 3. November are in "Pacific Standard Time" (see HKLM/Timezones/)?
The time zone of the other is different from this value? I just read the "Japan Standard Time" has no DST since 1951.
>> the units are not connected to a network since they are running in a hospital due to security reasons.
<< Ok, so we can exclude the time server. But can we be really sure that nobody can plug in the Networkcable? Not even a service technician?
And what is about "HKEY_LOCAL_MACHINE\Software\Microsoft\Clock\AutoDST". Can you still check this value on the devices which switched DST?
Hello,
are all units connected to the Network?
Assume you set "HKEY_LOCAL_MACHINE\Software\Microsoft\Clock\AutoDST" to zero for all devices?
I am not sure what happens if you are connected to a Network and time server is active. It should recognize the "AutoDST" flag, but I am not sure if it is so!
Please check following if time server is runnuing , set Flags to 0x04 (or at least add |= 0x04) and test the behavior of the device in a Network:
PS: assume on NetDCU11/WCE6 servcer list is a bit different. DST server should not appear.
Hello,
thereby the steps for remote debugging a WPF application in Visual Studio 2022 (Version 17.11.4) on Windows 1x IoT Enterprise LTSC device. In the attachments you will find my used Visual Studio configuration. There is also a description from microsoft which will be found here: remote debugging. In the following we will repeat this and give you some addtional hints.
1. Create a WPF project named MyWPF
2. Set a breakpoint somewhere in the code that is easily reached.
3. In Solution Explorer, right-click the project and choose Properties. For C# projects targeting use .NET 6, add and select ARM64 using Configuration Manager.
4. Choose Debug tap or click the link for open "Startprofile".
Enter the system name of the device and the port number as shown below, the port number is fix for VS2022.
You can retrieve the system name by open the System Information on the device or by using FS Device Spy which will be found in our Windows-Tool download.
5. Make sure the Working directory text box is empty
6. Choose Use remote machine, and enter the string as said in 4.
7. Make sure that Enable native code debugging is not selected
8. Built the project
9. and 10. Copy the complete project to the device the path should be exactly the same as on your development computer. Share the folder on the device, so that you can access it from you development compute with write permissons.
Afterwards you can configure Visual Studio the copy the new files after each built.
11. Launch the remote debugger on the device. You will found the installation file for VS2022 at microsoft or in our Windows-Tool download (VS2022_RemoteTools_ARM64).
12. In Visual Studio start debugging
13. If prompted, enter network credentials, default user is FuS with empty password.
If any questions please come back here.
Hello,
I measure on TX pin - neither bootloaders nor kernel send anything while power on! TX ping goes from 0V to high to low, does the modbus server interpret this as "start-data-stop"? Is there an option to prevent this behaviour on server side?
