Posts by Kaiser

Hello,

thanks for your answer.

Of course, I started conmanclient2 and notclientshutdown - sorry.

But now it seems to work for a while - I don't know why.

I also added

Reg set val CoreConOverrideSecurity dword 1

into registry - maybe this helped.

Or I had a open connection by US, but I think this wasn't the reason...

But after some further tests and changed IP address, there is again no connection any more.

Often, after once connected by USB, also the network connection works.

What I detected, after start of conmanclient2 a file is generated (514c36bf-c13e-4091-a3a7-1e566227b20d).

After change of IP address, I have to delete that file, to create a new one. And sometimes after restart, I get a connection.

Once connected, after restart of all (netdcu and VisualStudio), I always get a connection.

But first connection with new IP causes problems - seems that restarts after each cahnges help.

I also found out, the change in registry does not help. I have to start cmaccept anyway.

Hello,

I'm trying to connect and debug my NetDCUA9 board by TCP, but I get no connection -> "Fehler beim Verbinden. Das Gerät ist nicht bereit."

Im using the tools from NetDCU11/9 called:

clientshutdown

CMAccept

On netDCU11 it works fine.

But on NetDCUA9 I get no connection. Maybe there are other tools or other version for NetDCUA9 board?

Thanks, Andy

Hello,

when I execute that, I get following error message in a new window shown on display (WrongParameter.gif).

When I execute your code with parameter "-n" (only -n without redirection), executable is executed correctly with parameter, but output is shown as expected in new window (Output.gif).

Seems the problem is the redirection which also causes problems when I execute it directly in shell by telnet with output in files in other directories than root.

Hello again,

it seems I had the completely wrong way to do what I wanted. Now I solved it with a small code. Maybe it helps someone...

Hello,

this all wouldn't be neccessary, if I could access data directly from program into memory.

Unfortunately there are 2 problems I cannot solve.

I would like to start tool netstat in background by CreateProcess(), but always a white window is shown shortly on display.

But the biggest problem is, that I cannot write the standard output of "netstat -n" into memory and process the output.

I found examples to get output into memory by Pipes, but they are not available on WinEC7.

I also tried a short program in C#, but also there I cannot write to memory (the property RedirectStandardOutput is not known).

Also the CreateNoWindow property is not known. Seems that both are not available on WinEC7? I'm wondering, because they should be available in .NET Framework 3.5 ???

Has someone other ideas, how I could execute "netstat -n" and get output into memory for further operations?

The original purpose of all that, is to check a port (5900) to detect if a running VNC server has an opened connection.

Unfortunately the server itself has no interface to get information directly from it.

I also tried to open a connection by myself on port 5900, but neither bind() nor listen() delivered me an error. Only when I do that twice, I get an error after 2nd call. Why is it possible, to bind() and listen on port 5900, when it is already in use by VNC server?

According to my understanding it should not be possible and I should get an error, when I access it when already in use? A port should be only available once on one host?

Best regards, Andy

I thought, I have Win EC7?

In System Properties I can see:

Microsoft Windows Embedded Compact Version 7.00 (Build 2882)

After telnet login I see:

When I try your example, I get following results:

netstat -n >> "/ffsdisk/exampleOutput.txt" in executed in root directory:

-> Output is shown shorty on display and created file is empty.

netstat -n >> "/ffsdisk/exampleOutput.txt" executed in /ffsdisk directory:

-> Receive error message: "Cannot open \ffsdisk\ffsdisk\exampleOutput.txt as standard output."

netstat -n >> "./exampleOutput.txt" executed in /ffsdisk directory:

-> Output is shown shorty on display and created file is empty.

netstat -n >> "./exampleOutput.txt" executed in root directory:

-> Works.

netstat -n >> "/exampleOutput.txt" executed in root directory:

-> Works.

Seems that I have to use the copy command...

It works with a batch file, which changes dir to root, executes netstat and moves result file to ffsdisk directory.

Don't know the difference to your example. Are you on the same hardware? I'm connected to a NetDCUA9 board (Kernel V3.8) by telnet.

Hello,

oh thanks - that's working - but only for the root directory.

When I want it to write to FFSDISK dirctory, it is not working.

It's always written into the root directory, where some tool have no access.

I have tried "> /FFSDISK/x.txt" - there I get the error: "Cannot open \ffsdisk\ffsdisk\x.txt as standard output."

When I try "> /x.txt" in FFSDISK directory, it writes to root directory. It also don't work with backslash characters.

Are there maybe access problems?

Hello,

I want to get the output of "netstat -n" into file for later checks.

Neither a redirection by "netstat -n > output.txt" and "netstat -n 2> output.txt" nor a call of "CreateProcess()" in C++ program does it correctly.

The problem is, the tool netstat delivers its output always on display shortly and closes the output after finished.

Does anybody know a way, how to get the result into a textfile or memory in C++ program?

Would be great, if someone could help me.

Best ragards, Andy

Hello,

is there probably a problem with rs232 interface?

I have following situation:

