Jump to content

EZIO8SA no longer recognized?


smorgasbord

Recommended Posts

Posted

Thanks Brian,

 That confirms it is not reporting as an EZIO8SA.

My notes show it should report as "07 04"  and that is what I see with mine.

My notes also indicated that when I later factory reset the EZICOMM(PLM)  it then reported as "03 2A"

Also note that the message link response was NAK ed.  " 15" .

Posted (edited)

07 04 is the EZIO8SA. I can't find 03 2A in the list from Smarthome in the Developers Group. 03 is the category for a PLM and I think subcategory 2A may have been one given to Smartenit (Simplehomenet) for their EZICOMM and not in my standard list or the list is too old. Thank you for providing the 03 2A ID you found in yours.

When first booted up. The EZIO8SA should send and receive a few messages to the connected PLM or EZICOMM. To change its ID  to 07 04 so the controller knows it is an EZIO8SA and not a PLM/EZICOMM.

Since the user has said they have a wall wart power supply. I am not 100% sure if you factory reset the EZICOMM.  If it resets the EZIO8SA if not powered down by unplugging the wall wart.

Edited by Brian H
Add some information
Posted (edited)

I don't have a cable to connect my EZICOMM to a serial port. How to I buy/make one?

I reset my EZICOMM by unplugging, waiting 10+ seconds, holding down the SET button while plugging it in and holding until it beeps.

I tried both startup sequences in terms of applying power - no change in outcome. Even when I specify the type it changes almost right away to Unsupported.

 

IMG_0898.thumb.jpg.9e20041fa2157db73648b79aaee85b00.jpg

Thanks for all your help and suggestions, btw.

Edited by smorgasbord
Posted (edited)

We may have confused you. Talking a PLM. There should be two. One for the ISY994i and the second one in your case a EZICOMM connecting to the EZIO8SA. There is no connection from the EZIO8SA and the ISY994i systems PLM. The EZICOMM is a Smarthome base PLM with the Simplehomenet/Smartenit  custom RS232 serial board that can have RS485 on it also as an option..

The EZIO8SA should have a network type cable between its "PLM" jack and in your case the EZICOMM. The ISY994i has its own PLM to operate.

The EZIO8SA should send a few software commands to its connected EZICOMM(PLM) to change its ID to 07 04 so your system finds it as a EZIO8SA and not a 03 2A PLM.

I would factory reset the EZICOMM  with the EZIO8SA not powered up. Then power up the EZICOMM and let it initialize. Then power up the EZIO8SA and it should as part of startup. Send a few software commands to the EZICOMM so it identifies as a EZIO8SA 07 04 and not the native 03 2A.

If it still is found as a 03 2A we have to do more thinking.

Edited by Brian H
Add information
Posted (edited)

I did a test.
With an early version EZIO8SA, powered by a 12V wall wart, 2413S V1.0 PLM.
Network style cable between the 2413S and EZIO8SA.
Powered the PLM connected to the  EZIO8SA first. Then turned on the EZIO8SA.
The EZIO8SA sent some data to the PLM and its set led flashed a few times.
Added it to my ISY994i. Auto found it as a 07 04 EZIO8SA.
To get how the outputs working.
Their was an Options Screen.
Change On Level On to 100% and Ramp Rate to 0.1 seconds
Outputs changed on the screen as expected. I did not use a meter to check on the EZIO8SA.

I am not too sure if I had to set the options but I believe I did.

On the EZIO8SA I did have the AN1 and AN2 inputs grounded. Was recommended in their now gone Silmplehomenet forums. If you are not using them. They are high impedance and will pick up stray noise sometimes. With the AN1 and AN2 inputs randomly changing level.

Edited by Brian H
Add data
Posted (edited)

Smorgasbord,

I spent a little time refreshing my memory by retesting as it has been a long time since using a terminal program with EZIO8SA8.

I am attaching a pictorial of the serial cable needed ( Brian provided pinouts earlier).    If you every bought a 2413 PLM by itself you should have received one of these cables with the PLM in its box.

image.png.0e6d1fe1b50d3fe08da210ebc5c02200.png

First Connect the EZICOMM to the terminal program and see if you can communicate with it .  ( this is to assure you have the terminal program setup correctly). Brian supplied the terminal program parameters ( baud etc) earlier.

If you send an "02 60"  you should get a response as shown:

image.thumb.png.21dd96823518cff44cc8450223443ffe.png

If you have that working then you will need to swap pins 2 and 3 ( Rx and Tx) at the DB9 connector to be able to talk direct to the EZIO8SA module at its J2 connector.   As soon as you power up the EZIO8SA you should see it sending the message as shown.   That is  the EZIO8SA trying to change the EZICOMM's  Category and sub -category values to "07 04".  Since there is no EZICOMM connected in this scenario it sends it over, and over and over again.

If you do not get this then the EZIO8SA module is likely not working correctly.

 

image.thumb.png.055b7342a61f14056e402becfca1b6d5.png

 

The EZICOMM(PLM) does not store any updated Category and sub-Category value upon power down.  So the EZIO8SA needs to provide that updated  Category and sub-Category each time the pair are powered up together.

