AGG Software Forums
November 24, 2024, 01:57:49 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Welcome on our forum!
 
  Home Help Search Login Register  
  Show Posts
Pages: [1]
1  Online Help Center / Data loggers and plug-ins / Re: Error using a Serial Device Server (RS232 to TCPIP device) on: May 20, 2010, 11:20:00 AM
Thank You that helps just fine.

I managed to find the MOXA 5110 here in Greece for an affordable 140 Euro so I will go with that.




2  Online Help Center / Data loggers and plug-ins / Re: Error using a Serial Device Server (RS232 to TCPIP device) on: May 20, 2010, 12:02:56 AM
Can you propose some that will work?

3  Online Help Center / Data loggers and plug-ins / Error using a Serial Device Server (RS232 to TCPIP device) on: May 19, 2010, 03:37:54 PM
Hi,

I am using the PBX data logger for a few weeks now and I would like to connect a second PBX over a virtual COM port created by the driver software of a Serial Device Server (Advantech ADAMS 4571L)
see picture server.jpg

This device connects to a serial port and transfers the com port data over the LAN to a PC where a virtual com port (COM8) has been created. This acts like a normal com port under windows (as if the serial device was connected on the PC itself). I can open COM8 with hyperterminal and log data to a text file.

If I now create a configuration for COM8, the PBX logger can not open it and I get the message:

COM8 can't be opened [Apro Exception]


see picture error.jpg

Any Clue ?
4  Online Help Center / Data loggers and plug-ins / Re: Foreign Character Sets on: May 11, 2010, 10:57:14 AM
Sorry!

it was my mistake, I had changed the sa password on the SQL server. I had updated the system ODBC connection with the new password but forgot to edit the data Logger configuration as well.

Thanks and again sorry for the false alarm!

PalMan
5  Online Help Center / Data loggers and plug-ins / Re: Foreign Character Sets on: May 10, 2010, 05:19:32 PM
Dear All,

I have now registered the product and I am using the Panasonic KX-T1232.xmlz file you send me for the last days.

It seems that now I have another small problem:

some calls appear as they have been made to or from extension 255 but concern other extensions

See for example serial log on attached pbx.gif, a call is been made from extension 140 to 6976770884
This entry appears in the SQL as made from ext 255, see sql.gif

I have attached a log file as well

Thanks
6  Online Help Center / Data loggers and plug-ins / Re: Foreign Character Sets on: May 04, 2010, 11:48:32 PM
Thank you very very very very much !!

This has solved my foreign character issue just fine.

I also feel the need to thank you once more for your remarkably fast response.
It is the first time after 25 years in the IT world that I witness such a swift solution following a blog post.



7  Online Help Center / Data loggers and plug-ins / Re: Foreign Character Sets on: May 04, 2010, 03:04:06 PM
Thank You!

here is the log file

and I have added an explanation file for PM AM and INCOMING

8  Online Help Center / Data loggers and plug-ins / Foreign Character Sets on: May 04, 2010, 01:53:36 PM
my Panasonic PBX model KXTD1232 exports date and time with PM and AM symbols in Greek characters
farther the flag "Incoming" is also exported in Greek characters. (see DateTime.gif)
This is something I can not change because the PBX comes with preinstalled Greek ROM chips.
Also I am not allowed to change the time field from 12h to 24h display.

When capturing data from the serial port now, the logger can not translate this characters correctly and therefor leaves the SQL tables CALL_TIME column empty. (see CALL_TIME.gif)

Also the Incoming Flag is not recognized. (see INCOMING.gif)

Has anyone ideas how to solve this issue?

Greetings from Athens, Greece !



Pages: [1]
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines