Quote from: g0re79 on February 28, 2014, 01:47:16 AM

EDIT: My final conclusion - Haas can connect to Cryptsy, read wallets stats (and maybe even place orders), but can´t read any actual prices. Its strange, because according to a log print screen on my first post in this page Haas was able to read prices..

Quote from: SmokedMolex on February 28, 2014, 07:20:44 AM

EDIT: Prices started working at 1:56 CDT. Cryptsy apparently doesn't like to be polled every minute. It does however get prices every 5 minutes it seems.
EDIT EDIT: The above isn't true. Cryptsy gives prices when it feels like it. There is no set interval as to when it works or doesn't. But it does seem to be updating every few minutes.

Quote from: eyegoatboy on February 28, 2014, 04:19:12 AM

@papasmurph how come your Cryptsy works Huh

??

Special thanks to the people above here for the responces. I am glad to see everybody keeps everybody posted here (and in a fair way!).

This are really the last steps that i am unable to solve from the software side. There are now 3 methods to read the prices and there are 2 ways implemented to progress and monitor the orders. I have got no other API thats has so many backup methods to do its work. This is really the limit of what i am able to do, the rest is up to to the API of Crytspy itself just to answer correctly.

I have had contact with Cryptsy to discus this situation and Cryptsy have told me this is related to a overload of the API.

Based on the random problems (price reading, order progressing and tracking) and the answer of Cryptsy i can only confirm. This what we see is a result of a instable or overloaded server.

BTW This message:

Quote

The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF

Is NOT related to Cryptsy, this is a error caused by Bitstamp. At the release i already notified we monitor this message at this moment. First i thought this was caused by the update, but all versions have this message. Secondly i thought it was just an small error at the API of Bitstamp but is seems to be staying. This is last one is what i needed to know for sure, if it stayes or not. (It could have be caused by a DDOS too) Because this is clear now i can make changes to the software to work-around this protocol error. Despite the error itself there is nothing to worry about. I will make and push a small update to solve this one.

A general usage tip:
If you backtest or if you auto-tune, do not forget to press the "Clear statistics" button. This will get rid of all the data in the trade-bot. After all, during real time usage you do not want to see/continue on the simulated data.