Hope this helps and good luck.

 If there is an extra duplicate  screen shot at end ignore it.  I could not remove it for some reason.

 

 

 

 

Edited by ELA
Posted

The "PLM.ptp" program for DockLight Scripting Evaluation program should have all the setting in it already. Except maybe the COM port if not 1. In that case you pick Tools, Project Settings and change the COM port number. It may ask to save changes but it will not as the evaluation version has a few features disabled like save and print.

Posted (edited)

The photo you posted yesterday. Is the back of the EZICOMM used for the EZIO8SA correct?

The FCC tested label on the back, the two prong AC Pins, factory reset beeps and address showing in your  EZIO8SAAdd.txt match the photo's label. Would indicate you have one built on the 2413 base PLM assembly. So it is subject to the same power supply capacitors issues many of us have fought with for years.

The cable in the box will allow you to test the EZICOMM with DockLight Scripting. The EZIO8SA would need the cable modified. Because the send and receive signals are reversed between the EZIO8SA and EZICOMM. Smartenit still has some of the cables on their sales site.  https://smartenit.com/shop/plm-serial-cable/

I had a chance to look at the information the EZIO8SA sends to its PLM/EZICOMM. It sets the ID to 07 40, another command turns off the Set LED on the interface, then turns it back on and resets the configuration to disable the Set Button from doing local linking. So when you power it up part of the startup should flash the EZICOMM LED from on to off and back on.

Edited by Brian H
Add information
Posted (edited)

Ugh, so I looked everywhere and I don't have the RJ-45 to RS-232 cable. Do I need to make one up from parts, or can I buy one somewhere?

Edited by smorgasbord
Posted

Would be easier to purchase one from Smartenit.

If you assemble it then you could probably easily reverse the RS232 #2 and #3 to look at the signals out of the EZIO8SA side of the equation.

To just see if they are talking to each other. The LED on the side of the EZICOMM  should flash a few times at power up as it reprograms it to ID as a EZIO8SA and not the native EZICOMM ID.

 

Posted

OK, just to update - I got my cable and now need to hook things up and run some software. I'm going out of town later tonight, so won't be able to pick this up again until Mon/Tues next week. Thanks for all you'alls help here.

 

  • 4 weeks later...
Posted

Sorry guys, but I'm having newbie problems. I got the cable from Smartenit connect it to my EZICOMM (which has just been reset) and to my laptop and I see that it's using COM5.

I then try Hyperterminal, configured thusly:

image.thumb.png.29378b02e97c320ea5a4dcf3b34a8a6b.png

But nothing works. When I type characters I get these weird symbol characters:

image.png.16ed19d0b8002f643fcebf44ee6b7db9.png

 What am I doing wrong? Should I use something other than HyperTerminal? I'm on Windows 10 but also have a Mac.

 

Posted (edited)

OK, got DockScript and the PLM.ptp file and did some of the preliminary commands:

image.thumb.png.8051e53b4ccf17f862307d66322295fe.png

 

What's my next debugging step here?

TIA

Edited by smorgasbord
Added success info
Posted

I also connected the SHN utility and tried connecting through that:

image.thumb.png.92917ae6cdc4b15613faf068ea25f2be.png

But, I don't have any instructions or idea of what I'm doing.

Note that when the PLM is connected to the laptop, the EZIO8SA box itself is not connected to anything, since there's only one RJ-45 out of the PLM. So, I'm a bit confused as to what I should be doing.

Sorry for all the newbie questions. I actually am reasonably technical, but not at this kind of low-level stuff.

 

 

 

Posted (edited)

The Smartenit program uses its own connected interface.  PLM both 2412S and 2413S. May also use a 2412U or 2413U that I never tried. The older 2414S PLC or maybe the 2414U USB PLC. The PLC also needs the SDM3-308 Smarthome Device Manager. SDM3-308 was in the utilities download package. Maybe too old for Windows 10. Their EZServe or EZICOMM.

With the EZIO8SA it still needs its own PLM or EZICOMM and the program needs it own interface. So you need a interface separately for the program to access the EZIO8SA. Your utility display shows not connected so you can't do anything with the EZIO8SA. I believe since it has no interface connected to the EZIO8SA and the interface is being used by the Utility.

Your PLM.ptp display.  02 60 Get IM Info. 1E 7F 33  6 digit Insteon ID. Category 03 PLM. Subcategory 2A (I think id is a Smartenit id). 9B firmware version. 06 ACK command processed correctly.

You may want to run the PLM.ptp on the EZCOMM after you have it initialized by the EZIO8SA and not reset. The 02 60 Get IM Info results should now show the category and subcategory for the EZIO8SA and not the PLM data.

Edited by Brian H
Add information and remove old data.
Posted (edited)

I checked my notes and Developers Guide. I have a correction.

With the EZCOMM programed by the EZIO8SA. The 02 60 command will still return the 03 2A with the 02 60 command but to the outside world. Like the ISY994i it should report it is a 07 04. If programmed by the EZIO8SA the command 02 73 should report a 80 if it was programmed by the EZIO8SA.

