Hi,
I am having some trouble sending XML through the command processor. Here's what the command is when I debug the char pointer in GDB, and the XML I am sending:
https://gist.github.com/df72eb72fa7df63c02dd
The "6 " before the command just tells it what to do and (I guess) can be ignored. Notice ...
Search found 81 matches
- Mon Jul 26, 2010 9:15 am
- Forum: NetBurner Software
- Topic: command processor and XML input
- Replies: 4
- Views: 5752
- Mon Jul 19, 2010 6:57 pm
- Forum: NetBurner Software
- Topic: Communication protocol
- Replies: 9
- Views: 9552
Re: Communication protocol
Tod,
I actually just read up on istringstream and that's it's safer, so I will probably use that. It seemed non-trivial to parse multiline content with it (like human readable XML), but I can just strip newlines out on transfer: problem solved.
Thanks for the tips!
Christoph
I actually just read up on istringstream and that's it's safer, so I will probably use that. It seemed non-trivial to parse multiline content with it (like human readable XML), but I can just strip newlines out on transfer: problem solved.
Thanks for the tips!
Christoph
- Mon Jul 19, 2010 12:51 pm
- Forum: NetBurner Software
- Topic: Communication protocol
- Replies: 9
- Views: 9552
Re: Communication protocol
Sounds good, thanks!
Christoph
Christoph
- Mon Jul 19, 2010 12:10 pm
- Forum: NetBurner Software
- Topic: Communication protocol
- Replies: 9
- Views: 9552
Re: Communication protocol
Thanks Chris!
The data should be human readable and easy to construct, thus XML. I'd prefer json, but found a nice XML parser that is super fast and lightweight, so we decided on XML.
Looks like I wasn't too far off with sscanf, that's good to know :)
What do you use for testing the board in ...
The data should be human readable and easy to construct, thus XML. I'd prefer json, but found a nice XML parser that is super fast and lightweight, so we decided on XML.
Looks like I wasn't too far off with sscanf, that's good to know :)
What do you use for testing the board in ...
- Mon Jul 19, 2010 11:26 am
- Forum: NetBurner Software
- Topic: Communication protocol
- Replies: 9
- Views: 9552
Communication protocol
Hello,
I am looking for some advice about how to structure the communication to a TCP/IP socket on the board.
Ideally, I'd like to be able to send it some kind of header that defines the kind of content that can be expected.
Right now, I use sscanf to get an int, which is the mode, and a float ...
I am looking for some advice about how to structure the communication to a TCP/IP socket on the board.
Ideally, I'd like to be able to send it some kind of header that defines the kind of content that can be expected.
Right now, I use sscanf to get an int, which is the mode, and a float ...
- Wed Jul 14, 2010 12:47 pm
- Forum: NetBurner Software
- Topic: serial speeds
- Replies: 12
- Views: 14459
Re: serial speeds
Thanks for your patience 
I knew the pedestal worked, since it was fast on the laptop (which used the working cable), so I suspected my code. Your board being the problem was the last resort for me; glad it wasn't it.
Christoph

I knew the pedestal worked, since it was fast on the laptop (which used the working cable), so I suspected my code. Your board being the problem was the last resort for me; glad it wasn't it.
Christoph
- Tue Jul 13, 2010 4:54 pm
- Forum: NetBurner Software
- Topic: serial speeds
- Replies: 12
- Views: 14459
Re: serial speeds
Hi guys,
Thanks for all the tips. I figured it out, and it was rather dumb. The pedestal has two serial connections coming from it that apparently do the same thing. It's just that one cable does that thing fast, and the other very slowly. I was using the slow cable, so swapping cables sped the ...
Thanks for all the tips. I figured it out, and it was rather dumb. The pedestal has two serial connections coming from it that apparently do the same thing. It's just that one cable does that thing fast, and the other very slowly. I was using the slow cable, so swapping cables sped the ...
- Tue Jul 13, 2010 3:27 pm
- Forum: NetBurner Software
- Topic: serial speeds
- Replies: 12
- Views: 14459
Re: serial speeds
Gavin,
Thanks for explaining, that makes sense. It's 8 bit data, 1 start 1 stop bit, no parity.
I know the device can handle it because its own program gets the data fast over serial, through a USB adaptor no less.
I think I may be making some headway though, but nothing sure yet.
Christoph
Thanks for explaining, that makes sense. It's 8 bit data, 1 start 1 stop bit, no parity.
I know the device can handle it because its own program gets the data fast over serial, through a USB adaptor no less.
I think I may be making some headway though, but nothing sure yet.
Christoph
- Tue Jul 13, 2010 1:22 pm
- Forum: NetBurner Software
- Topic: serial speeds
- Replies: 12
- Views: 14459
Re: serial speeds
How are you reporting your incoming messages?
I write them to a RingBuffer and read it out in another task, and write that out to a network socket. When I do that, I get tons and tons of 0.0 (meaning the RingBuffer is empty), with a real data value mixed in every once in a while, so it seems ...
I write them to a RingBuffer and read it out in another task, and write that out to a network socket. When I do that, I get tons and tons of 0.0 (meaning the RingBuffer is empty), with a real data value mixed in every once in a while, so it seems ...
- Tue Jul 13, 2010 11:27 am
- Forum: NetBurner Software
- Topic: serial speeds
- Replies: 12
- Views: 14459
Re: serial speeds
Hi,
The other possibility is that the test app setups the device to output faster.
The device is set to 115200 baud, which is the max it supports, so the speed should be the same.
Try connecting the device to a PC serial port and see how fast its sending.
Doing just that with a USB adaptor ...
The other possibility is that the test app setups the device to output faster.
The device is set to 115200 baud, which is the max it supports, so the speed should be the same.
Try connecting the device to a PC serial port and see how fast its sending.
Doing just that with a USB adaptor ...