Reply to thread

Message

<blockquote data-quote="kdschlosser" data-source="post: 1131816" data-attributes="member: 151614">ummm.... Atmolight uses Atmowin and if i used BOB with a raspberry pi. i believe it can do UDP or some other IP based protocol. But Atmolight with Atmowin and an Arduino is serial only. but with the wonderful world we live in there is a thing called serial over IP. and the wificard I have for the Arduino is bit banged right into a Serial UART chip on the Arduino. so all the Arduino see is serial data. And works great. It doesn't know any different. the TCP stack is built right onto the wifi chip so I have to que it up like an old school modem but instead of dialing a number i have it punch in an ip connecting to a socket on my computer which is then brought to the OS as a serial port.but Atmowin doesn't want to answer the proverbial phone (and no it is not a dialup connection) it's the easiest way to explain it because i have to give the wifi module AT commands just like i was back in the old BBS days.. I have no idea as to why because every other serial based app i try does just fine. data sends and recieves at 115200 perfectly. it has something to do with the file that's made on the computer (windows does makes files for connections just like linux). it's got something to do with that. I don't know what an error 2 is tho from Atmowin.</blockquote>

[QUOTE="kdschlosser, post: 1131816, member: 151614"] ummm.... Atmolight uses Atmowin and if i used BOB with a raspberry pi. i believe it can do UDP or some other IP based protocol. But Atmolight with Atmowin and an Arduino is serial only. but with the wonderful world we live in there is a thing called serial over IP. and the wificard I have for the Arduino is bit banged right into a Serial UART chip on the Arduino. so all the Arduino see is serial data. And works great. It doesn't know any different. the TCP stack is built right onto the wifi chip so I have to que it up like an old school modem but instead of dialing a number i have it punch in an ip connecting to a socket on my computer which is then brought to the OS as a serial port. but Atmowin doesn't want to answer the proverbial phone (and no it is not a dialup connection) it's the easiest way to explain it because i have to give the wifi module AT commands just like i was back in the old BBS days.. I have no idea as to why because every other serial based app i try does just fine. data sends and recieves at 115200 perfectly. it has something to do with the file that's made on the computer (windows does makes files for connections just like linux). it's got something to do with that. I don't know what an error 2 is tho from Atmowin. [/QUOTE]

Verification