axsx Posted Friday at 08:34 PM Report Posted Friday at 08:34 PM (edited) SPY chart and connect symbol is blank, price multiplier is 1 and offset is 0. convert = yes in dashboard (maybe it has to be NO) Edited Friday at 08:36 PM by axsx
axsx Posted Friday at 08:40 PM Report Posted Friday at 08:40 PM NQ chart and connect symbol is blank. Rest defaults (price multiplier is 10 defaults). Truth engine uses QQQ to get option chain and convert, but spot price is wrong in dashboard. I dont see the put and call and flip etc.
axsx Posted Friday at 08:45 PM Report Posted Friday at 08:45 PM nq chart with connect symbok $NDX ; price multiplier is 1 offset is 0.
axsx Posted Friday at 08:50 PM Report Posted Friday at 08:50 PM I think one important decision to make is For nq and es futures we have to do autoconvert, the symbols to be used are SPY and QQQ. For any other instrument, we have to use it directly in schawab to see if we get the option chain, if not we have to map to a closet ETF option chain stored in a internal table/array. this is with no autoconvert flag in the NT indicator parameters. Giving price multiplier and offset without autoconvert flag will be misleading. all thee or none imo.
Ninja_On_The_Roof Posted 20 hours ago Report Posted 20 hours ago It is so great having an indicator named after you huh Kimsam?🥰 kimsam 1
kimsam Posted 16 hours ago Author Report Posted 16 hours ago 4 hours ago, Ninja_On_The_Roof said: It is so great having an indicator named after you huh Kimsam?🥰 Haha limited edition 😄Every detail counts .. Name is just part of the user experience 😌 jquiroz75 and Harrys 2
axsx Posted 1 hour ago Report Posted 1 hour ago (edited) @kimsam SPX charts with old and new versions. Old version works perfectly, schwab fetches SPX option chain ( I think it is not fetching spy, you can verify in code). The new version, auto convert is false, price multiplier is 1, connect symbol is SPX. The fetch of SPX fails. Can you check why ? my guess is due to return code of 400, the API call in the latest version of code might have an issue. I checked with NQ similarly, I see the same issue. NDX also same issue. Edited 1 hour ago by axsx
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now