On mine at power up of the EZIO8SA. It sets the Host Category to 07 04. Turns off the Automatic LED control and Local Set button linking, turns the Set LED off, turns the Set LED on, turns back on the Automatic LED control and leaves the Local set button linking off.

When turned on. The LED on the side of the EZCOMM should flash off and back on if the EZIO8SA is programming it. Another clue would be a programmed EZCOMM reporting a 80 with the 02 73 command if it was programmed or a 00 if not.

In your Hyperterminal showing @@@@@. The PLM uses HEX for messaging. If you are sending ASCII that maybe the reason. The preset DockLight ptp file is set to send HEX.

Edited by Brian H
Add something
Posted

Thanks @Brian H, but if you don't mind, can we get specific on the steps I need to take? I think they are, in order:

  1. Connect PLM to EZ8IO with ethernet cable
  2. Plug PLM into power
  3. Plug EZ8IO wall wart into power
  4. ???

I'm not sure what I'm debugging here. My problem is that my ISY isn't recognizing the EZ8IOSA device properly. It comes in as "unsupported device." Do I reset the EZIOCOMM while it's connected? How am I using the connection cable from the EZIOCOMM to the PC if that means the EZ8IOSA can't also be connected at the same time?

Sorry again, I'm very confused at this point.

 

Posted (edited)

Step 4. The LED on the side of the EZICOMM should flash a few times if it is communicating with the EZIO8SA and setting the EZICOMM.

The network style connector on the ISY994i,EZICOMM and EZIO8SA all are serial signals not the normally used network signals. You normally find on a RJ45 jack.

When you have the EZICOMM connected to the PC with DockLight. You can use the PLM.ptp file to see if the EZICOMM will respond properly.

The EZIO8SA uses a PLM or EZICOMM. To be used in the system. The Smartenit program needs it own interface to run. So you need a PLM or EZICOMM on the EZIO8SA and another one on the PC. So you need two PLM units. One for the PC and another for the EZIO8SA. With no PLM on the EZIO8SA but on the PC so the utility runs. It can open the program but will not connect with an EZIO8SA with no attached PLM or EZICOMM.

Does the LED on the EZICOMM flash when you start up the connected EZIO8SA flash a few times? That should show if the two units are communicating and should be setting the EZICOMM to report it is a 07 04 module and not the default 03 2A.

Are you still getting the messages you posted in a previous log file. Where it tried to add the module and got many communications listed. Normally I would expect the unsupported device would show up quickly if the device was not in the ISY list of known devices. Not the whole sequence of commands before calling the unsupported device.

Have you tried connecting the EZIO8SA to the EZICOMM and letting it initialize?  Then connecting the EZICOMM to the PC and seeing what the 02 73 command reports? With out resetting it first.

Edited by Brian H
Change data
Posted (edited)

Maybe a recap would help.

In your log file posted in the early messages. It showed the EZIO8SA with EZICOMM. Reporting it was a category 03 subcategory 2A. That is a PLM from Smartenit as the 2A is not one used by Smarthome and probably given to Smartenit as a third party device. I would have expected the 03 2A would have been caught earlier before the Administrative Console tried to add it and not program all the relay and input links in the module before giving the unsupported device message.  It should have been 07 04 if reprogrammed.

The flashing of the EZICOMM Set LED may give a clue to the programming data being sent and properly received by the EZICOMM from the EZIO8SA.

Our tests where trying to see if the EZICOMM was being set to 07 04 and not the default 03 2A. Though not 100% conclusive. As you have found out.

Edited by Brian H
Correct message and add something.
Posted (edited)

OK lets try this.

Factory reset the EZICOMM and EZIO8SA. Power them back up and let the EZIO8SA reprogram the EZICOMM to look like a EZIO8SA. The LED on the EZICOMM should also pulse during the reprogramming. 

Take the EZICOMM and connect it to the PC with out resetting it. In the DockLight program PLM.ptp  The Get IM Configuration 02 73. Should get a reply back of 02 73 80 00 00 06. If it was reprogrammed by an EZIO8SA  or a 02 73 00 00 00 06 if it was not reprogrammed.

I found the Get Version 02 60 always reports it is a PLM even if reprogrammed but the Get Configuration 02 73. Would be 02 73 80 00 00 06 if it was programmed and not the default 02 73 00 00 00 06.

Edited by Brian H
Spelling and add stuff.
Posted

After you are able to see if the EZIO8SA has programmed the EZICOMM. We may have a better handle on what the problem is.

I looked at one of your previous posts. The back photo shows the EZICOMM is a base 2413 Dual Band Module. So one more thing to consider is it has power supply capacitors just like we see in our 2413S PLM.

Posted

So for "Factory Reset" that's the Press and Hold the SET button in while plugging the EZICOMM back in and hold SET until it the beeping stops. Then it'll buzz/beep again. I should do this while the EZIO8SA is connected, right to it, right? There is no separate EZIO8SA reset that I know of.

Then go to ISY Admin Console and try to add the device?

Or, unplug the EZIO8SA and connect the EZICOMM to the computer and run Docklight again?

Thanks much

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      37.2k
    • Total Posts
      372.6k
×
×
  • Create New...