- This topic is empty.
-
AuthorPosts
-
February 14, 2008 at 8:39 pm #934
Just don’t understand this one.
I’m not a pro at setting up serial connections but I can usually fumble around with them enough to get things working.
Trying this on a S10.
The serial device is weight scale and it is setup to comunicate with a type of windows setting which automatically sets up the coms to Com1, Baud 300, Parity None, Stop 1, Size 8, Flow None.
Scenario 1:
Wyse does not support 300 Baud but I want to try it any way.
So I set all of the following to these settings:
Com1 is device manager on the server,
In the control panel, Accessiblility Options,General tab, SerialKey Devices, Settings to Com1 and 300. Then checked Use Serial Keys
In Hyper Terminal for testing
In the wnos.ini file (which I will put in below)
Com1
Baud=300
Parity=None
Stop=1
Size=8
Flow=NoneWith the scale hooked to the server it’s self I get the data I’m looking for in Hyper Terminal and Excel the end goal. As soon as I disconnect and hook the scale into the S10 I get jiberish in HT and nothing in Excel.
So thinking that since Wyse doesn’t list 300 Baud as a trasfer rate that it can use, so I chaged everything above to 1200 Baud resulting in
Scenario 2This in fact has the exact same results as Baud 300. It works great in both HT and Excel when the scale is local to the server but when it is connected to the S10 I get jiberish in HT and nothing in Excel.
In both scenario’s I have used both a user with amin rights to the server and limited rights and the outcome is the same.
here is the wnos.ini I have to be missing something simple.
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator *
;* Copyright by Thomas Moellerbernd *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************Privilege=High
;*************************************************************
;* General 2 *
;*************************************************************Serial=COM1 Baud=1200 Parity=None Stop=1 Size=8 Flow=None
;*************************************************************
;* Display *
;*************************************************************Resolution=1024×768 Refresh=75
DeskColor=”128 128 128″;*************************************************************
;* Network *
;*************************************************************SignOn=No
;*************************************************************
;* General Session *
;*************************************************************SessionConfig=ALL UnmapSerials=no
;*************************************************************
;* RDP *
;*************************************************************;
;- RDP Session 1 –
;
CONNECT=RDP
Host=*
Description=”desktop”
Icon=desktop.ico
AutoConnect=yes
Reconnect=0
Fullscreen=yes
Experience=0
Resolution=1024×768
Username=*
Password-enc=*
Domainname=*
LocalCopy=noThanks,
Wade
February 14, 2008 at 11:10 pm #11713Hi Wade,
From memory you will have to map the COM port into the session, something like this:
– Create a connection on the S10 and make sure the COM port option is ticked under options.
– Log in to the Presentation (Zen App ❓ 😮 ) server and run the command NET USE COM1: \CLIENTCOM1:
– Test this at a common baud rate like 9600 first with hyper terminal
I have mapped scales this way before on Wyse 1125 and S10 devices and it all worked well,
Cheers,
-TTFebruary 14, 2008 at 11:21 pm #11715Does this apply to RDP also? I don’t have Citrix installed on this box.
Tried the command anyway and it says
“The local device name is already in use.”I just found out how to manally configure the scale and got it working with hyper terminal, but I’m still not getting any data when I open up Excel.
One step closer 🙂
February 14, 2008 at 11:27 pm #11718Ahh, you are on TS.
Yes its the same process but the syntax is a bit different:
net use COM1: \tsclientCOM1
Its been a while since I did this but Google the above command and you will find loads on the internet. You can do a straight net use to see if the COM ports are mapped in the session. I would not use excel as a test application as not all scales appear as HID devices so they will not function without the application. hyperterm will show there is some basic coms.
If the command works put it in the login script,
Cheers,
-TT -
AuthorPosts
- You must be logged in to reply to this topic.