Announcement

Collapse
No announcement yet.

Not Connecting HS3P -> GEM-3200

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • nfrobertson
    replied
    What version of the GEM-AUTOMATION chip do you have installed in your panel?

    Leave a comment:


  • rubbernecker
    replied
    Thanks for all the effort, Nathan, but I just can't seem to replicate your success.

    I uninstalled all of the drivers except the Aeon Z-Stick and rebooted countless times. Then I reinstalled with more countless reboots.

    There was a Prolific driver installed and nothing seemed to be using it. I removed it through the add/remove programs. When I reinstalled the drivers from the adapter installation programs, the Prolific driver did not reappear. I requested a downloadable factory reflash of my Hometroller harddrive to truly start all over.

    I also tried a Belkin USB-Serial Adapter.

    Here's what I have:
    Hometroller SE running Windows XPe
    Homeseer HS3 Pro 3.0.0.96

    Belkin F5U109 adapter - Driver: MCT Corp, 8/26/2002. 2.60.826.2
    Tripplite USA-19HS - Driver: KSPN, 9/20/2007, 3.7.0.2
    VSCOM mini - Driver: FTDI, 7/12/2013, 2.8.30.0

    All are set to 9600,8,none,1,none

    I don't have the serial tester, but I'll go ahead and order one if I can't find it locally.

    Leave a comment:


  • nfrobertson
    replied
    So I went ahead an purchased a Tripplite Keyspan 19HS USB/serial adapter which is the same one you started with. I was able to install the software that came with it making sure to skip the windows update driver check.






    I was then able to update my hspi_napco_gemini.ini and change to COM4. I then plugged in my panel via the normal GEM-RS232, fired up HS3 and it worked out of the box.



    I then swapped out the GEM-RS232 for PCI-MINI and that worked too



    Finally I connected a new RS2323 tester between the tripplite and the PCI-MINI and made a short video showing the changes in the CTS level that are necessary for the plugin to work with a panel that has GEM-AUTOMATION installed.

    http://www.kazteel.com/HomeSeer3/Nap...test_video.mp4

    The RS232 tester can be found on Amazon at the link below. I guess if you already have one or could purchase one you could see the state of the CTS signal which will likely confirm what the plugin sees and that is it doesn't change.

    http://amzn.com/B004OT995U

    Do you have any other ideas?

    Leave a comment:


  • nfrobertson
    replied
    What version of the Napco GEM-AUTOMATION EEPROM do you have?

    I need to confirm you actually do have the automation EEPROM installed as I believe Quickloader works with or without it but the HS3 plugin will not.

    Leave a comment:


  • nfrobertson
    replied
    Related to my testing with that new TrendNet USB/serial adapter ($9/amazon) I just noticed that my Current Cost ENVI was no longer working. Looking in windows device manager it indicated the port could not start. I looked at all my ports and found that the TrendNet also appears to use a Prolific driver and apparently windows had updated to the latest from 10/2013 when I installed the TrendNet adapter. That driver seems incompatible with the Current Cost ENVI (black plug, white cable) which is also an older Prolific.

    So, I went three rounds with windows and trying to downgrade back to the 2008 era driver that Current Cost provides. What worked was to run the driver install provided by Current Cost which first uninstalled the existing driver, reboot, re-run the install and when windows pops the balloon that it's installing device software click it, and tell it to skip the windows update check, and reboot. This seems to have left the correct older 2008 Prolific driver in place. I'm now back using my VS COM USB/serial as it's an FTDI chipset for the Napco panel and the 2008 Prolific so Current Cost ENVI is happy.

    My point in all this is that the driver used for a USB/serial adapter is critical to it functioning as desired with hardware.

    My VS COM is using a 7/12/2013 FTDI driver, screen shot in a previous post. What driver version does your VS COM show?

    Leave a comment:


  • nfrobertson
    replied
    When I swapped my VS COM for the TrendNet ($9/amazon) it recreated it as COM10. I had to edit my INI file in C:\Program Files (x86)\HomeSeer HS3\Config\hspi_napco_gemini.ini to get this to take. I'll have to look at the plugin to see why the config page didn't present cleanly after a COM port change. Anyway, yes, it works with COM10 so I do not expect any issues due to COM# or COM##

    I've been doing a lot of google searching trying to find anything to help with your situation. I've found examples where driver issues cause strange behavior, something that works with hyperterminal doesn't work with DotNet code but a windows reboot seemed to fix it LINK. I also came across the FTDI support page. In the section on CTS/RTS they mention some devices could invert the CTS signal. There are some interesting RS232 to USB articles that cover some of the challenges we might face with different chipsets and why the driver layer is so important.

    What this boils down to is the DotNet4 SerialPort class CtsHolding property isn't behaving as required. The plugin checks CTS to see if the panel is ready for the plugin to send data to it. If the CTS state never changes the plugin issues those timeout warnings that you are seeing.

    I'll see about working up a debug version with some switches we can add to the hspi_napco_gemini.ini to test inverting the CTS state or to ignore it initially and send the HAIL anyway to see if we can get this working.

    I understand your frustration as QuickLoader works but the DotNet4 SerialPort based plugin doesn't. I wish I had the HomeTroller hardware you have to test with. I'll post again when I have a debug version for you to test with.

    Nathan
    Last edited by nfrobertson; May 29, 2014, 01:57 PM. Reason: add article link

    Leave a comment:


  • rubbernecker
    replied
    I'm running the Hometroller with Windows XP. Out of the box, COM1-8 were being used by something. The Z-Stick took COM9 and the three USB-Seruial Adapters that I tried took COM10, COM11 and COM12. Does the script support high COM Port Numbers?

    Leave a comment:


  • rubbernecker
    replied
    Here is what is listed on the Plug-In Status page:

    **FATAL**: Failed getting InterfaceStatus from Napco Gemini - the interface was not found in the list of active interfaces.

    Leave a comment:


  • rubbernecker
    replied
    Plugged in the VSCOM adapter and updated the comm port. No luck. I shutdown HS3 and opened Quickloader. Changed the com port and it worked with the new adapter. shut down Quickloader and restarted HS3. Still no luck.

    Any ideas?

    I disabled and reenabled the plug in. Here is the log excerpt:


    May-27 3:04:00 PM HSTouch Server Debug 03:04:00:1562 ~ Updating device enumerator due to a device change.
    May-27 3:03:19 PM Plug-In Finished initializing plug-in Napco Gemini
    May-27 3:03:16 PM Info Plugin Napco Gemini with instance: has disconnected
    May-27 3:03:16 PM Error Initializing plug-in(1): Napco Gemini Instance::Unable to establish a good connection to the Napco Panel.
    May-27 3:03:10 PM Napco Gemini TIMEOUT waiting for panel to be ready for our command
    May-27 3:03:00 PM HSTouch Server Debug 03:03:00:1562 ~ Updating device enumerator due to a device change.
    May-27 3:03:00 PM Napco Gemini TIMEOUT waiting for panel to be ready for our command
    May-27 3:02:49 PM Napco Gemini TIMEOUT waiting for panel to be ready for our command
    May-27 3:02:39 PM Napco Gemini TIMEOUT waiting for panel to be ready for our command
    May-27 3:02:34 PM Napco Gemini hs.PluginLicenseMode = Registered. Thank you!
    May-27 3:02:34 PM Napco Gemini hs.InterfaceVersion = 4
    May-27 3:02:34 PM Napco Gemini hs.Version = 3.0.0.96
    May-27 3:02:34 PM Napco Gemini ---------------------------------------------------------------------
    May-27 3:02:34 PM Napco Gemini Starting Up... Napco Gemini plug-in version = 3.0.0.3
    May-27 3:02:34 PM Napco Gemini ---------------------------------------------------------------------
    May-27 3:02:33 PM Info Plugin Napco Gemini has connected. IP:127.0.0.1:2384

    Leave a comment:


  • nfrobertson
    replied
    I received the TrendNet USB to Serial today, plugged it in, change the COM port for the plugin and it worked as expected. Hopefully you have similar luck with the VS COM you purchased.

    Leave a comment:


  • rubbernecker
    replied
    Thanks... I purchased the VSCOM USB-COM Mini model 619 from Serial Stuff for $37.88 (includes shipping). I'll give it a shot when it arrives.

    Leave a comment:


  • nfrobertson
    replied
    There's also this TrendNET USB/serial for $9. I'm going to get one of these and try it. Claims it supports all the necessary signals.

    TRENDnet Converter

    Install as a standard Windows COM port, full RS-232 modem control signals, RS-232 data signals, TxD, RxD, RTS, CTS, DSR, DTR, DCD, RI, GND

    Leave a comment:


  • nfrobertson
    replied
    I can't tell the exact model of this VS COM adapter by the outside packaging. Purchased back in 2005 when I picked up my Napco system. However, I did a google search for VS COM and found what I believe it to be on their main website. The pictures match anyway: http://www.vscom.de/619.htm

    Then looked for US distributors and found they only list one and it's in Canada. They want $49 for a single one of these, ugh.
    http://www.electronicnetwork.ca/en/usb-com-mini.html


    Looking on amazon I can't find VS COM but I do see USB/serial adapters that look cosmetically identical like this USBGear adapter which has a FTDI chipset for $20.


    Looking on other sites like bestbuy.com I see a bunch of other adapters for $10-$20. I wish I knew if any of them were worth purchasing.

    Leave a comment:


  • rubbernecker
    replied
    I'll get a VSCOM adapter and give it a shot. They seem to have about 20 different models. Which model adapter do you have?

    Leave a comment:


  • nfrobertson
    replied
    I tested this today. I disconnected my GEM-RS232 from the panel and the USB/DB9 serial port converted. I replaced that with my PCI-MINI.

    Before: Panel -> GEM-RS232 -> USB/DB9 -> USB Hub -> PC/HS3
    After: Panel -> PCI-MINI -> USB/DB9 -> USB Hub -> PC/HS3

    After restarting HS3, I was able to successfully establish the same connectivity via PCI-MINI as with GEM-RS232. The key differences between your and my setup then is the USB to serial converter and the windows driver. You have a 3200 panel and I have a 9600 but I have heard back from others with the 3200 panel and theirs is working.

    It would appear that the CTS/RTS hardware handshaking isn't happening correctly with your setup. This plugin is VB.net 4. It relies on the VB SerialPort class and the underlying windows driver for the serial port hardware. SerialPort.CtsHolding is the property that tracks the state of the CTS line. There is a specific protocol flow that has to happen between the client (HS3 w/plugin) and the Napco Panel. The basic flow is the client checks CTS for true (is panel free), then writes a hail message to the panel, then watches CTS to change to false. It's that last step that the plugin is waiting for and never sees based on your debug log messages.

    I'm using a basic VSCOM USB to DB9 serial port adapter with an FTDI serial port driver that came with it. I've run this on my dev and prod machines with no special changes to the windows port settings. Images below show their settings.







    I've seen significant compatibility issues with other serial devices connected to windows with USB/Serial converters. Often the windows driver is critical to getting them to work correctly. I don't know if that's what you might be facing here? Do you have other USB/Serial converters you could try?

    Leave a comment:

Working...
X