RoboTxTest for Windows 7 and 8 (.1) (x86 and x64)

[vleeuwen]

ROBOTxTest for Windows 7 and 8 (.1) for x86 and x64 systems is available.
You will find it in the ROBO TX Key package in the \RoboTxTestx86x64 folder.

or as

Robo TX Test for MS-Windows 7,8 and 8.1, 32 and 64 bit - 0.25 MB

http://www.fischertechnik.de/en/Home/do ... uting.aspx

[ft-ninja]

Hello Carel,

In my case (windows 7 64 bit) the RoboTxTest.exe from RoboTxTestx86x64 archive is not working. After start it immediately crashes with following message:

Error:
"The library [ftMscLibEx] could not be initialized"

[vleeuwen]

Which download?

The one in the
"ROBO TX Key" package
or
"PC Robo TX Test für MS-Windows 7,8 und 8.1, 32 und 64 bit - 0,25 MB"

I will test them and see what is the problem.

[ft-ninja]

"PC Robo TX Test für MS-Windows 7,8 und 8.1, 32 und 64 bit - 0,25 MB"

[thomasdr]

Hallo.
I use the new version.
The ROBO TxTest x64 works.
The Firmware is V1.32, from the package.
The example upload is ok.

After start example the controller say
"Ch1,00:00:00...
BT Adresss is already used by another channel"

The tx is the only BT Device...

[vleeuwen]

As promised, I tried the download.
See this threat

I just downloaded "PC Robo TX Test für MS-Windows 7,8 und 8.1, 32 und 64 bit - 0,25 MB" from the fischertechnik web site.
My OS is MS-Windows 7 x64 Ultimate , I am logged on as administrator.

After unzip the "PC Robo TX Test für MS-Windows 7,8 und 8.1, 32 und 64 bit - 0,25 MB" into a folder (the \RoboTxTestx86x64)
you need to inspect the properties sheet of each file and see if it needs to be unblocked.

The files

• RoboTxtTest.exe
  RoboTxtTest.exe.config
  RoboTxtTest.vhost.exe
  RoboTxtTest.vhost.exe.config
  FtMScLibEx.dll
  FtMScLibEx.exp
  FtMScLibEx.lib

needs to be in the same folder.
Go to this folder with the Windows Explorer and start RoboTxtTest.exe.

The application starts with ftMScLibEx: version 01.05.14 (2014/05/16).
Open the connect to the right COM?? port (over Blue tooth). Test this connect with RoboPro in case of doubt.
Start the transfer area.
It is working fine with firmware V 1.30 on the TX-C.

@ft-ninja
I am not able to reproduce your problem.
There is also a RoboTxtTest.log.
Can you open it and see if the HomeFolder is pointing to the folder with all the files in it?
If this problem is still there, contact me by e-mail please.

[vleeuwen]

@thomasdr
Which package you are using?
Can you sent me more information about the steps that lead to your problem by e-mail.

Thanks in advance,

[vleeuwen]

I also downloaded the ROBO TX Key package and perform the same test.
See: http://forum.ftcommunity.de/viewtopic.p ... 441#p15430
No problem.
Upload of firmware 1.32: it tooks some time but the result was positive.

The other applications in the "ROBO TX Key package" are not recompiled with the FtMscLibEx.dll for Windows7 and 8 X86/x64 use.
May this can be the course of the problem

I uploaded the example.bin with the uploader of the RoboTxTest 2014.
After starting this program, I got the same error message on the display.
This also after closing the RoboTxTest 2014 application.

My question is:
Has this problem a relation with the RoboTxTest 2014 application or is it an internal TX-C (firmware related) problem?

[vleeuwen]

We are very interested in your experiences with the RoboTxTest 2014 for WIndows 7/8 x64.
Your feedback will be appreciated very much.

[vleeuwen]

Although RoboTxTest 2014 runs in test under Windows 7 sp1 x86 and x64 well, we received a message that this is not always the case.
See this threat
So I am very interested in the experiences of other MS-Windows 7 sp1 users with RoboTxTest 2014.
Could you start the application and connect to a TX-Co0ntroller?

[schnaggels]

Hi Carel,

just tried it under Win 8.1 x64 and it worked perfect. Didn't test BT but this will follow later.
I will try now Win 7 SP 1 x64...

Thomas

[vleeuwen]

Thanks Thomas and ft-ninja for the feedbacks.

[schnaggels]

Hi Carel,

also on Win 7 this package from the ft website worked fine (only USB tested so far)
Obviously I had the right preconditions already in place

If you need some additional specific details please ask...

Regards,
Thomas

[vleeuwen]

Thanks,
To discover the differences between a developer system and a end-user system can sometimes be difficult.
However we resolved the problem.
I performed all my test with Bluetooth connection even uploading a local application.

[thomasdr]

Hallo,
I have tried the packages of today (14.06.2014).
One controller with firmware version 1.30 ------> Controller hangs with example programm.
Two Controllers with firmware version 1.32 -------> Example Programm "Channel 1 00:00: ... BT Adress used by another channel"

Firmware and programm upload without problems.

Unfortunately still the same problem

Thomas

[vleeuwen]

Hi Thomas,

So far as I know:
After uploading the file which is containing the local program code, the TX-C, the RoboTxTest and the online API have finished their task.
Starting up the local program is under the responsibility of the firmware on the TX-C self.
You need to going the code of the example program and see what is happing and were.

RoboTxTest has no roll in the execution of the local program.
=====================================================================================
The only thing that can happen is that the content of the fill has been damaged during the upload.
However I assume that the program file works with a checksum an that the local program loader does check it.

@all,
Is there a problem with the example program?

[schnaggels]

@all,
Is there a problem with the example program?

About what example program do we speak in detail please? In my RoboTxText package was no extra test program...

Thomas

[vleeuwen]

@Thomas
The "example" program is a part of the "App´s (Android) ROBO TX Key" package and has nothing to do with the RoboTXTest itself.
The "example" program is a downloadable local TX-C program.

"thomasdr" mention this problem.


Suggestion to @thomasdr,
Create a different task for this "App´s (Android) ROBO TX Key"-package problem.

[thomasdr]

Hello, the app had a problem.
After performing the correction function in the app, the controller switched the channel.
Now works.
Thank you Thomas