Page 14 of 72 FirstFirst ... 49101112131415161718192464 ... LastLast
Results 196 to 210 of 1070

Thread: new $EE tuning thing!

  1. #196
    Fuel Injected!
    Join Date
    Sep 2012
    Location
    Huntsville, AL
    Posts
    237
    If anyone hasn't donated something to Steveo, now's the time. There's an ebay auction for some repair parts his car could really use.. ending in the next 18 hours. If you can throw $50, 20 or even $10 his way, do it soon.

  2. #197
    Fuel Injected! fbody_Brian's Avatar
    Join Date
    Mar 2013
    Location
    Biloxi MS
    Posts
    166
    Definitely deserving!
    1994 LT1/4L60E Formula

  3. #198
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    TCC indicator is backwards when selected manually, but correct when on auto.
    can you confirm that this is still the case with latest beta?

    so if you click: On the converter is locked, but the indicator is OFF?
    and if you click OFF converter the is unlocked but the indicator is ON?

    or is it something else

    im flying blind with this one

  4. #199
    Fuel Injected! fbody_Brian's Avatar
    Join Date
    Mar 2013
    Location
    Biloxi MS
    Posts
    166
    That's exactly what I saw yesterday.
    I will try to confirm asap
    1994 LT1/4L60E Formula

  5. #200

  6. #201
    Fuel Injected! fbody_Brian's Avatar
    Join Date
    Mar 2013
    Location
    Biloxi MS
    Posts
    166
    on a side note, been desperately trying to get this working on nix. I've posted on qt forums and posted on qtbug for qtserialport.

    here's some of the conversation:

    I'm setting to 8192, I get the error:
    "Baud rate of serial port /dev/ttyUSB0 is set to 8193 instead of 8192 :divisor 2929.687500 unsupported"
    Yet it works in windows, and in emulation under linux, so the hardware does work at this baud rate.
    If I set it to 8193 baud i get this error, which is strange:
    Baud rate of serial port /dev/ttyUSB0 is set to 8193 instead of 8193 :divisor 2929.329834 unsupported
    Baud rate is set to 8193 instead of 8193
    I'd really like to get this working
    thank you

    Denis Shienkov added a comment - 7 hours ago - edited

    @Brian Labbie ,
    in your case it is not an error! it was already explained to you at a forum

    in this case your device got 8193 baud instead of 8192.
    UPD: You can also try 5.6.0 branch.




    Brian Labbie added a comment - 1 hour ago

    Not sure how it was explained to me...
    I got no real answer on this.
    "in this case your device got 8193 baud instead of 8192. "
    then why if I set to 8193 do i get the error:
    Baud rate of serial port /dev/ttyUSB0 is set to 8193 instead of 8193 :divisor 2929.329834 unsupported
    it makes no sense!




    Denis Shienkov added a comment - 1 hour ago

    > Baud rate of serial port /dev/ttyUSB0 is set to 8193 instead of 8193 :divisor 2929.329834 unsupported
    it is just incorrect output of the debug information, where the fractional part of real baud rate is lost.. should be like:
    Baud rate of serial port /dev/ttyUSB0 is set to 8193.blablabla instead of 8193 :divisor 2929.329834 unsupported
    Instead of:
    if (serial.custom_divisor * baudRate != serial.baud_base) {
    qWarning("Baud rate of serial port %s is set to %d instead of %d: divisor %f unsupported",
    qPrintable(systemLocation),
    serial.baud_base / serial.custom_divisor,
    baudRate, (float)serial.baud_base / baudRate);
    }


    should be:
    if (serial.custom_divisor * baudRate != serial.baud_base) {
    qWarning("Baud rate of serial port %s is set to %f instead of %d: divisor %f unsupported",
    qPrintable(systemLocation),
    (float)serial.baud_base / serial.custom_divisor,
    baudRate, (float)serial.baud_base / baudRate);
    }


    and I repeat again: this debug output does not matter to your issue, because the method does not returns an errors!
    So even though it hangs with that debug output, it's not an error.
    I'll just keep rebooting into win7 to log and flash, unless you have some idea.

    EDIT:
    the latest:
    "Maybe the linux drivers of your device do not support using of custom divizors... try 5.6.0 branch, where are used the new 'termios V2' feature instead of old 'serial_struct', maybe it will work.."

    So I'll probably muck around with it tonight.
    would be so awesome to have a native linux app for this
    Last edited by fbody_Brian; 12-30-2015 at 07:05 PM.
    1994 LT1/4L60E Formula

  7. #202
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    we can do it. do you use debian/ubuntu or something else? i need a distribution to make an official port/package for to start with.

  8. #203
    Fuel Injected! fbody_Brian's Avatar
    Join Date
    Mar 2013
    Location
    Biloxi MS
    Posts
    166
    Quote Originally Posted by steveo View Post
    we can do it. do you use debian/ubuntu or something else? i need a distribution to make an official port/package for to start with.
    I currently use openSuse. I usually install most stuff from source, but if we get it to work I can build an rpm package for my distro.
    I'll try to compile qtserialport 5.6 tonight and see if it behaves differently.
    1994 LT1/4L60E Formula

  9. #204
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    qt is a real clusterfluck sometimes. it's the most gigantic library ever. sometimes it's like using a 10 pound sledgehammer to push a tack into a wall.

    anyways qt's serial driver probably isn't the issue, it's well tested on linux.

    what kernel are you running, what serial driver and chipset do you use?

    the ultimate solution in linux or freebsd (which i used in my old aldl-io program) was to completely disable the kernel's serial driver and use libftdi to just send/recieve raw usb commands directly to the chip from userland. a bit more overhead, but that way you don't have a universal serial driver that needs to interface with ttys and junk telling you that a baud rate is no good, you can command the chip to do whatever it's capable of doing.. i found it rediculously stable.

    unfortunately qserialport does not support libftdi, but if i had to write a version that DID use libftdi, it would be a no brainer, i could just port the serial layer from aldl-io, as the api is fairly similar.

    edit: also what version of QT are you building against?

  10. #205
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    i read the termios patch for QT and it seems like it might solve the problem. 5.6 is due for release soon too so we could make it a requirement for linux support..

  11. #206
    Fuel Injected! fbody_Brian's Avatar
    Join Date
    Mar 2013
    Location
    Biloxi MS
    Posts
    166
    Quote Originally Posted by steveo View Post
    qt is a real clusterfluck sometimes. it's the most gigantic library ever. sometimes it's like using a 10 pound sledgehammer to push a tack into a wall.

    anyways qt's serial driver probably isn't the issue, it's well tested on linux.

    what kernel are you running, what serial driver and chipset do you use?

    the ultimate solution in linux or freebsd (which i used in my old aldl-io program) was to completely disable the kernel's serial driver and use libftdi to just send/recieve raw usb commands directly to the chip from userland. a bit more overhead, but that way you don't have a universal serial driver that needs to interface with ttys and junk telling you that a baud rate is no good, you can command the chip to do whatever it's capable of doing.. i found it rediculously stable.

    unfortunately qserialport does not support libftdi, but if i had to write a version that DID use libftdi, it would be a no brainer, i could just port the serial layer from aldl-io, as the api is fairly similar.

    edit: also what version of QT are you building against?
    qt5.5.x at work right now so I can't be super precise, but it's definitely 5.5
    I've written a program using QT before, it was gigantic at qt3, I can only imagine it's just gotten bigger.
    The thing is, I can connect using winflash, datamaster, tunercats, all using wine in linux, so I know that it can work in linux. Not sure how wine talks to the serial device. I'm using the ftdi arduino setup. the $10 setup.

    Quote Originally Posted by steveo View Post
    i read the termios patch for QT and it seems like it might solve the problem. 5.6 is due for release soon too so we could make it a requirement for linux support..
    That's what I'm hoping for
    1994 LT1/4L60E Formula

  12. #207
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    qt5.5.x at work right now so I can't be super precise, but it's definitely 5.5
    i think there's only 5.5.0 and 5.5.1

    i read all the 5.6 changelogs and eehack should build against it with no problems. qt is pretty good with backwards compatibility.

    Quote Originally Posted by fbody_Brian View Post
    Not sure how wine talks to the serial device.
    me either but i betcha it's either using termios (which has been around for ages) or it just knows how to deal with bitchy divisor complaints in a better way than me and qserialport do.

    I'm using the ftdi arduino setup. the $10 setup.
    good, same here.

    I've written a program using QT before, it was gigantic at qt3, I can only imagine it's just gotten bigger.
    it does depend how you build it. 5.4 bundled with qt creator was built with internationalization and webkit junk and required like 20mb+ of libraries for your average program.

    getting qt to recompile on windows can be a nightmare, so i just left it alone, also it's GPL so even changing some #defines means technically i'd have to host the entire source for it.. at least if it's unmodified, i can just link people to the qt windows source if i get called on it.

    5.5, though, seems slimmer in it's default windows binary form, it doesn't seem to require linking against internationalization shit, which is just awesome. that's how i managed to get eehack+libraries+installer down to around 6mb (uncompresses to like 12mb, no big deal)

  13. #208
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    i should mention every single other developer i talked to before writing my own aldl software (and that includes quite a few) told me that setting the serial baud rate to 8192 in a way that works on most configurations can be the hardest part of the entire development. im glad qt did all the nasty work for me on windows.

  14. #209
    Fuel Injected! fbody_Brian's Avatar
    Join Date
    Mar 2013
    Location
    Biloxi MS
    Posts
    166
    Quote Originally Posted by steveo View Post
    can you confirm that this is still the case with latest beta?

    so if you click: On the converter is locked, but the indicator is OFF?
    and if you click OFF converter the is unlocked but the indicator is ON?

    or is it something else

    im flying blind with this one

    Latest beta:
    Driving with torque converter set to auto:
    torque converter works as expected, indicator works as expected.

    set torque converter to off:
    torque converter stays unlocked, indicator light stays off until the normal lockup mph is reached then the light turns on, even though torque converter is unlocked.
    drop below the normal speed and indicator goes off, above the speed and it comes on. Light has the same behavior as if it's set to auto.

    set torque converter to on:
    torque converter is locked, works in any gear, light never indicates a locked condition
    1994 LT1/4L60E Formula

  15. #210
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    so the indicator light doesn't function at all with mode4 tcc enable. i can live with that.

    so what i'll probably do in this release is just force the light to be on/off to not confuse people, then in the next release i'll try to patch it so the mode4 override also sets/unsets the status bit.

Similar Threads

  1. 1badcell and thats not the only thing
    By 1badcell in forum Introductions
    Replies: 2
    Last Post: 12-31-2013, 02:25 AM
  2. Replies: 6
    Last Post: 11-27-2012, 09:03 PM
  3. Replies: 2
    Last Post: 11-07-2012, 05:26 PM
  4. Minor thing.
    By historystamp in forum GearHead EFI Forum Support
    Replies: 7
    Last Post: 01-22-2012, 12:00 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •