El 07/07/14 08:40, Denis ha escrit:
> Hi everybody
>
> Up till now we always worked with FTDI and Prolific cables and the data
> that's
> been sent by our device can be received correctly.
> Now we started using a new FPGA that has an Exar USB serial convertor on
> board.
> http://www.exar.com/
On 07/08/2014 05:15 PM, Denis wrote:
> On Linux?
Like I said: `strace`
You will probably want to invoke it like `strace -f yourcommandgoeshere
yourargument1 yourargument2 ...`. The `-f` makes sure that any child
process that are forkes by `yourcommandgoeshere` will be traced aswell.
--
Ewald
On Linux?
> On 07/08/2014 04:19 PM, Denis wrote:
> > No, is not possible.
> > Is there a way to catch the setup of the serial interface before and
> > after open it?
>
> Have you tried strace (on OS X: dtruss with some command line options? I
> can look them up again if it helps)? This tool prov
On 07/08/2014 04:19 PM, Denis wrote:
> No, is not possible.
> Is there a way to catch the setup of the serial interface before and after
> open it?
Have you tried strace (on OS X: dtruss with some command line options? I
can look them up again if it helps)? This tool proved very helpful in my
las
No, is not possible.
Is there a way to catch the setup of the serial interface before and after
open it?
> > Up till now we always worked with FTDI and Prolific cables and the
> > data that's been sent by our device can be received correctly. Now we
> > started using a new FPGA that has an Exar
> Up till now we always worked with FTDI and Prolific cables and the
> data that's been sent by our device can be received correctly. Now we
> started using a new FPGA that has an Exar USB serial convertor on
> board.
> http://www.exar.com/connectivity/uart-and-bridging-solutions/usb-
> uarts/xr21v
> Dear Denis, did you see my solution? You can use ls to get the available
> ttyUSB devices attached and you can use ls to get the locks in the
> /var/lock folder. Please review my previous answer and see if that helps.
Thanks for your reply.
In order to guarantee the right operation of all progra
> So your OS is assigning different device names after reattaching? Sounds
> like a Linux problem, not a programming problem.
> Look at e.g. udev rules to persistently name the device ttyUSB0
Yes, you're right. But, read below:
1) Normal condition, /dev/ttyUSB0
2) Program starts and open USB0
3)
On 6-12-2012 9:18, Denis Gottardello wrote:
> Hi everybody. I have a problem with usb serial interfaces on Linux. If a
> serial device is disconnected from the machine and then reconnected, if
> before
> the serial had as name ttyUSB0, then it will assume ttyUSB1. Now the sequence:
> 1) The devi
> One idea concerning to your problem: AFAIK, Synaser
> inits COM port by the sequence:
>
>- clear DCB
>- set some fields of DCB
>- SetCommState(DCB)
Not anymore :)
>
> whereas typical implementation is
>
>- GetCommState(DBC)
>- change some fields of DCB
>- SetCommStat
On Jul 20, 2012, at 11:42 AM, Clinton Shane Wright wrote:
> To whom it may concern,
>
> Please can you assist me. I have installed Lazarus IDE in Ubuntu
> 10.04 and I get this message when I try to compile my application
> with synaser included inthe libraries of my project.
>
> synaser.pas(1
On Fri, 27 Jan 2012 11:16:27 +0200, Kocsis Levente
wrote:
>
> When I send data to the device I'm using AnsiString and I'm waiting for
> AnsiString result. I think that the problem is in the RecvBuffer function,
> where the buffer pointer is pointing to an AnsiString.
>
How do you get the byt
Thanks again Lukas. :)
Lukas Gebauer wrote:
>> Does anyone knows if Synaser can detect DCD status of a modem? If so, how
>> can it be done?
>>
>
> See the propery TBlockSocket.Carrier
>
>
> --
> Lukas Gebauer.
>
> http://synapse.ararat.cz/ - Synapse Delphi and Kylix TCP/IP Library
> http://
> Does anyone knows if Synaser can detect DCD status of a modem? If so, how
> can it be done?
See the propery TBlockSocket.Carrier
--
Lukas Gebauer.
http://synapse.ararat.cz/ - Synapse Delphi and Kylix TCP/IP Library
http://geoget.ararat.cz/ - Geocaching solution
---
A lot of the minimal distributions on this page were updated today with
the latest fpGUI and Free Pascal 2.4.2:
http://www.turbocontrol.com/monitor.htm
This is a new page with FPC 2.4.2 and fpGUI:
http://www.turbocontrol.com/easyfpgui.htm
This unreleased file with SynaSer for WinCE was als
A few notes I forgot to include in the readme...
Note that in WinCE the COM port name must include ":" on the end:
ser.Connect( 'COM1:');
Also note that this routine doesn't work:
GetSerialPortNames
--
The Next 800
> With the arrival of Delphi 2009 and Lazarus 0.9.26 I made some adjusts
> to correctly handle binary data ... Basically changing statements
> "String" to "AnsiString"
Well done, thank you!
Uploaded to SVN as rev. 120.
I must made some next modifications into synaser soon, because
support for W
> What a dumbass I'am. I was debugged read requsts (Timeout) but not the
> config. It returned 'The parameter is incorrect' and it's clear that
> the app couldn't work with this settings. Yestreday I tried to change
> everything but stopbits because the device is set to 1 stopbit - still
> returnin
riginal Message-
From: Lukas Gebauer [mailto:gebyl...@mlp.cz]
Sent: Tuesday, December 29, 2009 5:05 PM
To: Ararat Synapse
Subject: Re: [Synalist] SYNASER - port initialization problem
> Thank you for reminding me LastError function - it returns Timeout.
> Yes, first create, then Connect
> Thank you for reminding me LastError function - it returns Timeout. Yes,
> first create, then Connect and then Config. What's most isteresting is
> that this problem occures only after convertor pluging in. Since there has
> been some trafic on the converted port, there's no problem at all.
> How
Dne Mon, 28 Dec 2009 22:46:45 +0100 Jirka Hudec
napsal/-a:
> Since other apps can work proprly even for the first time, the question
> is why synaser can't ... :-(
I've never used Synaser, but your problem resembles me
troubles we met while trying recognize connected device
with convertor su
aser can't ... :-(
Thank you in advance
-Original Message-
From: Lukas Gebauer [mailto:gebyl...@mlp.cz]
Sent: Monday, December 28, 2009 4:07 PM
To: Ararat Synapse
Subject: Re: [Synalist] SYNASER - port initialization problem
> I'am fascinated by Synaser philosophy and successfully us
> I'am fascinated by Synaser philosophy and successfully using it to
> comunacate with DIRIS A20 multimeter over 485-to-USB convertor (based on
> FTDI chip). But during final testing I've found out that my app isn't able
> to connect to COM port after first pluging in the convertor and
> multimeter
To: synalist-public@lists.sourceforge.net
>> Date: Wed, 25 Mar 2009 12:38:16 +0100
>> Subject: Re: [Synalist] synaser compile problem using lazarus
>> cross-arm-wince-win32 complier
>>
>>> That means I can not use synaser under windows mobile system in PDA or
>&
learner, I want to have a try.
> From: gebyl...@mlp.cz
> To: synalist-public@lists.sourceforge.net
> Date: Wed, 25 Mar 2009 12:38:16 +0100
> Subject: Re: [Synalist] synaser compile problem using lazarus
> cross-arm-wince-win32 complier
>
> > That means I can not use syna
> That means I can not use synaser under windows mobile system in PDA or
> Smartphone?
Yes. It means - nobody ported Synaser to this platform yet.
--
Lukas Gebauer.
E-mail: gebau...@mlp.cz
http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib.
--
much.
> From: gebyl...@mlp.cz
> To: synalist-public@lists.sourceforge.net
> Date: Wed, 25 Mar 2009 11:58:21 +0100
> Subject: Re: [Synalist] synaser compile problem using lazarus
> cross-arm-wince-win32 complier
>
> > I have written an application to open virtu
> I have written an application to open virtual serial port(bluetooth)
> using 5dpo and synaser. When compile (set as LCL widget type: wince
> (beta); Target Platform: wince, arm);
> It gives error message as
>
> C:\lazarus\Sdpo\SdpoSerial\synaser.pas(1,1) Fatal: Can't find unit
> termio used by
04
An: Ararat Synapse
Betreff: Re: [Synalist] Synaser - parametr is incorrect - error 87
I don't use synaser but I'll toss out a guess:
com.config(9600,8,'N',0,false,true);
What is the 0 in the function call above?
If it's "number of stop bits" then it p
I don't use synaser but I'll toss out a guess:
com.config(9600,8,'N',0,false,true);
What is the 0 in the function call above?
If it's "number of stop bits" then it probably needs to be either 1 or 2, not 0.
-Original Message-
From: Tomas Rosa [mailto:tr...@seznam.cz]
Sent: Wednesday,
Hi all,
I want to use one serial port for writing to and reading from
two different devices. Therefore I wanted to open the port for reading
and then close it again.
I have tried the following for the reading part:
PROCEDURE lesen;
var ser: TBlockSerial;
begin
repeat
ser:=TBlockSerial.Cr
> {:stopbit value for 1 stopbit}
> SB1 = 0;
OK, there I had something wrong in my mind. Sorry, but I relied too
strong on my mind instead of looking it up.
> {:stopbit value for 1.5 stopbit}
> SB1andHalf = 1;
> {:stopbit value for 2 stopbits}
> SB2 = 2;
It works as it should, thanks
Richard wrote:
>> Look at stopbits, should be SB1, SB1andHalf or SB2.
>>
>> So use:
>>
>> ser.config(9600, 8, 'N', SB1, False, False);
>>
>>
> I did. No positive results.
> I used the value "1" instead of the constant "SB1" with the value 1,
> which should be equivalent.
What ever gave you the imp
> > Look at stopbits, should be SB1, SB1andHalf or SB2.
> >
> > So use:
> >
> > ser.config(9600, 8, 'N', SB1, False, False);
> >
> I did. No positive results.
> I used the value "1" instead of the constant
> "SB1" with the value 1,
> which should be equivalent.
> >
Wrong:
{:stopbit value fo
>
> Look at stopbits, should be SB1, SB1andHalf or SB2.
>
> So use:
>
> ser.config(9600, 8, 'N', SB1, False, False);
>
>
I did. No positive results.
I used the value "1" instead of the constant "SB1" with the value 1,
which should be equivalent.
>
>
>
>
>
>
> -
> ser.config(9600, 8, 'N', 1, False, False);
>From the documentation:
procedure Config(baud, bits: integer; parity: char; stop: integer; softflow,
hardflow: boolean); virtual;
Reconfigure communication parameters on the fly. You must be connected to port
before!
parameters:
baud
I made two modifivations in the program (see below) with only the
following effct: I only get "empty characters" (Spaces) instead of the
strings.
Am Donnerstag, den 27.11.2008, 18:15 +0100 schrieb Richard:
> > Based on you question and the information you have gathered thus far,
> > anything else y
> Based on you question and the information you have gathered thus far,
> anything else you need to know, maybe I can help?
Thank you for this offer!
I don't know if this mailing list accepts attachments so I have copied
the program "serialtest.pas" at the end of this mail.
I have connected my sen
Take a look at:
http://synapse.ararat.cz/doc/help/synaser.TBlockSerial.html
There's documentation for the Recv* methods.
The help file can be downloaded at http://synapse.ararat.cz/files/synahelp.zip
-
This SF.Ne
True, guess that is the case if you are supporting a free product.
Here is some information on the synapse components as well (to so much
synaser): http://www.dubaron.com/synapsecookbook/
Also, when searching the forums you should also find some information. The
documentation on the procedures in
Am Mittwoch, den 26.11.2008, 17:21 +0200 schrieb Werner Hauptfleisch:
> Thant link is pretty much what you need to know in order to work with
> Synaser. There is also some good examples available on the synapse
> website:
>
> http://ararat.cz/synapse/doku.php/download#synaser_serial_library
Sorry
Thant link is pretty much what you need to know in order to work with
Synaser. There is also some good examples available on the synapse website:
http://ararat.cz/synapse/doku.php/download#synaser_serial_library
On Wed, Nov 26, 2008 at 10:18 AM, Richard <[EMAIL PROTECTED]> wrote:
>
>
> > Let me
> Let me explain the problem in short, perhaps you could give me some
> hints on the documentation:
> On Linux I want to read from a measuring instrument, which is connected
> via /dev/ttyS1 (9600 8N1, only RxD used). It sends each second a string
> of roughly 16 Ascii-characters. This string sho
I bought a GUC232A made by IOGear (with a pl2303 prolific chipset) and
that works under both i386 and ARM Linux.
It appears that some linux drivers for FTDI and MOSCHIP chipsets have
problems.
I'm glad that I found something that works, and it also appears that
SynaSer and FreePascal work OK.
Werner,
> I have used simular converters before and this sound like a driver issue. I
> found that the USB-Serial converters from EasySync is the best and when
> connected to Linux provides a full 'real' serial port without any issues.
> Simply connect to ttyUSBx and continue from there.
Thanks f
Hi,
I have used simular converters before and this sound like a driver issue. I
found that the USB-Serial converters from EasySync is the best and when
connected to Linux provides a full 'real' serial port without any issues.
Simply connect to ttyUSBx and continue from there.
Are you able to comm
> Hi. I have written a program using Free Pascal / Lazarus which uses
> Synaser to communicate with a ham radio via a serial port at
> 4800/8/N/2. It is running under Windows XP SP2. When the radio is
> connected via a regular serial port it works fine. When connected
> using a USB to serial adapte
Mark Rogers wrote:
> I'm not ready to take the blame yet, much easier to blame the drivers :-)
>
OK, time for me to put my hand up...
I had a lot of problems.
Partly because I was not properly terminating my comms thread while
testing the code and that was often leaving the port tied up.
Par
Jon wrote:
> Ah yes, the good old PEBKAC issue
> (http://en.wikipedia.org/wiki/Pebcak). Get's me every time ;-)
I'm not ready to take the blame yet, much easier to blame the drivers :-)
I mostly use Linux now, so I forget that you can often fix problems in
Windows with a reboot!
> Seriously tho
>
> There was definitely something odd going on
> but it seems to have passed now.
>
Ah yes, the good old PEBKAC issue (http://en.wikipedia.org/wiki/Pebcak). Get's
me every time ;-)
Seriously though, to check the port names, examine the registry branch:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\
In addition to what I just wrote in reply to Lukas' email:
Jon wrote:
> Are you sure that the port is not in use? PortMon is always my first
> troubleshooting tool.
>
If I shut down my software and used the software supplied by the
hardware manufacturer (ie the software to talk to the thing
Lukas Gebauer wrote:
> No, here are no reason for this. I am using Synaser with USB emulated
> serials, I am using it for RS-895 too.
>
I thought it should be OK, it's nothing particularly unusual.
> What exactly is failing? Connect method or Config method?
>
I can't remember now, because
I have used SynaSer successfully with USB serial ports on Windows 95 upwards.
No fancy coding, I just followed the basic example.
> At the moment I can connect to the real COM1 ok but any
> attempts to connect to COM5 are failing (using SysInternals
> portmon, it recognises that COM5 exists but w
> Is there any reason why SynaSer would see the port any differently than
> Windows? Any suggestions as to what I can try to find the port?
No, here are no reason for this. I am using Synaser with USB emulated
serials, I am using it for RS-895 too.
What exactly is failing? Connect method or Conf
Yes, Hyperterm works fine. I connected one PC with Hyperterm instead off my
serial device, with the same settings (port, speed, handshake ...). The
second Hyperterm was running in terminal server session. The communication
works in both direction.
Mayby, Synaser ignores redirected serial ports ?
> Synaser Connect('COM2') pass without error, but external serial device seems
> to be not
> connected.
And Config call is OK too? (Lasterror is zero after Config?)
--
Lukas Gebauer.
E-mail: [EMAIL PROTECTED]
http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib.
-
Did you try with Hyperterm first ?
Maybe the name of the comport is not the one you expect.
regards
Thomas
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von
Roman Olexa
Gesendet: Mittwoch, 13. Februar 2008 08:20
An: synalist-public@lists.sourceforge.n
> Under Linux TBlockSerial class tries to use write lock file
> "/var/lock/LCK..ttyACM0". But the user haven't permissions to write to
> this dir. What is correct way to workaround this trouble? The possible
> ways are: 1). Edit "synaser.pas" unit and point another dir for lock file.
> 2). Allow u
Lloyd Thomas wrote:
> I don't understand where I am going wrong, but I have the following code in
> a windows app and a service. When I run the app in idle it uses 0% cpu, but
> if I run the service it uses 50% of the CPU.
> If I change the var activeport := false, (as to not receive serial data) t
ndreas
Berger
Sent: 27 September 2007 12:49
To: Ararat Synapse
Subject: Re: [Synalist] synaser example
[EMAIL PROTECTED] wrote:
> OK,
> No response yet, But i have simplified my code as 'terminated' cause a
> problem. So while the new code will run I get an error after the
&g
OK,
No response yet, But i have simplified my code as 'terminated' cause a
problem. So while the new code will run I get an error after the
Recvstring timeout.
'ESynaSerError with message 'Communication error 9997' Timeout during
operation'.
What does this mean?
How can I improve my simple code?
[EMAIL PROTECTED] wrote:
> OK,
> No response yet, But i have simplified my code as 'terminated' cause a
> problem. So while the new code will run I get an error after the
>
Instead of a "Repeat ... Until false" loop try a "While not(Terminated)
do" loop
> Recvstring timeout.
> 'ESynaSerError
> No response yet, But i have simplified my code as 'terminated' cause a
> problem. So while the new code will run I get an error after the
> Recvstring timeout. 'ESynaSerError with message 'Communication error 9997'
> Timeout during operation'.
>
> What does this mean?
It meaning - no reqested d
>
> So, I made new Synaser version what have removed Libc dependency on
> FreePascal, and count of needed modifications is much smaller then in
> "Charlie" case, and result code is cleaner.
>
> I publish this new Synaser version in next Synasnap, please, test it!
right, I hope to try it next wee
> problem with error 9997 resolved with: ser->AtTimeout = 4000;. It is
> minimum for correct functional. GSM Module Siemens MC55.
>
> But, I tried another component for com port communication (TComPort)
> and there is not problem with timeouts. And of cource when I send SMS
> via TComPort I got it
> And problem is, that everytime i get error 9997: Timeout during operation.
> after all ser->ATCommands My System is WinXP + BDS2006 update2. I
> tried Set Sleep(xxx) in all possible steps, but without positive result.
> SMS is sended always without problem, but alwais with this error. Please
Hi,
If you are sending a PDU message (looks like it, seen the 0x1a/ctrl-c)
be aware that the protocol is a bit 'mangled' (not like normal AT
commands behave). You must _not_ send a LF after the ctrl-c, and the
modem will report 'ok', but also send out a '>' char prior to the client
entering th
> cele dopoledne se lopotim s komunikaci GSM brany za pomoci Synaser ale
> nemuzu se hnout s odesilam sms. A jelikoz mi na foru nikdo neporadil
> tak pisu. Kod je v C++, ale to snad nevadi:
Well, but this is English forum. ;-)
--
Lukas Gebauer.
E-mail: [EMAIL PROTECTED]
http://synapse.ararat
68 matches
Mail list logo
