C-Bus Plugin

[DLI]

Has anyone had any luck with the C-Bus plugin?
I can't seem to get any activity coming from the CNI. Is there
something in the setting up I have missed? I have successfully
controlled C-Bus groups without using the plugin.

Any info would be appreciated!
Thanks

[dogs_au]

Hi there, just a few things to do. have you downloaded cbus
diagnostics, if not download it from the clipsal website??

It will be the same setup for the pci or cni, but pci is better as you
can have multiple users on (8 total) at a time, where as the cni has
only one.
Go to settings in option 1 make sure you have connect, checksum, smart
mode ticked.
option 3, pcn, local sal, pun, exstat.
although all these settnigs are not required it will work, also in
option 2 depending on your cbus setup you may need to have burden and
clock ticked.

In your CF, make sure you have the global cache address and port 4999
in there, not the cbus address, the only itme you will use a the cbus
address and port (usually 10001) if you are using a cni direct to the
internet instead of a pci and global cache box

If you have a global cache box, go to its settings page, enable
multiple users, and make sure you baud rates are set to match up.

Dont use advanced settings in your buttons, just use basic settings
with only the cbus command on it. and it should work no problems at
all.

[Loz]

can cbus be controlled directly from the ipad (port 10001), or do you
have to go through a GC?

> > Thanks- Hide quoted text -
>
> - Show quoted text -

[DLI]

Thanks for the help, I'm not using the Global Cache though, accessing
through a CNI - although I do have a Global Cache iTach for my IP-IR
commands.
I've made sure the settings are ticked in the Diagnostics utility,
reloaded the project file and still seem to be having issues.

I've also got a C-bus wiser connected so I am using that to monitor
the C-Bus network while using iViewer and I can't see any commands
coming through when using the plugin preset functions (toggle etc),
but if I create a button in Gui designer and use the original string
to control the group (e.g Turn group on : \05380079xxxx ) then the
control works.

I'm guessing this comes down to the Javascript code. It's got me
stumped. Do I need to enable the javascript anywhere that I have maybe
missed?

[DLI]

This is something I am starting to wonder too. I can successfully
control my C-Bus through port 10001 straight through the CNI using
only the serial strings supplied by Clipsal, but cannot control my C-
Bus using the plugin through the same port.

[Jarrod Bell]

What version of iViewer are you testing with?
The plugin will only work with v4+

Look for iViewer Next in the app store to use this plugin with. Soon we
will be releasing "iViewer 4" app with all the features.
iViewer Next is our beta app and is only used for testing, not to be
used in client installs as we might break something in future updates
without notice.

Jarrod

[DLI]

I was using iViewer but have just tried iViewer next..seems to be the
same result.
I'm doing something wrong. Lol.

[Loz]

Im using iviewer next (4.0.4 build 164)

Like DLI if I dont use the plugin and just send strings direct to the
pci I can control groups, but is I use the plug in, it doesnt seem to
work.

I havent got a GC yet so I cant test with that.

On Jul 18, 2:55 pm, Jarrod Bell <jar...@guilink.com> wrote:

> > missed?- Hide quoted text -

[dogs_au]

without looking at what you have both done, just making sure that you
are using application 56 for lightings, i see DLI is from his string,
not sure about loz, also that you have loaded the JS into the project.
Now the other thing is, in your new system you setup, did you name it
cbus??? , protocol needs to be tcp. heartbeat is reply mode, and use
\x0D\x0A for the EOM. and what ever you do dont use 255.255.255.255
for your loopback. and be careful not to drag your ramp command onto
your toggle button as it will not work either. hopefully that helps.
One more thing even though you are not controlling it, see if you are
getting feedback, so set a digital join for example if it is cbus
address 2, set the digital join on the button to be 1002, thats if you
made your base join to be 1000 in your cbus toolbox, then try and
press the cbus light switch to see if your button on your ipad /
iphone changes state.

something to remember dont be concerned you dont see anything with a
button press on your ipad, etc in hyperterminal, diagnostics, herc etc
as being from third party and the setup used in the pci, cbus will not
respond, the other ipads etc on the network gets it levels, states etc
through broadcast.

on your button

> > - Show quoted text -- Hide quoted text -

[DLI]

Thanks again Dogs, my system is named cbus, I have \x0D\x0A sitting in
the EOM line, heartbeat reply mode. My cbus system is at 192.168.1.40
using port 10001.
This may be a stupid question but what should I have my feedback
broadcast set at?
Also do I need to tick Javascript sends command on each command?