I use serial connection (Modbus RTU server with 9600Baud) over rs232 interface to NetDCUA9.

* When I first switch on NetDCUA9 and then the Modbus RTU server, everything works fine.

* When the order is changed - I switch first on the Modbus RTU server and then the NetDCUA9, I can never establish a connection. Also after several starts of the software on NetDCUA9. Only when I stop and start the service on Modbus RTU server, a connection is established.

I can open the COM2: port and send data - seems to work, but no reaction on server - also I never receive something on NetDCUA9.

Reset of COM2 port after start and several reconnects didn't help on NetDCUA9 side.

The same problem I have with other hardware with Modbus RTU server (customer machine).

The problem is still there, when I remove serial cable and insert again.

Do you have any idea, what could cause this problems and how I could solve that?

By the way, I use the latest V3.8 kernel.

New info 30.08.2024

I have made some tests and find out an important detail.

After power on of the board, the serial interface sends automatically the value 0x00.

This causes the Modbus RTU server to block. No further requests will be answered. Only after restart of server, when no 0x00 received, server works as expected.

Is it somehow possible to avoid to send something on NetDCUA9 board at power on?

Thanks a lot.

Best regards, Andy

Ok - thanks a lot.

So I have to install it for a few customers to test.

If I get further information, I let you know.

[30.08.2024]

Problem is solved. Everything works fine now. Thanks a lot.

Best regards, Andy

Hello,

at the moment I'm using Kernel Version 2.9

I thought this is the latest one. But now I see, the latest is V3.8, so I will try this one.

Thanks a lot.

Best regards, Andy

Hello,

I have a problem that is being reported more and more frequently by customers. The display seems to freeze occasionally.

At least that's how it looks. At first I thought it was my program because it runs smoothly from start (autostart)

until suddenly not a single press on the touch panel is accepted. It looks like everything is frozen.

This sometimes happens during operation and sometimes immediately after starting the display. In this case the main program runs

normally up, but can no longer be used.

Yesterday, however, when I had to restart the display several times while testing, it happened to me while a program did not start automatically

the display also stopped responding. The operating system is booted, the display is blue with the taskbar at the bottom,

but nothing can be operated - touch doesn't respond. It also looks like everything is frozen.

However, I was able to log in via telnet and see that everything was working. Ethernet, CAN, RS232 etc.

I started the main program and everything was visible on the display, but it couldn't be operated. But it reacted to CAN, Ethernet and RS232.

Now I'm guessing it's a problem with the touch driver or something similar.

Unfortunately, the problem occurs very rarely and is very difficult to reproduce.

Touch is teached correctly by 5 points and works well usually.

I would be happy if you could help me with this in some way.

Extract from the registry:

Thank you.

Best regards, Andy

Hello,

today I found a new kernel for this hardware (XIPIMX6_C7E_V280_200424.bin) and installed it, but unfortunately no improvement on this point.

Now nearly 4 months passed since I reported this problem but nothing seems to be done. Are you really working on this or are you neglecting this problem?

Best regards, Andy

Hello,

I'm still waiting for good news on this point. Now 4 weeks passed...

Could you tell me more in the meanwhile? It begins to be critical with our customers. For workaround we had to use a hardware button where we can handle long pressed situations - but this is no final solution!

Best regards, Andy

Hello again,

just want to ask again if you were able to reproduce this problem?

You wanted to try it 2 months ago but unfortunately I didn't heard something from you.

In the meanwhile we have some problems with customers because we have to start machine by longer pressing on a button and sometimes it starts and sometimes not because focus is lost. Time is running away.

Please help to solve that problem or give feedback if it is at least reproducable.

Best regards, Andy

Hello,

yes thank you. This helped.

After searching the appropriate file for approx. 1h, I finally found the needed file.

The link of your referenced page unfortunately didn't work. So I had to search manually.

Just for interest, the needed file is called: "VS90SP1-KB2483802-x86.exe"

Now debugging works as expected.

Thanks a lot.

Best regards, Andy

Quote from fs-support_ZU

sorry i just debug on a NetDCUA9 using FSVYBRID_WEC7_SDK and MS Visual Studio 2008 but i cannot reproduce the problem.

Hello,

still have the problem. Either with FSVYBRID_WEC7_SDK or with FSIMX6_WEC7_SDK. Still the same wrong behaviour.

The only thing I do after creating a new project, is to add the 2 directories

into include path. Did I forgot something?

Could you maybe send me a small "Hello World" project, where I could test to debug? If it's not working with that, then there should be a problem with my configuration? But on the other side - debugging with a NetDCU11.2 board works without problems...

Thanks a lot in advance...

Andy

Hello,

just want to ask if you were able to reproduce this problem andy maybe could offer a solution?

This would be great.

Best regards, Andy

Hello,

I have attached a short video which illustrates the problem.

Usually the next window shuld be shown, when leaving the "Browse" button.

But as you can see, I'm still pressing and next window is shown after a random time while button is down.

No difference if finger or a pen.

Best regards, Andy