I have 2 WIN10 computers - one has been in use for long time (update from WIN7) for many activities, and the other is bright new.
The old computer is not handling recieved data as the new one - there seems to be an extra 0x00 between all characters recieved on serial port. The new computer works.
I have testet the Serial comm with other tools (Hercules, VB, etc) and it works alike onthe 2 computers.
Can you hint me in the direction of the error, i think it's some setting in the Qt enviroment.
By the way, it's very hard to uninstall "ALL", as the setup seems to be "saved" across Uninstall (old version) and Install (New version) - is there a "cleanup" somewhere ?
Regards Joakim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
installation:
If you install SC on a computer which has already installed a SC instance then the old instance is uninstalled by the installer and the installation folder of the old SC instance is used. If you want to install the new SC instanc in a differnt folder then you have to uninstall the old instance manually (ScriptCommunicator folder in the start menu or execute unins000.exe in the ScriptCommunicator folder).
extra 0x00:
That sounds weird.
- Where do you see the extra 0x00? In the consoles? In the script? Or both?
- Do you use the prebuild version of ScriptCommunicator for windows (in this case all Qt libraries are included and you don't need to set up the Qt environment)? Or do you compile ScriptCommunicator by yourself?
- Do you use a Rs232 interface (standard COM port) or do you use an USB to serial device?
- which are your settings for the serial port?
- does only the version 5.03 has this problem (maybe you can test it with older versions of SC)?
Best regards,
Stefan
Last edit: Stefan Zieker 2017-08-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok about the installation, WIN10 do not allow installation in the default program directory (unless you run as administrator) - and this had that lead me to install 2'nd time on a new location - giving some problems (now cleared).
the extra 0x00: Found a Bug in the USB firmware for this specific device. Interesting is that the 0x00 seems to terminate strings, i thought that .js was working with a length field as part of the string "object".
KInd regards Joakim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I'm running Version 05.03
qt version 5.5.1
I have 2 WIN10 computers - one has been in use for long time (update from WIN7) for many activities, and the other is bright new.
The old computer is not handling recieved data as the new one - there seems to be an extra 0x00 between all characters recieved on serial port. The new computer works.
I have testet the Serial comm with other tools (Hercules, VB, etc) and it works alike onthe 2 computers.
Can you hint me in the direction of the error, i think it's some setting in the Qt enviroment.
By the way, it's very hard to uninstall "ALL", as the setup seems to be "saved" across Uninstall (old version) and Install (New version) - is there a "cleanup" somewhere ?
Regards Joakim
Hi Joakim,
installation:
If you install SC on a computer which has already installed a SC instance then the old instance is uninstalled by the installer and the installation folder of the old SC instance is used. If you want to install the new SC instanc in a differnt folder then you have to uninstall the old instance manually (ScriptCommunicator folder in the start menu or execute unins000.exe in the ScriptCommunicator folder).
extra 0x00:
That sounds weird.
- Where do you see the extra 0x00? In the consoles? In the script? Or both?
- Do you use the prebuild version of ScriptCommunicator for windows (in this case all Qt libraries are included and you don't need to set up the Qt environment)? Or do you compile ScriptCommunicator by yourself?
- Do you use a Rs232 interface (standard COM port) or do you use an USB to serial device?
- which are your settings for the serial port?
- does only the version 5.03 has this problem (maybe you can test it with older versions of SC)?
Best regards,
Stefan
Last edit: Stefan Zieker 2017-08-03
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hello Stefan.
Thank you for the reply.
Ok about the installation, WIN10 do not allow installation in the default program directory (unless you run as administrator) - and this had that lead me to install 2'nd time on a new location - giving some problems (now cleared).
the extra 0x00: Found a Bug in the USB firmware for this specific device. Interesting is that the 0x00 seems to terminate strings, i thought that .js was working with a length field as part of the string "object".
KInd regards Joakim
Hi Joakim,
extra 0x00:
I thought the same. Internally QtScript uses QString and this class shouldn't have problems with single 0x00.
Best regards,
Stefan
Last edit: Stefan Zieker 2017-08-05