[Jarrod Bell]

Broadcast should be at 255.255.255.255

If you have a loopback system, it should be 127.0.0.1

Jarrod

[xAPPO]

Did I miss the C-Bus beta invite or perhaps I wasn't selected :-(

I have the code from GITHub but there are no setup instructions there
- are there some somewhere ?
I think I've mostly worked it out from this thread although it's not
working for me either (direct to CNI) . I am not getting anything
back from the CNI although I can see that pressing a button with a
suitable join and dragged command sends some data (15 bytes) too it.
It is connecting OK, at least showing connected in the debugger but
curiously whilst iViewer is running I can still connect the C-Bus
Diagnostic Utility to the network which I shouldn't be able to as it's
single socket only.

K

[Jarrod Bell]

Ben can you help here?

Jarrod

[xAPPO]

OK - Made quite a bit of progress now, and I am receiving the correct
incoming data.

The issue seemed to be that I was using the Wiser inbuilt CNI for the
iViewer connection and another standalone CNI for the C-Bus
Diagnostics . From Diagnostics you can set the remote PCI / CNI mode.
But it was throwing checksum errors and losing comms in iViewer.
Reversing these so that C-Bus Diagnostics uses the Wiser CNI and
iViewer the standalone has made it all much happier. I am not sure if
this is a CNI options setting issue or not. It may be that Wiser
changes the mode as it hands the CNI over between connection requests
and it's own use. Whatever...it's a mute point as using the Wiser CNI
is not a viable solution anyway because the Wiser functionality is
sacrificed.

Getting there... :-)

Kevin

PS I'm very familiar with the C-Bus protocol and hope to include some
additional application and message decode support. Probably
thermostat / temperature / measurement and maybe security
application , if that's of interest to anyone. Or maybe the original
author 'dogs_au' / Scott(?) is intending this ?

[Jarrod Bell]

Original author was Ben, Scott helped out heaps with testing.

I would love to see some community input. Simply fork the repo, add your
stuff, and issue a pull request to us after its been tested to death.

Any documentation added to the wiki for the plugin would also be great!

Jarrod

[dogs_au]

Lol, I was just the pleb, this was worked out by a much smarter person
than me, one thing to remember which i forgot to mention is if you are
just using the cni, it prob is not working as you are already hogging
the link with diagnostics, wiser, herc etc if you have it running.

[DLI]

Na the connection isn't being used anywhere else, I can get a
connection join status as well.
Guess i'll have to wait until this is released officially.
Thanks!

[xAPPO]

My connection wasn't being shared either, although I did comment about
the anomoly of the access via the Wiser CNI.

Are there no basic setup instructions ! ? If not then I will write
some up but here's some quick backround...

