Serial communication: Hyperterminal OK, hs.sendtocomport fails - Solved!

[Moskus]

While I'm waiting for my cables needed to use the plugin for my Monoprice HDMI switch, I thought I would use hs.comportsend to operate the switch.

It works great using hyperterminal. If I send "A2" I set the output A to port 2. If I send "on" I turn the unit on, "off" turns the unit off, and so on.

I thought it was just a matter of opening the com port (14 in this instance) and do:

hs.OpenComPort(14,"9600,n,8,1",1,"","")
hs.sendtocomport(14, "A1" & vbCrLf)
hs.CloseComPort(14)

While this works great in hyperterminal, I don't have the same luck using scripts. I'm sure there is something I don't know about serial communication, but what is it?

Thanks!

[Pete]

Much of the older scripted to serial HS software opened the serial port when booting HS and closed it when shutting it down. SnelvCID does this today with the netcid box.

That said though it should really function the same once that HS is running.

Give it a try anyways; put an open com port statement in your startup text and and close statement in your shutdown text.

' Steves CID

hs.runex "SnevlCallerID_funcs.vben","open_port",""

' Steves CID
hs.runex "SnevlCallerID_funcs.vben","close_port",""

[Moskus]

What you really are saying is that I need a delay between opening the comport and sending data?

[Uncle Michael]

I don't think a delay is either necessary nor likely to fix the problem. I've used both methods and they both seem to work the same.

FWIW, I had a similar case a few weeks ago. I tried all sorts of stuff, but the thing that finally worked was moving to a different computer port. I have no idea what the original problem was. What was even more puzzling is that the original port worked fine for weeks, then transmission suddenly stopped. As soon as I changed ports everything started working again, and has worked flawlessly since. At least it's worth a try.

[Pete]

Here my 16 plus serial port connections (maybe 20 something today) / configurations haven't really changed in years.

They are all using the same device controller; IE: Digi Edgeports and 1 Digi USB hub (to a few USB to serial) and two Quatech boxes.

That said I have never really lost com with any of them except for the Z-Troller.

The Z-troller is on one com port of maybe 3 utilized on the HS Standard box test box.

The "test" though was disabling the Z-Troller plugin, disconnecting the com port, reconnecting the com port and re-enabling the Z-Troller plugin.

The most current beta boot up and shut down of Homeseer is probably the quickest that I have seen in many years of beta testing.

Most interesting "phenomenon" cropped up relating to serial port communications and specficially with HSPhone/NetCID/W2C box. Recieved 4 calls this morning after shutting down HSTouch (disabling the plugin). I did not hear any TTS relating the four calls since shutting down HSTouch. I decided to call myself to test the TTS and then ended up hearing the TTS for the four previously incoming phone calls. That and I did not see the CID's come up on HS until I made the last call to myself.

[Moskus]

Hmmm! Now even Hyperterminal won't play nice:

[AshaiRey]

In the root of the HS folder there are two file with an example how to do it. They are called comm_open1.ttxt and com_event.txt
Have a look at those two, maybe it will help. Not sure of it will.

[Pete]

Attached are a couple of freeware serial port diagnostic tools that will help some.

[Moskus]

"Telko A/S"? Really? Go Norwegians!


But no explanation on the weird characters in Hyperterminal (or anything else)?

[Pete]

I would guess that the HDMI switcher com port settings on the HDMI switch may have gotten trashed (reboot HDMI switch) and / or Hyperterminal comm port settings got trashed (which can happen and I have seen that).

In a synopsis; shut down and unplug the HDMI switch box and the testing box and start again. You might also be talking to another serial port (not the HDMI one).

[Moskus]

Thank you all for your input and suggestion. However, once again it doesn't work because I'm an idiot.

It turns out that this switch doesn't use the same protocol for communication as the other HDMI switches. This uses plain ASCII commands and responses.

And the speed NEEDS to be set to 4800. Once I figured that out, it was plain sailing...

[Pete]

Good News!

Yup:

It works great using hyperterminal

Thought you had the baud set right originally. Here I still utilized a GPS for time sync. The newer one has an adjustable baud rate which I really have never seen before.

[Moskus]

A GPS for time sync! Hmmm, now there's an idea.
(Don't you trust internet time?)

The HDMI matrix is awesome!
I feel like people are used to technology being smart, but why this isn't more common I have no idea.

[Pete]

(Don't you trust internet time?)

no

$GPGLL,4134.4418,N,08800.6301,W,202206.477,A*29
$GPGGA,202206.48,4134.4418,N,08800.6301,W,1,09,0.9,00223,M,, ,,*37
$GPRMC,202206.48,A,4134.4418,N,08800.6301,W,00.0,000.0,21041 3,02.,W*68
$GPGSA,A,3,16,32,31,20,29,06,13,03,23,,,,1.8,0.9,1.5*3D
$GPGSV,3,1,11,16,80,164,41,23,60,307,42,13,33,312,46,20,33,2 35,40*75
$GPGSV,3,2,11,31,28,073,46,32,28,202,42,06,27,143,46,03,21,1 62,44*79
$GPGSV,3,3,11,29,08,036,46,07,02,270,,10,02,330,,,,,*4E

[Bill Brower]

A GPS for time sync! Hmmm, now there's an idea.
(Don't you trust internet time?)

You have to trust the internet, everything on the internet is true, I know because I read that on the internet once.