new $EE tuning thing!

[steveo]

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.

[fbody_Brian]

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.

[steveo]

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?

[steveo]

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..

[fbody_Brian]

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.

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

[steveo]

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.

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)

[steveo]

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.