Thanks for pComms.
There was a problem with the included MSCOMM32.OCX version 5.00.3714 and I had to replace it with 6.00.8169.
During an alarm the output status does not show active siren.
No other issues so far. Waiting for the arming option
Guys,
Beta has been released to those who contacted me, if there are anyone else interested please PM me.
Matt
Thanks for pComms.
There was a problem with the included MSCOMM32.OCX version 5.00.3714 and I had to replace it with 6.00.8169.
During an alarm the output status does not show active siren.
No other issues so far. Waiting for the arming option
NessComms or pComms actually do work over IP, LAN or Internet.
On Ness’ side you will need either IP232/K6002 or a PC/laptop with freeware .
On PC with NessComms or pComms you will need freeware .
Are there better alternatives?
K2M, do you mean the right hand side output display doesn't show siren is on? I see this a bit on mine as it seems that for some reason the output on and output off are sometimes switched. Not sure why but will check.
Arming from the app may be an issue as only specific firmware allow for this and mine doesn't . That's why it's not implemented yet.
Matt
Sent from my iPhone using Tapatalk
I use HW VSP also. I've been looking for other software that is suitable also. But I am also contemplating writing some code to directly communicate to the serial/tcp interface.
Matt
Sent from my iPhone using Tapatalk
Woops, shouldnt read stuff on my iphone and not think about it before posting. Driving Outputs is not supported in any firmware below 7.8. I have 7.3, I will add arming functionality in next version. I do have a list of things I want to add also, but first will be connecting to the Serial/TCP convertor without the need of virtual serial ports.
Matt
While waiting for the arming option in pComms here is a quick way to arm/disarm your Ness.
To arm with user code 123 type on Windows command line:
To disarm with user code 123 type on Windows command line:Code:echo 8300560A123E7E > COMx
Where 'x' in COMx is the physical or virtual port number connected to Ness.Code:echo 8300460123EC0 > COMx
If it does not work, preset the port with command:
To use a different user code you need to format it as specified in Ness Serial Interface ASCII Protocol referred to earlier in the thread.Code:mode comX baud=9600 parity=n data=8
With all the hard work done has anyone thought of building a "binding" for home automation. I've just started using Openhab which has bindings for a number of alarm panels (mostly US) and it would be great to connect through my ELK232. The great thing with the ELK is that you can have multiple connections so it will work in parallel with Ness aComms.
I have added the following features that still need to be tested on a live system (hopefully over this weekend)
Arm Away Button
Arm Home Button
Disarm Button
Direct Connection to Serial Server from Application (no longer need a serial port emulator)
Send alerts on Arm/Disarm Events
Auto Scan now checks for Status of Outputs.
As soon as its ready I'll send out to testers again.
Thanks
Matt
Version 1.1 has been released to Beta Testers. All the above features have been added. I am thinking of removing the Serial Port part of the program now that direct network function is working. Thoughts?
Please send me all your feedback so I can improve the program
Thanks
Matt
Does any one know if there is a way to get the firmware version and model of the d8x/d16x via serial? Can't find anything in the ascii docs on it.
Matt
Sent from my iPad using Tapatalk
Venturis (11-04-16)
I have updated pComms again with some new features. If anyone wants a beta to try out please PM or email me. Also I am working on a plugin for LIFX Globes where you can set the globes to show different effects and colours based on events. Like Flash Red when in exit and entry delay etc.
Matt
auMatt, or anyone else, I'm after some help with the Ness ASCII serial protocol.
I have wired my D8X serial port to a Linux server. I'm happy enough with the passive stream of events and have written a small C program which logs them in human readable form to a file. I have also tried out write access with some keypad strings working fine.
One thing that just isn't working for me is setting the time (which I'd like to do automatically, say weekly). The panel gets into master program mode OK (shouldn't need installer mode) but ignores everything after that -- even exit program mode. I've experimented with various permutations of the ? end of line delay, and inserted various pauses into my code, but nothing seems to make any difference. Here is the most recent attempt:
Those sequences and timing seem to work OK when I push the buttons. Send them serially and long rejection beeps is all I get.Code:8300560M340E71? (already in prog mode, P340E then 10 sec. delay) 830036029EEC (29 minutes, delay) 8300560M341E70? (P341E, delay) 830036011EF5 (11 hours, delay) 8300260ME0B (PE -- exit program mode)
One thing I haven't tried is stringing the whole lot together. Anyhow, googling around turned up this thread and it seemed worth subscribing to see if you had any tips. Will be grateful for any advice.
Have fun,
Rob.
Since you have already working communication with Ness panel from laptop using NessComms software
you also have working serial connection cable.
I have Ness D8x Deluxe V8.4 and the panel is with 4 pins socket for serial connection on the panel board
but I could not find the pinout of that small socket. Could you share that info?
jag87,
Mine is 7.8.6 (apparently) and has only a three pin header for serial. With the board aligned as per the installer's manual (with phone jack at the top), the top pin is definitely serial ground. I'm less certain of the other two (I started with a direct DB-9 connector to a laptop before stringing cable properly to an RJ11 socket) but my notes suggest the sequence is Gnd, Tx, Rx. Pretty safe if you get them wrong anyway -- I just trial and errored my way.
Have fun,
Rob.
I found the picture of the serial cable connected to Ness 7.x and it looks like the GND at bottom of the 3 pin socket.
Is that correct as you said the GND is at the top of that socket.
However on the C-bus board the socket configuration is like you said, from top GND, Tx and RX
plus power red wire to the main board. Something must be wrong with that picture.
John
Last edited by jag87; 25-08-16 at 11:44 AM.
Here is where you can buy the cable, you can zoom on the picture
Bookmarks