Basically the model is that one iViewer , I'll call it the 'master',
needs a project with a TCP connection to C-Bus named 'cbus'. Because
a C-Bus CNI or PCI can only have one attached client (unless shared
through say a Global Cache serial) a second UDP connection named
'broadcast' is employed to forward update information to any other
active iViewers. I had expected that any C-Bus button presses on
iViewers are heard by the master (UDP broadcast) and then an
appropriate command forwarded to C-Bus over TCP but I can't see any
code for this :-( aspect. This means that as long as the iViewer
'master' is communicating with C-Bus then others are updated but they
can't control C-Bus and this will cease if it closes.

C-Bus periodically sends messages called MMI's that act as a
synchronisation method. The JS decodes the Level MMI's when received
(and provided the CNI is in a mode that sends them) to synch initial
button state on connection. The JS also monitors the originating
commands that change a group level on C-Bus and updates the state of
any button/slider who's join number 'matches' the group number.
Within the GUI configuration you create an offset for a button number
eg 1000 and hence button 1023 would 'match' C-Bus group 23. The
application number (eg 56 for lighting) is not stored in or derived
from the button number but each of the two supported applications
(lighting 56 and trigger 202) has it's own configurable offset . As
there are a max of 256 groups per application this is quite economical
on join usage but not flexible or necessarily easy to reverse lookup
or expand should you wish to support the other C-Bus applications.
However lighting and trigger cover the needs for most people.
Similar to my issues with xAP device identification the usage of the
join number to identify the C-Bus endpoint is messy but hopefully this
should go away when we have tags available.

The C-Bus plugin reads the XML file that C-Bus Toolkit creates (neat)
and you select individual groups within lighting or trigger
applications to add preset commands that then get listed under the
cbus connection. You can then drag the commands onto a button/slider
that has a suitable join number such that it then controls the C-Bus
group.

I am not sure quite what aspects of C-Bus there might be within the
DLL (I suspect only the GUI is within this code) but I've now had a
chance to better understand what is being done in the Javascript and
it's fairly straight forward. However no initialisation or setup of
the PCI / CNI is done upon initial connection and no check that it is
in the right mode. Hence no restore on exit is needed. This means
that it must be preconfigured to be in the correct mode or the
connection won't work. Various other applications that connect to the
CNI/PCI (C-Gate, C-Bus Toolkit via C-Gate and C-Bus Diagnostics) may
well change the mode and cause difficulties. There are also the
power up defaults for the interface to consider. This is I'm fairly
sure where all the problems are happening. Also no MMI request is
issued upon connect to speed state synchronisation.

In my usage of attaching via a single CNI and changing it's
defaults and then disconnecting and reconnecting from iViewer I did
not get a lot of success , I am not sure if this is because of an exit
cleanup of defaults by Diagnostics. I did get it to work by
configuring a second remote CNI .

Key to troubleshooting is ensuring that the system shows 'connected'
and that data can be seen continually arriving from C-Bus and creating
feedback matches. Pressing a button should show data being sent. Then
it's important that the correct data is arriving from the interface
and the mode setup here is all important. Checksums are required and
validated. The actual data (sIn) arrives via feedback from the cbus
connection and calls a function called doNetworkTraffic if you're
interested. This routine is a good place to check that checksums are
working too.

[xAPPO]

How many people here are stuck and would like to work through getting
this going and are you familiar with the iViewer web debugger ? If
people just want to await a release version we can do that too.

There are a few issues that I think people might have and I think I
have some solutions.

Firstly an easy one. An initialisation string that people can
include as a system startup command that will ensure that the CNI/PCI
options are set up in the correct mode. I just want to double check
it sets the modes that the code expects as I have no real plugin
documentation to know what was intended.

Secondly JavaScript changes to the MMI handling and the C-Bus
commands, but these are problematic because the C-Bus plugin DLL
overwrites the Javascript code each time you add a new command via the
GUI. Any changes you make to the JS get undone :-( I think this
was probably the only way that Ben could get the system names into the
JS. Unfortunately it makes a quick fix awkward.

I guess I could fork and alter the plugin VB source code but that's a
bigger task and really someone else's code base so I'd like to talk to
Ben first, but I'm not sure how to contact him and if he's still
involved in this. Jarrod could you get me an email address or maybe
he could contact me ?

Kevin

> ...
>
> read more »

[Florent Pillet]

Release version will come very soon, iViewer 4 has been submitted to the AppStore.

Florent

On 19 juil. 2011, at 19:30, xAPPO wrote:

> How many people here are stuck and would like to work through getting
> this going and are you familiar with the iViewer web debugger ? If
> people just want to await a release version we can do that too.

--
Florent Pillet - Software Engineering Lead
www.commandfusion.com

[xAPPO]

Florent - is there a more recent 'release' version of the C-Bus plugin
than the one maintained on GitHub ? I don't want to waste my time ,
try and assist testers and confuse your users by changing things if
there is. Or are you referring to iViewer 4 release which will not fix
these issues.

The C-Bus plugin contains non editable Javascript with coding
oversights, hard coded C-Bus network and unit addresses as well as
lack of initialisation that just wont work for most peoples C-Bus
install.

Kevin.

[xAPPO]

OK - I've now studied this C-Bus code and anyone succesfully using
the C-Bus plug in must have been using a different version than the
one I am looking at from GitHub. Are they ?
The version there is broken in so many places that it just couldn't
work. It has hardcoded unit addresses , status updates that miss most
groups and C-Bus message creation that include 'NAN' values in hex
only command strings becuase they've been skipped and not initialised.
Maybe this is an early version and the beta is not released yet ?
It couldn't have been tested or used in any useful way - have I got
the wrong version here ?

K

[Jarrod Bell]

I was under the impression it was a release version.
Ben would have to comment.

As always, feel free to fork and submit pull requests to us with updated
code.

Jarrod

[dogs_au]

HI guys,

I have not seen the gist one yet, but i will have a look tonight and
compare it, I spoke to ben very briefly the other night but didnt
mention it as he was very busy, but i am sure he will get back
regarding this when he is not as busy. Just to let you know I have
this running on two seperate cbus systems at the moment and also had
it running within minutes on a test bed as well last week. Ben was
talking about doing a itialisation string when i was testing it with
him, but just remember this is just a beta at the moment, I am sure
there will be additions. its not a big deal to setup the pci for now
while its still being tested, I dont have the problems with setting
changes as i have a dedicated pci just for CF. but if you do use
toolkit on the same pci it will change the settings and wiser i think
will as well, also the softtouch app changes the settings as well.. I
have another script being my general CF stuff, page flips, input
changes etc and upon start up i send a command to get the status of
everything. this plugin does work and works really well, temporarly I
cant see sending out the pci set up string in a separate script if it
is a pain to keep on setting up the pci because of other things
comming online changing it if yours is not dedicated. by the way i
have not had a problem yet with the plugin. so i am sure theres just a
mix up in the script on gist or something vey simple.

> >>> Florent Pillet - Software Engineering Leadwww.commandfusion.com- Hide quoted text -

[xAPPO]

Just to keep you posted Scott as I'm moving forward quite well now on
this.

Aside from that initialisation issue the major issue is that the C-
Bus unit address that the script recognises are hard coded (to unit
FE) which is the default new module address. If your CNI/PCI is not
at that address (as most wont be) then the Level MMI messages can't
match. If the MMI's don't match then joins aren't initialised until
each C-Bus group actually changes state. I have an initialise routine
now and that also sends an initial Level MMI request.

The problems in the C-Bus message parsing are in the JavaScript
rather than the plug in DLL's . So FTTB I have slightly altered the
plugin code such that it will support you altering the JavaScript code
and create a new MD5 code for the revised version should you wish,
which avoids it being overwritten. Now with some JavaScript changes
things are much better. I still need to double check issues such as
network numbers, bridges etc. I have also added the basic state MMI
(on/off/error/absent) to speed synch up but I also don't want to load
iViewer too much so this drops out after synch. The JS reads the unit
ID of the interface you are attching to to support message matching.
One lingering issues is that occasionally I am finding that I just get
no data coming back from the CNI even though it is showing connected,
and I'm not sure if that's a CNI issue, code , initialisation or maybe
even iViewer .

For any release version it must work standalone without requiring
external initialisation, status instigation or specific C-Bus network
reconfigurations, which I hope these changes will achieve.

I would be interested to know if the GitHub version is the latest
though....

Kevin

> > >>> Florent Pillet - Software Engineering Leadwww.commandfusion.com-Hide quoted text -

[DLI]

I have noticed that whenever I disconnect from the CNI via diagnostics
it sets the checksum to off. Just out of curiosity what is your
initialisation string?

> > > >>> Florent Pillet - Software Engineering Leadwww.commandfusion.com-Hidequoted text -

[RichyP]

Hi Guys,

Great work on this plug-in, however I'm having difficulty getting it
working.

I have read through the entire thread, which has pointed out a few
things, however still no luck.

If anybody can shed some light, much appreciated, my setup as follows:

1. Using GC connected to a PCI, with straight through cable
2. Ran the Cbus Diag tool, and set the Mode, as Dogs recommended.
3. Comms Setting 9600 8N1
4. GC properties in GUID - system name = cbus, tcp, port = 4999,
Hearbeat Mode = reply mode, EOM = \x0D\x0A
5. Under properties of project in Script Manager - checked that
cbus.js is loaded.
6. from the Bi\release\ dir cfCBusJS.dll copied into the GUID Plugin
dir.
7. Dropped a Toggle command from App 56 onto a button. Group = 21
8. Captured the serial strings coming out of the GC, seems correct.

Still no luck.


also which cbus Applications are supported in this Plugin?

On Jul 22, 9:49 am, dogs_au <sde...@crediblegroup.com.au> wrote:
> HI guys,
>
> I have not seen the gist one yet, but i will have a look tonight and
> compare it, I spoke to ben very briefly the other night but didnt
> mention it as he was very busy, but i am sure he will get back
> regarding this when he is not as busy. Just to let you know I have

> this running on two seperatecbussystems at the moment and also had

> > >>> Florent Pillet - Software Engineering Leadwww.commandfusion.com-Hide quoted text -

[xAPPO]

In the current version you will need your PCI unit address on C-Bus to
be 254.
Sometimes it seems that via C-Bus Diagnostics although you set the
checksum mode it becomes unset as soon as Diag disconnects.
Two applications are supported lighting and trigger (56 and 202).
I'm not sure this is required in all commands but best to make sure
you have all the joins (analog serial and digital) set up for a C-Bus
group in GUI elements e.g. if you are using an offset of 1000 for
lighting and group 22 then include a1022 d1022 and s1022 joins
somewhere.
I don't have a GC unit so I'm not quite sure how your point 8) works
but if you see the toggle command being sent to C-Bus could you post
it here. Does it change on alternate presses (there is no C-Bus
toggle command so iViewer has to look up the current state and send
the opposite

Lastly - are you able to use the web debugger ? If so can you look at
the system connection and check it is receiving data from C-Bus. In
the 'Mixed Log' tab you should also be seeing entries like

16:39:23> cbus matched feedback cbus network traffic

and in the script log if checksum matching is failing you'll see
errors - If the PCI is not in Checksum mode it won't accept commands
you send to it either.

CBus Checksum Error: Expected 'AN', received 'AD

K

> > > >>> Florent Pillet - Software Engineering Leadwww.commandfusion.com-Hidequoted text -

[RichyP]

Hi Kevin,

thx for the heads up,

bit silly it relies on the unit address to be 254, that looks like the
missing part for me, as all my jobs the PCI is either 0 or 1.
I did not think software burdens worked beyond those two numbers
anyway ?? (but thats a diff subject).

Shame only two APPs are supported.

since the GC talks serial, I'm feeding it back into a PC with a Hyper
Terminal equivalent, and seeing what this actual plugin spits out.
Like I said seems correct, but I only have a table table calc that
produces ON OFF RAMP at certain levels and instances.
I'll capture the toggle again, but I think your correct, it does not
produce a toggle.

Sorry I have not run the debugger yet, but I really should.

I have a few projects to deliver this week, so going to be hard. But
after that, I will spend some time on this.

I will also get our in house JS guru to clean it up, if that is ok
with everyone?

Your correct there are many things missing.

1) Init for PCI to set to correct mode.
2) Removing hardcoded Address
3) Support for other APPS

