Home Automation Forum - PLC-BUS smart power line communication
http://plc-bus.info/

Starting with PLCBUS
http://plc-bus.info/viewtopic.php?f=48&t=54
Page 4 of 4

Author:  PlcBuster [ Fri 22. Apr 2011, 18:08 ]
Post subject:  Re: Starting with PLCBUS

Regarding your first question, you are correct. the interface listens on the bus and brings via USB/232 all PlcBus messages it finds.

About the getting hot while receiving, I didn't check it, but according to guru's explanation, I think it would require sending a pulse to generate the heat.

Should be easy to verify if you have a scene module and an interface. just keep sending scenes and then check the interface for heat.

Author:  PLCBUSguru [ Mon 25. Apr 2011, 16:56 ]
Post subject:  Re: Starting with PLCBUS

The interface just goes hot while sending commands.

Yes - PLC-BUS interface is an eavesdropper!
Each PLC-BUS command on the bus can you receive with the PLC-BUS interface.

But ACK pulse, ID pulse or ON pulse are not a PLC-BUS command.
The ACK is just one PLC-BUS impulse on the bus.
The PLC-BUS interface generates a complete RS232 message from this one impulse!

When other PLC-BUS controller (e.g. mini controller) sends a command, you can receive this command with the PLC-BUS interface – it is like the bus echo, but the interface does not handle the ACK. So you do not receive an ACK message from PLC-BUS interface on the RS232 interface.

Quote:
The ACK Pulse
The ACK Pulse is a single PLC-BUS Pulse that is generated in Position #3 of the PLC-BUS Frame immediately following the end of a PLC-BUS Message. Its purpose is to indicate to a transmitting device that the intended receiving device accepted the PLC-BUS Communication Packet. A PLC-BUS device only generates the ACK Pulse when it receives and accepts a PLC-BUS Communication Packet that has the ACK-bit set to 1.

Quote:
The ID Pulse
The ID Pulse is a single PLC-BUS Pulse that is generated in Position #3 of the PLC-BUS Frame (immediately following the end of a PLC-BUS Message) that corresponds to the receiving device’s Unit ID. For instance, if the receiving device’s Unit ID is 4 then it will generate its ID Pulse 4 frames (AC half-cycles) after the end of the received PLC-BUS Message.

Author:  QmQ [ Wed 15. Jun 2011, 00:07 ]
Post subject:  Re: Starting with PLCBUS

OK, I had a little break from PLCBUS but I'm back now.

I have made an observation that might be obvious but I'd like a confirmation.

The UserCode value is meant to distinguish between different homes that might be close enough to receive each others data.
The HomeUnit value is meant to distinguish between different devices in one home.

So if I set up a system in my own house I always set the UserCode to some constant value and setup all the devices with that UserCode value and a different HomeUnit value for each device.

Is that correct? I find the names misleading...

Author:  PlcBuster [ Mon 20. Jun 2011, 23:12 ]
Post subject:  Re: Starting with PLCBUS

QmQ,

My understanding is that devices ignore commands with a different user code (i.e. 3 phase coupler which usually just forwards the command/response onward)

Author:  PLCBUSguru [ Tue 21. Jun 2011, 07:39 ]
Post subject:  Re: Starting with PLCBUS

You must know PLC-BUS use the same addresses as X10 (home code, unit code) and extended these with the user code.
All modules they want work together must have set up the same user code.

So it is possible to have more installation with different user codes at same house. E.g. one house has more flats!

Author:  QmQ [ Sun 26. Jun 2011, 15:39 ]
Post subject:  Re: Starting with PLCBUS

PLCBUSguru wrote:
You must know PLC-BUS use the same addresses as X10 (home code, unit code) and extended these with the user code...


Thanks for that valuable piece of information!

Page 4 of 4 All times are UTC + 1 hour
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/