1. Forums
2. FAQ
3. TypeError: exchange.Log is not a function

TypeError: exchange.Log is not a function

Author: baran, Created: 2018-07-17 10:30:37, Updated:

---

---

• OK futures robot is not getting information for you
• BitAsiaEx General Protocol supported by plugins
• Can the FMZ platform perform the functions of a filter?
• Problem with the GetRecords function
• Use of common protocols Plugins implementing JS language Synchronized tasks
• The small question is, how do you operate two pairs of transactions simultaneously in one strategy?
• Please note: Chart does not call updates and does not update, you have to output Log once to update?
• Problems with the GetTicker () market data acquisition for different cycles in the retrospective system
• Exchange IDAX General Protocol Supported by plugins
• Please ask how to get BTC/USDT from the Bitcoin exchange
• Can the interactive button be described as an input box, pull down list with json?
• About the low-level K-line cycle in the option setting for generating ticks
• Please help me to get my token account information
• Please tell me what strategy to use to start making money thanks to you.
• Asking for help, the website has a big card
• Small white questions in the python version of the live digital currency trading library
• GetTicker: 400: {"code": 2, "data": {}, "message": "invalid params"}
• After the configuration is complete, the Control Center - > Robot - > Debugging Tool, after running, the alarm as follows, please ask how to solve.
• Can we divide the quantity of transactions in the coin circle into the following 9 types?
• The first test bot, using the default code, only had a getaccount function that told me not to log in.

---

Inventors quantify - small dreamsRe-testing temporarily not supported by exchange.Log

Inventors quantify - small dreamsPlease tell me how to simulate ordering in retest, using exchange.Buy exchange.Sell will accidentally clear a global variable. I don't quite understand what you mean, it bothers you. Describe it.

baranThen ask why a global variable is wrong in retesting.