Hearsay USB Serial
Pages: 1 2
Chris C. (2322) 174 posts |
Hey All, Is there a way to get Hearsay working with a USB → Serial adaptor? I have a PL2303 chipset on the adaptor. From reading I think I need the Block Drivers package and the PiSerial package. Perhaps the PL2303 driver for RISC OS? Chris |
Chris C. (2322) 174 posts |
I tried the SerialUSB program but *SerialUSBDevices shows nothing. !USBinfo shows that it sees the device. Should I just get an FTDI based device? |
Chris C. (2322) 174 posts |
I just bought a TTL to Serial device. I think this will help the cause also. |
Raik (463) 2026 posts |
I play around with FTDI and Delock FTDI adapter in the past. Was working with Hearsay after the correct setting (baud, parity, stopbits etc.) was stored in !FTDI but Nettle was working a bit better. |
Chris C. (2322) 174 posts |
I got my FTDI adapater this morning. I can communicate with the network switch using the Test_FTDI command. I tried to run that as a command inside Nettle but I get a “Handle is either illegal or has been closed” How did you get it working with Hearsay? It complains “Driver not found!” Curious to hear how you got it working.. |
Ronald May (387) 407 posts |
I think I need the Block Drivers package and the PiSerial package Tanks PiSerial Blockdrivers are for the pi gpio style port, needing a voltage adapter or one of the combined 9pin and 3.3-5V adapters unless you are connecting to another 3.3V serial device.(like another pi or gps perhaps). |
Raik (463) 2026 posts |
Sorry, I not remember in detail. Round about two years ago as I play around with the very early OMAP5 port without video output. I can try my setup at the beginning of the next week. |
Chris C. (2322) 174 posts |
Hey Raik, I got it to work in Nettle. The trick is it only works once. Once that basic file is run, it can’t be run again until reboot. I got my TTL → RS232 device. I am getting nothing. I have hooked VCC up to the GPIO 5v #2 pin and the others to Ground, TX and RX. I tried !Connector but I get nothing from my switch. It is a MAX3232 chip. The module lights up but I get nothing. I also tried a null modem and got nothing. |
Ronald May (387) 407 posts |
I tried !Connector but I get nothing Do you have a 32bit version of !Connector then? AFAIK it has only run on 26bit machines in the past |
Chris Mahoney (1684) 2100 posts |
It’s available in Bonus binaries. |
Raik (463) 2026 posts |
With Nettle, FTDI and nullmodem cable I have try this morning. Works like expected. |
Chris C. (2322) 174 posts |
I am using the 32 bit !Connector from the bonus binaries along with PiSerial block drivers. Don’t know what I am doing wrong at this point I am trying to connect to a simple switch at 9600 8N1 |
Ronald May (387) 407 posts |
It’s good to hear of the 32bit !Connector, the second requirement for serial is to establish wether the cable needs to be crossover or not. Changing tx for rx on the pi gpio should show a difference if this is a problem. Even with serial speed/handshaking wrong you should get some garbled data arriving. But does your device output anything by default? Can you see data when connecting to it from another platforms terminal? *Help modules shows a Serial Device module present but *Help Serial Device only returns for Serial. Important for !Hearsay using blockdrivers is p190 of the pdf |
Chris C. (2322) 174 posts |
So I updated my PI to the latest ROM image and firmware and now !Connector complains about the PiSerial drivers not being loaded even though I have double clicked on !SerialDev (which I got from !Store in the SatNav package. I do get output on my MacBook Pro. Maybe it’s the TTL → RS232 board. I don’t need a null modem as the console cable is a null modem. |
Ronald May (387) 407 posts |
I do get output on my MacBook Pro. Maybe it’s the TTL → RS232 board. As long as you know how to get some output when you want some. The 9pin adapters need a straight through cable when connecting api to a computer. Colins USBSerial Driver allows The SerialUSB adapter model with flying leads to connect a Laptop directly to the Pi pins. |
Chris C. (2322) 174 posts |
So my cables are as follow: 1 FTDI, 1 PL2303, 1 MAX3232 (TTL Adapter). I have to use a gender changer with the TTL adapter as it’s female and so is the crossover cable from the switch. The !SerialUSB didn’t recognize my PL2303 device, so I went with the FTDI cable, which does work in a limited fashion with the !FTDI program. I have tried the TTL adapter on my Pi2 and my B+ – no output from the switch when running !SerialDev. I really like RISC OS which is why I am trying to get it to work. It’s a nice environment. |
Ronald May (387) 407 posts |
So my cables are as follow: 1 FTDI, 1 PL2303, 1 MAX3232 (TTL Adapter). There are no known problems with the 9pin adapters but I speak from experience with the Pi Zero and Pi B. I would forget the switch for the time being, use the USB Serial adapter you know works with the MacBook and work out why the PiSerial Drivers aren’t working. Note that !FTDI may be using it’s own driver so be careful of conflicts with the blockdriver set. Reboot if you need to. By using things like |
Rick Murray (539) 13406 posts |
I cannot really provide much help as I am using an older ROM, however just wanted to point out that in order to use serial, two things are needed. The first is a driver to talk to the physical hardware, and the second is a blockdriver to act as an interface between the comms software and the low level driver. That said, the reason I mention an older ROM is that I believe support for the Pi’s onboard serial port is built into RISC OS now? If this is the case, use your USB serial dongle ‘backwards’ and you ought to be able to talk to the serial port using the “InternalPC” blockdriver (though forget about anything that needs flow control pins, the Pi’s default port is a straight Tx/Rx only). |
Ronald May (387) 407 posts |
That said, the reason I mention an older ROM is that I believe support for the Pi’s onboard serial port is built into RISC OS now? When I read Jeffrey’s post I thought he was just adding support for SerialOp calls. I guess these were used in the internal port blockdrivers so you may be right. I think connecting the Macbook → USB Serial adapter → 9pin adapter on the pi should be the least trouble for getting blockdrivers of either variety to work. Your USBSerial blockdriver would be of use to someone wanting all the available i/o pins for another job, I think there is a vga driver that uses a lot of pins, or for someone just not wanting to bother with the hardware connections at all. On the Iyonix, it would easily allow a third serial port. I did make a data logger with port 1&2 once. |
Raik (463) 2026 posts |
Have try to use a modem with a internal USB2Serial interface but I’m to stupid. Have try to use it with Nettle. The same. !Hearsay crash with a “error type 3” if it has seen the latest blockdriver with the USBSerial one inside. Help needed. I not really know what I (should) do. |
Rick Murray (539) 13406 posts |
For AT commands, etc, the interface doesn’t have any. It’s a dumb serial port. What is connected to the other end? |
Raik (463) 2026 posts |
As I wrote. A modem with a internal usb2serial adapter. |
Rick Murray (539) 13406 posts |
Does your modem have Rx/Tx indicators? Can you see if anything is being sent? Try also 115200bps. |
Raik (463) 2026 posts |
The baudrate by default is 19200bps. To change I must send a AT-command… |
Colin (478) 2433 posts |
I can’t comment on the serialdev drivers as I don’t use serialdev but have you tried changing the ‘nohandshake’ to ‘dtr’ or ‘rts’ in the serialterminal program it looks like you are receiving but not sending |
Pages: 1 2