First and most important, a program like this really should be run on multiple threads. I wrote a serial terminal program before this one in Ruby and it used threads. It seem Ruby's thread handling is superior to Python's. The problem was that Ruby doesn't have a serial library, so I was reduced to calling platform-specific utilities to set things up, and there were times when the serial setup would fail mysteriously.
Wxwidgets serial port programming
Much of my time designing this program was spent trying to get Python threads to work. Eventually I realized the problem was insoluble and is caused by Python's crappy thread handling, so I implemented a solution using a timer instead. I set up a recurring timer with an interval of 100 milliseconds, which calls a data processing function that reads the keyboard and serial port. This seems to work fine, even at the highest data rates. And, unlike the threaded version, there are no more core dumps every thirty seconds.
About the time of Fedora 14, the default location for serial port lock files changed, and this complicated the setup for preventing multiple accesses to serial ports. The old arrangement for a given port was:
The second reason is expandability. SAM-BA ships with support for all of Atmel's evaluation kits but does not provide generic configurations for other boards. It is a complex task with little documentation to modify SAM-BA to support custom boards. Sometimes, one can get away with using one of the evaluation kit configurations if it is similar to a custom board but other times not since custom external devices could cause a conflict. BOSSA is focused solely on programming the flash inside of the SAM device and so is independent of the board's external devices. So long as one develops a custom board with a crystal and I/O connections capable of communicating with SAM-BA, BOSSA can reliably program the flash without having to worry about external device conflicts.
BOSSA communicates with the SAM-BA boot loader running on the SAM device via either a RS-232 port connected to the SAM device's debug serial port or for SAM devices that support USB, over a USB CDC virtual serial port.
BOSSA also comes as an interactive shell which, in addition to flash programming, comes with a number of simple diagnostic operations such as memory reading and writing, PIO line manipulation, and ARM disassembly. The shell is built on top of the GNU readline library so it has the familiar line editing and history operations familiar to users of Unix command shells. A list of the supported commands is shown below.
I've tried the current method, I tried using libserial, I've tried using other people's "working" code. I was able to get it to work when I made a terminal version, the port configuration of which is in the current code, but not working. I've tried introducing delays when opening the port (I have a capacitor in the arduino to prevent it from resetting when the port opens - confirmed working.) I've researched the basics of serial communication, the settings, and different methods of sending it, but nothing is working.
The program does use a wxwidgets interface, which I wont include in the code for brevity's sake. It's worth noting that I've tried closing the port after every send, as well as just closing it when the program terminates. Neither seems to matter.
Is your C++ program allowing time for the Arduino to reset after the C++ program opens the serial port? And does the C++ program keep the serial port open until all communication with the Arduino is finished?
I wrote an application which controls some hardware by reading and sending commandstrings over an serial port. These commandstrings often contain numbers using always a dot as decimal point.Also, the program supports two languages (english and german) by using wxLocale and _() for all displayed strings.I am using wxString throughout the programm. For the conversion of strings read from the serial port I use the wxString method "ToCDouble" which works fine since it expects an dot as decimal point.To prepare a string I want to send to the serial port I used "wxString::Format" but when I initialze the german wxLocale it gives me an ',' as decimal point where I need an dot. As a workaround I replace the ',' with a dot after the call to "wxString::Format".So here is my question. Is there a function for converting double to wxString using the "C" locale instead of the application-wide locale (just as ToCDouble does for wxString to double)?Or does somebody know a better way as my workaround to resole this issue?I lookt through the wxWidgets-Docu and searched the internet but didn't find anything helpfull.If there is no such function, I have to stick to my workaround, but I would prefer to use a wxWidgets-function.I am using the wxMSW build of wxWidgets 2.9.2.Thanks,Michael-- ##############################Michael Himmelreich SoftwaredesignKieserstraïœe 1507749 JenaTel.: 03641 528608Mobil: 0175 8167674Email: mic...@himmelweb.de
PonyProg support ludipipo and JDM interface to program PIC16x84. To select it choose "JDM I/O" from the Options - Setup menu and the serial checkbox. If you use Linux or experiment problems select "JDM API".
This simple GUI allows to select a serial port and open it (the baud rate is fixed to 115200, 8N1 format). Once it is opened, there is a line where to write text to send to the serial port while received text is showed below.
thanks for your serial port classes. Do you want bug reports? In that case: If you create an instance of the BufferedAsyncSerial class without arguments and later call open() then it will never receive anything.
Thanks for your article on serial ports. As a newbie to Qt and C++ i have found the info a great help.On a GUI i was trying to figure out the best way to read what COM ports are available and show them in a combo box. I came up with the following:
and surround the call to open() in your code in a try..catch block.In this way you should be able to check if the serial port was opened successfully (no exception thrown) or not (exception thrown).
class AsyncSerialImpl : private boost::noncopyable{public: AsyncSerialImpl() : io(), port(io), open(false), error(false) writeQueue.reserve(IO_BUFFER_SIZE); receivedDataBuffer.set_capacity(READ_CIRCULAR_BUFFER_SIZE); /// IO Service object. boost::asio::io_service io; /// Serial port object. boost::asio::serial_port port;
AsyncSerial::AsyncSerial(const std::string& devname, unsigned int baud_rate, boost::asio::serial_port_base::parity opt_parity, boost::asio::serial_port_base::character_size opt_csize, boost::asio::serial_port_base::flow_control opt_flow, boost::asio::serial_port_base::stop_bits opt_stop) : m_pimpl(new AsyncSerialImpl) open(devname, baud_rate, opt_parity, opt_csize, opt_flow, opt_stop);
void AsyncSerial::open(const std::string& devname, unsigned int baud_rate, boost::asio::serial_port_base::parity opt_parity, boost::asio::serial_port_base::character_size opt_csize, boost::asio::serial_port_base::flow_control opt_flow, boost::asio::serial_port_base::stop_bits opt_stop){ if (isOpen()) close();
setErrorStatus(true); // If an exception is thrown, error_ remains true m_pimpl->port.open(devname); m_pimpl->port.set_option(boost::asio::serial_port_base::baud_rate(baud_rate)); m_pimpl->port.set_option(opt_parity); m_pimpl->port.set_option(opt_csize); m_pimpl->port.set_option(opt_flow); m_pimpl->port.set_option(opt_stop);
If I understood correctly, you want to set other serial port parameters, such as flow control and parity? You could just extend the open() member function in QAsyncSerial to take additional parameters, and maybe add default values so as to remain compatible with code that just passes the first two. Then in the implementation of open() in QAsyncSerial, just pass those parameters to the CallbackAsyncSerial open() member function.
thanks a lot for your quick reply fedetft. Yes this is my aim and launch at least several threads for reading serials ports. I was doing something else like instanciat at first the QAsyncSerial object in the mainwindow constructor and making setter in QAsyncSerial to set Parity stopbits flowcontrol and dataBits but it seems to be not a good way.
The important thing when reading data from serial, is to bind the reading of the data to a timer, so that the app will read data only at a certain rate and it won't crash. Here's a basic example that draws a line and a rectangle from the wxPython API (but you can use other Python libraries for drawing, like Matplotlib or Cairo).
First of all, I'm using an AVR microcontroller (albeit an xmega) with only 4K or RAM and 64k of NVRAM (minus the bootloader) to perform allof the control functions, including MIDI and patch programming, as well as the (dual DCO) tone generator, envelope timing, and modulation.And with dual serial ports, one for MIDI, one for programming. Yeah.
A major improvement to the V2 design from over 3 years ago, the V3's DCO features dual tonegenerators and greatly improves the sound quality. Additionally, the VCF is far more accuratewith extended range as compared to the earlier version. This is primarily due to the increasedspeed and advanced peripherals found in the ATXmega32e5 processor, as well as improvements inthe overall design.Additionally, programming for Version 3 uses a second serial interface at 115kbaud. Plans are to usean FTDI or similar USB to serial bridge. For now, it uses an 'FTDI friend' or similar cable.
A proof of concept version, using a 'proto board', significantly reduces the total parts count,while simultaneously improving the quality WAY beyond original expectations. Version 3 will costless to make, be physically smaller, and likely support an on-board USB serial device (like FTDI)rather than requiring an external serial device to be plugged into it. The proof of concept designis working as expected and I will add information to this web page as the project moves forward.Some of the information on this page pertains to Version 2 and earlier (including the soundclips). When I have some good sound clips available for V3, I shall make them available from thisweb page. In general, V3 is less 'buzzy' and has additional waveform capabilities that you'd expectto find on high end synthesizers, suchy as dual DCOs with de-tuning capability, true sine wavegeneration, symmetry control, 4 noise colors, and so on. 2ff7e9595c
Yorumlar