Page 2 of 2
Re: Noobie Question
Posted: Thu Aug 18, 2011 12:14 pm
by volvoguy50
Lance wrote:All,
It seems that the CAN transfer likes the input pages to be in 8 byte blocks. So I have added 7 bytes to the code and INI as 'pad bytes' for a total of 640 bytes and the CAN comms appear to work perfectly again.
The new 2.110 code and INI are here:
http://www.msgpio.com/manuals/mshift/V2code.html (you may need to refresh this page if you have visited it recently). Anyone experiencing CAN issues should upgrade.
Many thanks to Phil for his work and advice on this! And thanks to users for their patience.
Lance.
The pile of dash errors is still there for me. Every time I open TS, this comes up:
I reported that to Phil over on the MSExtra Forums as well.
I'm using MS3 on USB, CAN passthough to a MegaShift (GPIO) and a JBPERF IOx board.
Re: Noobie Question
Posted: Thu Aug 18, 2011 12:19 pm
by Bernard Fife
volvoguy50,
Yeah, I can't really say much about that, I don't have an MS-III - I do know it now works perfectly with 2.905 on MS-II, including the gauges whose values are from MShift sent over CAN.
Lance.
Re: Noobie Question
Posted: Thu Aug 18, 2011 12:35 pm
by LT401Vette
That is a TS issue in 1.13. I stumbled across that this morning myself. When you first add a new CAN device and TS creates the dash for it, it is not assigning the controller properly. So it is looking for the OutputChannels on the CAN dash on the Main Controller.
If you right click and load the default dash it does it right. I fixed that today for the next patch release.
Re: Noobie Question
Posted: Thu Aug 18, 2011 12:45 pm
by Bernard Fife
Phil,
A thousand thank-yous for sorting this out!
Lance.