Not signed in (Sign In)

Vanilla 1.1.5a is a product of Lussumo. More Information: Documentation, Community Support.

    •  
      CommentAuthorhusar
    • CommentTimeJan 26th 2010
     
    As I have been developing my own front end for the OpenSprints hardware there has only been one significant snag. I mentioned it in another post but I wanted to put in my bid for an official request in the next firmware.

    Goldsprints FX is developed in Flex and uses ActionScript and MXML as the programming language. Once Flex opens the stream to the Arduino you can send commends and get anything it puts out. Commands are sent as follows...

    xmlSocket.send("g");

    xmlSocket.send("s");

    xmlSocket.send("l55");

    The limiting factor here, and a slight thorn in my side, is that I can't send any none-keyboard accessible commands. The smallest distance I can set is and "l" with two spaces or something like 2953 meters on a 4.5'' roller.

    So, the impact of this is that I have to check the ticks in my my code to end the race for each rider with my own code. It is not too big of a deal but it sure would be easier if I could simple check for the end "t" command that the Arduino puts out on its own.

    The other impact is the start lights kicks off as expected the end light doesn't when I have two sensors per rider or even one sensor per rider. Basically all the sensors stay green until I make sure that all riders have completed the distance and send the stop command. Then and only then do the sensors go red.

    Neither of these are show stopper for me. They are just inconveniences right now. I can work around the distance with my own code but I cannot work around the red/green light issue without creating my own firmware to the OpenSprints system. One of my original goals was not to reflash the OpenSprints system just to support my front end. I want it to run off the OpenSprints system with no modifications. This allows people more options when choose the right front end to meet their needs.

    So, my request for the next release is to be able to set the distance using the ActionScript send("") command with keyboard type-able characters only.

    Let me know if anything did not make sense or you need more information. Happy to help any way I can.
    •  
      CommentAuthorhusar
    • CommentTimeFeb 12th 2010
     
    Any word on any firmware updates anytime soon?
    •  
      CommentAuthorjonfen
    • CommentTimeFeb 19th 2010 edited
     
    husar:
    Goldsprints FX is developed in Flex and uses ActionScript and MXML as the programming language.

    The limiting factor here, and a slight thorn in my side, is that I can't send any none-keyboard accessible commands. The smallest distance I can set is and "l" with two spaces or something like 2953 meters on a 4.5'' roller.


    I did a quick google search, and it looks like you can send non-keyboard characters. Using the:

    /xnn

    whereas: The ASCII character with the character code specified by the hexadecimal number nn

    Reference, actual document page 138 (not page number)
    •  
      CommentAuthorhusar
    • CommentTimeFeb 19th 2010 edited
     
    Are you sure it was page 138? I couldn't find it but I did find basically the same thing here http://livedocs.adobe.com/flash/9.0/main/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=00000948.html

    I am pretty sure I tried that but let me give it another go. I think it did not work because I was not just manipulating a string but sending it over an XML socket so it was literally interpreting the exact characters I send instead of sending a non-keyboard charter like I wanted.
    •  
      CommentAuthorjonfen
    • CommentTimeFeb 24th 2010
     
    Why not make a direct Socket connection instead of XMLSocket

    after all, most micro controllers are going to communicate [faster] in binary, as opposed to having to parse XML.
    •  
      CommentAuthorhusar
    • CommentTimeFeb 24th 2010
     
    Trying to parse the data with the Socket is absolutely wacky. The XMLSocket gets the data back very nice and neat. Each line comes back and I have to do nothing to process it. But the Socket is totally jacked up. One big chunk for the entire 4 riders and the t and no consistency to line breaks or characters that follow each rider's data. I can send you a Socket example if you want to play around with it and try to parse it out. I have reached out to several message boards and read lots of other posts about the data coming back all messed up when using Socket. The only solution was to use Glue and Firmata. That would require me to put something on the Arduino that is not standard to OpenSprints.