We are just so tied up at the mo, and I guess Ben is as well,
otherwise he would be on it...

Cheers everyone, JS modules like this, is the future of CF, so the
more we all contrib. the better ...

On Jul 24, 10:04 pm, xAPPO <thor...@gmail.com> wrote:
> In the current version you will need your PCI unit address on C-Bus to
> be 254.
> Sometimes it seems that via C-Bus Diagnostics although you set the
> checksum mode it becomes unset as soon as Diag disconnects.
> Two applications are supported lighting and trigger  (56 and 202).
> I'm not sure this is required in all commands but best to make sure
> you have all the joins (analog serial and digital) set up for a C-Bus
> group in GUI elements e.g. if you are using an offset of 1000 for
> lighting and group 22 then include a1022 d1022 and s1022 joins
> somewhere.
> I don't have a GC unit so I'm not quite sure how your point 8) works
> but if you see the toggle command being sent to C-Bus could you post
> it here.  Does it change on alternate presses (there is no C-Bus
> toggle command so iViewer has to look up the current state and send
> the opposite
>
> Lastly - are you able to use the web debugger ?  If so can you look at
> the system connection and check it is receiving data from C-Bus.  In
> the 'Mixed Log' tab you should also be seeing entries like
>

> 16:39:23>cbusmatched feedbackcbusnetwork traffic

>
> and in the script log if checksum matching is failing you'll see
> errors - If the PCI is not in Checksum mode it won't accept commands
> you send to it either.
>

> CBusChecksum Error: Expected 'AN', received 'AD

>
>    K
>
> On Jul 24, 7:18 am, RichyP <driv...@mydevice.com.au> wrote:
>
>
>
> > Hi Guys,
>
> > Great work on this plug-in, however I'm having difficulty getting it
> > working.
>
> > I have read through the entire thread, which has pointed out a few
> > things, however still no luck.
>
> > If anybody can shed some light, much appreciated, my setup as follows:
>
> > 1. Using GC connected to a PCI, with straight through cable

> > 2. Ran theCbusDiag tool, and set the Mode, as Dogs recommended.

> > 3. Comms Setting 9600 8N1

> > 4. GC properties in GUID - system name =cbus, tcp, port = 4999,

> > Hearbeat Mode = reply mode, EOM = \x0D\x0A
> > 5. Under properties of project in Script Manager - checked that
> >cbus.js is loaded.
> > 6. from the Bi\release\ dir cfCBusJS.dll copied into the GUID Plugin
> > dir.
> > 7. Dropped a Toggle command from App 56 onto a button. Group = 21
> > 8. Captured the serial strings coming out of the GC, seems correct.
>
> > Still no luck.
>

> > also whichcbusApplications are supported in this Plugin?

> > > > >>> Florent Pillet - Software Engineering Leadwww.commandfusion.com-Hidequotedtext -

[RichyP]

Kevin,

below is a couple of links to a string generator.

One version produces a string at a time, the table maker produces
every string possible in the specified APP, needs Excel to create the
table.
They are both Exe, so needs a Windows env.

Single String
http://www.mydevice.com.au/tools/cbusrs232.exe

Many Strings
http://www.mydevice.com.au/tools/cbusrs232tablemaker.exe

Note, these results were produced to be "Cut & Pasted" directly into a
RTI control system, and therefore they have escape sequences for some
characters. To send \ in RTI you need to send \\, a Carriage Return in
RTI = \r

for e.g.
Using the Single String exe, and creating a String for : APP 56 Group
1 ON =
\\053800790149g\r

you would ignore the first \ and the \r at the end (replaced with your
respective EOM).


I also triggered a Toggle for APP 56 Group 1 via the cbus Plugin -
this is what you get : note the [13] is the EOM for this particular
serial program.
Press 1
.\053800NAN010[13]

Press 2
.\053800NAN010[13]

Press 3
.\053800NAN010[13]

Press 4
.\053800NAN010[13]



Also, Kevin, when you say " PCI unit address on C-Bus to
be 254. " are you sure you mean Unit address, or do you mean Network ?
From what I can tell, the unit address, should not matter if it is
different.
by coincidence, the default Network Address is 254, and thats not such
a issue if it is hardcoded... 99% of jobs you will find set like that.

[xAPPO]

I wouldn't worry about getting your in house JS guru's on it as I've
pretty well sorted all these issues now and shortly, once tested a bit
more and presentable, I'll post it as a fork on GitHub. Just bear
with me a few days. Anyone who want's to play in advance just drop me
an email.

The 254 unit address really only effects the processing of the MMI
status messages from C-Bus - which provide the initial
synchronisation. It's an easy one to fix. It impacts the toggle
function of course. I've now included an extended status request
(MMI) at connect to ensure it all synchs up really fast. The
software burden doesn't necessarily have to be in the PCI of course,
or it could be the hardware plug in.

I've also added memory toggle so that a button can toggle between last
brightness and off rather than always back to full brightness as the
standard toggle does. The state model which was originally maintained
within join values now uses a JS object..

I'm interested in your comment about just 2 apps. Which other apps
were you particularly after support for ? Adding apps that use the
same message constructs as the lighting application is very easy and
also the most pervasive , but there are other applications that use
totally different constructs and some are very complicated.

Kevin

[RichyP]

Hi Kevin,

All good, frees us up ...

Extra APPS

Enable Control 203
SCENES 57
HAVAC 115
BACNET 90

Cheers, anyway we can help let us know ...

[RichyP]

Kevin,

most of those have a similar same structure as what is already
there...

I think the only painful one is HAVAC.

Cheers.

> ...
>
> read more »

[xAPPO]

We are a C-Bus Enabled Developer so pretty familiar with the C-Bus
protocol , at least in the lighting app . (

The message you posted includes a lowercase g at the end which is a
way for the PCI to be forced to acknowledge sequences of commands -
this isn't implemented in the plugin and probably doesn't need to be.
The PCI has very limited command buffering - only a handful of bytes.

As you will see in the messages that the plugin is generating they
include 'NAN' (not a number) in the middle of the message which is
why they don't work and also why the checksum isn't working .

The scenes app should be fairly easy but the HAVAC is quite a bit more
complex, but coincidently one I would like too.... I have never used
BACNET

K

[RichyP]

Yeah, HAVAC popular but complicated, I can send you logs if required.

BACNET apparently easy, and similar to the Lighting APP 56.

> ...
>
> read more »

[dogs_au]

Hi guys,

Sorry wasnt on for a couple of days,

ok, just skimmed over a few things on here, sorry if i am going over
same stuff already mentioned, not a big deal regarding the 254 network
address, although most people I know use this address, and is only a
small part of the js plugin, its only an address, and is only affected
by the status request message comming back (mmi), just set it up as
this to get it going for now, if having problems with another device
you use on the network changing the pci, cni setting,add another pci
etc in, if your got cbus in a house or installing it in a premises, im
sure another pci in the price wont lose the job especially if you add
it in the CF and ipad price you will be charging for. I have this on
mine as i use the other just for connecting to toolkit as it changes
the settings once downloaded to it. burden not an issue use a physical
one.
set up string

A330001900h
A341001903i

although dont need the letter on the back as it is just confirmation
as you will already know, just wrote that for anyone who wanted to
know.

currently lighting 56 and the trigger 202 is only in use, (this was
done on the dlt with it scenes page), although these button joins are
a bit different for setup, if you use 2000 as the base in the toolbox,
then it will be trigger group (e.g 002), then it will be action
selector (e.g 004), so when you assign the join on the scene button
for feedback it will 2002004

if you are still having trouble im quite happy to try to help you
through it over skype. I agree that more can be added to this plugin,
such as initialisation, hvac etc, but you can work around this for
now, its not going to hold you up getting it going.

> ...
>
> read more »- Hide quoted text -

[dogs_au]

Ahhh sorry xAPPO, you covered a few things already on my post, I
should have read everything in thread, before posting lol.
well im sure now there is enough info on this thread to get people
going now.

[RichyP]

Hi Dogs_au

Yeah, will give it another crack next week, got a few projects to
deliver, will just have to go with CF<->RTI for now...

But yes, there needs to be many more APPs added, I'll go over in
detail, after I get a chance to breath after this week is over.

Cheers Guys !!!!

On Jul 25, 9:56 pm, dogs_au <sde...@crediblegroup.com.au> wrote:
> Ahhh sorry xAPPO, you covered a few things already on my post, I
> should have read everything in thread, before posting lol.
> well im sure now there is enough info on this thread to get people
> going now.
>
> On Jul 25, 9:37 pm, dogs_au <sde...@crediblegroup.com.au> wrote:
>
>
>
> > Hi guys,
>
> > Sorry wasnt on for a couple of days,
>
> > ok, just skimmed over a few things on here, sorry if i am going over
> > same stuff already mentioned, not a big deal regarding the 254 network
> > address, although most people I know use this address, and is only a
> > small part of the js plugin, its only an address, and is only affected
> > by the status request message comming back (mmi), just set it up as
> > this to get it going for now, if having problems with another device
> > you use on the network changing the pci, cni setting,add another pci

> > etc in, if your gotcbusin a house or installing it in a premises, im

> ...
>
> read more »

[DLI]

Any update on this?

> ...
>
> read more »

[DLI]

Not sure if anyone is monitoring this thread anymore but has a new
plugin been released??
Using the debugger when trying to send a command I get this error;

> Invalid parameters for CF.send: (
CBus,
"\\053800NAN340\\x0d",
1
)

On Jul 27, 2:27 pm, RichyP <driv...@mydevice.com.au> wrote:

> ...
>
> read more »

[Jarrod Bell]

Is the text "CBus" wrapped in quotes in the code? Because it's a string
and needs it.

Jarrod

>> read more �

[DLI]

No, the text is exactly as appears in my post. So in other words this
script needs to be edited to send

"CBus",
"\\0538......etc"

?

[Jarrod Bell]

Possibly, might not be the problem though, just a thought at first glance.

Does your GUI project have a system called "CBus" ?

Jarrod

[DLI]

Yeah, project has system "cbus" all lowercase.

> ...
>
> read more »

[Jarrod Bell]

That sounds like it could be the problem. Make sure the javascript
matches the system name.

Jarrod

>> read more �

[DLI]

That seems to have fixed the error message I was receiving, now when
pressing a command I see the digital join change state eg;

d1044 = 0
d1044 = 1

Is that correct or should I be seeing some script action too?

> ...
>
> read more »

[Jarrod Bell]

Not sure, I have never used it. Anyone else?

Jarrod

>> read more �