Hi,
Can this thread please be moved to the fpc-other list?
Thanks,
Jonas
FPC mailing lists admin
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Luca Olivetti wrote:
Al 04/07/13 17:24, En/na Mark Morgan Lloyd ha escrit:
In any event, my experience is that USB->serial converters are very poor
for anything that involves accurate timing, and I suspect that
controlling a 485 transceiver in conjunction with one would be
problematic.
Not if
Al 04/07/13 17:24, En/na Mark Morgan Lloyd ha escrit:
> In any event, my experience is that USB->serial converters are very poor
> for anything that involves accurate timing, and I suspect that
> controlling a 485 transceiver in conjunction with one would be
> problematic.
Not if the converter ma
On 04/07/2013 16:24, Mark Morgan Lloyd wrote:
> Lukasz Sokol wrote:
>> On 04/07/2013 12:03, Michael Schnell wrote:
>>> On 07/04/2013 12:52 PM, Lukasz Sokol wrote:
For RS485 adaptation, use a MAX232 like chip (to convert +-12
to ttl) and then a RS485 transceiver chip;
>>> If you want to cr
Lukasz Sokol wrote:
On 04/07/2013 12:03, Michael Schnell wrote:
On 07/04/2013 12:52 PM, Lukasz Sokol wrote:
For RS485 adaptation, use a MAX232 like chip (to convert +-12 to
ttl) and then a RS485 transceiver chip;
If you want to create hardware anyway, better use a PIC24 (pr PIC32)
chip with US
On 04/07/2013 12:03, Michael Schnell wrote:
> On 07/04/2013 12:52 PM, Lukasz Sokol wrote:
>> For RS485 adaptation, use a MAX232 like chip (to convert +-12 to
>> ttl) and then a RS485 transceiver chip;
>
> If you want to create hardware anyway, better use a PIC24 (pr PIC32)
> chip with USB plus a R
On 07/04/2013 03:55 PM, Luca Olivetti wrote:
Since the driver for prolific/ftdi usb to serial bridge (which is the
one these adapters use) is in the kernel since, like, forever, it will
work with any architecture.
I do know that there is a "standard" for how many USB-to-serial adapters
work.
On 07/04/2013 05:08 AM, Dennis Poon wrote:
thanks.
I am not using the fpc email as it seems off topic.
May I know the exact brand and model number of the adapter you used?
I have an ATEN usb-to-serial cable (UC-232A) but I am not sure how to
connect its serial pins to rs-485 's DIFFERENTIAL LINE
Al 04/07/13 12:24, En/na Michael Schnell ha escrit:
> But the problem might be that they don't come with a Linux driver for ARM.
Since the driver for prolific/ftdi usb to serial bridge (which is the
one these adapters use) is in the kernel since, like, forever, it will
work with any architecture.
Al 04/07/13 12:08, En/na Dennis Poon ha escrit:
> thanks.
> I am not using the fpc email as it seems off topic.
>
> May I know the exact brand and model number of the adapter you used?
I don't know the exact model, but it is one of these
http://vscom.de/1_1_09.htm
however there are other brands
On 07/04/2013 12:52 PM, Lukasz Sokol wrote:
For RS485 adaptation, use a MAX232 like chip (to convert +-12 to ttl)
and then a RS485 transceiver chip;
If you want to create hardware anyway, better use a PIC24 (pr PIC32)
chip with USB plus a RS485 tranceiver chip. So you get rid of the " ATEN
us
On 04/07/2013 11:08, Dennis Poon wrote:
> thanks. I am not using the fpc email as it seems off topic.
>
> May I know the exact brand and model number of the adapter you used?
> I have an ATEN usb-to-serial cable (UC-232A) but I am not sure how to
> connect its serial pins to rs-485 's DIFFERENTIA
On 07/04/2013 12:08 PM, Dennis Poon wrote:
I have an ATEN usb-to-serial cable (UC-232A) b
That is not suitable.
There are dedicate RS485 Adapters (many of those also support RS422 mode
(differential full duplex) ).
But the problem might be that they don't come with a Linux driver for ARM.
-
thanks.
I am not using the fpc email as it seems off topic.
May I know the exact brand and model number of the adapter you used?
I have an ATEN usb-to-serial cable (UC-232A) but I am not sure how to
connect its serial pins to rs-485 's DIFFERENTIAL LINES and how to set
that adapter into half-du
Al 04/07/13 11:16, En/na Dennis Poon ha escrit:
>> With RS-485 hardware you can - and supposedly need to - do
>> "half-duplex with output enable", if your hardware provides this.
>>
> After days of google search, I am afraid the bcm2835, the Soc of
> Raspberry Pi (the hardware I have to use) does
On 07/04/2013 11:16 AM, Dennis Poon wrote:
am afraid the bcm2835, the Soc of Raspberry Pi (the hardware I have
to use) does not provide this hardware support :-(
It states that it does not even support interrupt. Polling is the only
way for events :-(
As already discussed here the RPI is stri
Michael Schnell wrote:
On 07/03/2013 06:36 PM, Dennis Poon wrote:
Can you give me some pointer on directly using UART? I need to
implement half-duplex using UART for rs-485 protocol.
In a Linux system, accessing the hardware by user code is strictly
discouraged, at least whenever interrupts
On 2013-07-03 16:44, Dennis Poon wrote:
> Michael,
> I used the synapser.pas unit but the compiler choked at line 232 at the
> identifier 'B50', 'B576000' not found.
> Any idea ?
I believe you have an outdated version on Synapse then... Here is my
version of the code snippet you posted
On 07/03/2013 06:36 PM, Dennis Poon wrote:
Can you give me some pointer on directly using UART? I need to
implement half-duplex using UART for rs-485 protocol.
In a Linux system, accessing the hardware by user code is strictly
discouraged, at least whenever interrupts are involved (as with U
19 matches
Mail list logo