Tunerstudio communication problem on unix
Moderator: LT401Vette
Tunerstudio communication problem on unix
I posted this question on msefi forum but there seems to be a lot more activity here.
Does anyone here use TunerStudioMS on FreeBSD?
I was able to download and install TunerStudioMS_v3.0.22.tar.gz but am not able to get communication working in miniterm. No com port is available.
I am a member of group uucp as well as a group called dialer.
Starting a new project and trying to detect comes up with nothing.
I am able to connect an external modem and send AT commands to it so I know that the port is valid and working.
Port in FreeBSD is cuau0.
I think I read somewhere about "lock" group but that does not exist on my machine. Maybe I misunderstood.
I am able to connect with my old crummy laptop using megatune.
TunerStudio looks great if I can get it to work!
I do not see any type of log file.
I am using megasquirt I and 2.2 board.
freebsd-version 11.0-RELEASE-p1
Thanks
Does anyone here use TunerStudioMS on FreeBSD?
I was able to download and install TunerStudioMS_v3.0.22.tar.gz but am not able to get communication working in miniterm. No com port is available.
I am a member of group uucp as well as a group called dialer.
Starting a new project and trying to detect comes up with nothing.
I am able to connect an external modem and send AT commands to it so I know that the port is valid and working.
Port in FreeBSD is cuau0.
I think I read somewhere about "lock" group but that does not exist on my machine. Maybe I misunderstood.
I am able to connect with my old crummy laptop using megatune.
TunerStudio looks great if I can get it to work!
I do not see any type of log file.
I am using megasquirt I and 2.2 board.
freebsd-version 11.0-RELEASE-p1
Thanks
-
- Super MS/Extra'er
- Posts: 12732
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Tunerstudio communication problem on unix
I'm not sure it would look for that port name.Port in FreeBSD is cuau0.
Does it show up in the drop down as a port?
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
Re: Tunerstudio communication problem on unix
Not originally - but I found a file called "project.properties"LT401Vette wrote:I'm not sure it would look for that port name.
Does it show up in the drop down as a port?
If I add the line
Code: Select all
commPort=cuau0
Not sure what else to try.
-
- Super MS/Extra'er
- Posts: 12732
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Tunerstudio communication problem on unix
I would suspect that would actually be
/dev/cuau0
/dev/cuau0
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
Re: Tunerstudio communication problem on unix
You are correct, but after adding the path it is still no connect.LT401Vette wrote:I would suspect that would actually be
/dev/cuau0
-
- Super MS/Extra'er
- Posts: 1681
- Joined: Tue Oct 27, 2009 6:24 am
- Location: Van Alstyne, Texas
Re: Tunerstudio communication problem on unix
Try it as root, narrows it down to a permissions issue or hardware.
if the user lacks serial port hardware access, it won't work.
if you can send a fax or use minicom in loopback it should work.
The osx script included in TS package root might be useful as its *bsd based.
if the user lacks serial port hardware access, it won't work.
if you can send a fax or use minicom in loopback it should work.
The osx script included in TS package root might be useful as its *bsd based.
Always doing things the hard way, MS2 sequential w/ v1.01 mainboard, LS2 coils. 80 mile/day commuter status.
Re: Tunerstudio communication problem on unix
Thank you for your reply - I have been busy and this got put on the side.piledriver wrote:Try it as root, narrows it down to a permissions issue or hardware.
if the user lacks serial port hardware access, it won't work.
if you can send a fax or use minicom in loopback it should work.
The osx script included in TS package root might be useful as its *bsd based.
I logged in as root and not working.
TunerStudio does not see the com port - only com1 is listed in the drop down box and there is no com1 on this machine.
minicom app does not detect port either.
I see in the readme.txt file
"or to force 32 bit mode if your usb serial cable drivers don't support 64 bit:
./TunerStudio32.sh"
but I am using a plain old 9 pin serial port, not USB and I don't see a TunerStudio32.sh file in the download.
This might be a dumb question but is this a 64 bit app?
I am running it on a 32 bit machine.
I also tried running OSX_fixperm-217-leo.sh but gave 2 errors referring to dscl not found.
There is no command on my system by this name buy I think the equivalent is users.
I tried changing the script replacing dscl with users but it failed as well.
Thanks again for the help
-
- Super MS/Extra'er
- Posts: 1681
- Joined: Tue Oct 27, 2009 6:24 am
- Location: Van Alstyne, Texas
Re: Tunerstudio communication problem on unix
If you cannot access your serial port as root, abandon all hope; TS will never be able to see it.
Start by doing the basic serial port troubleshooting, I'm pretty use the *BSDs have good forums/how-tos out there.
I wish I could be of more help but the last time I really used a *BSD seriously was NetBSD 1.0. In ~1994.
You might consider trying a Linux liveCD/DVD to troubleshoot.
Some can be set up on USB stick with persistent user space, allowing updates and new programs you could easily run TS on that.
You can also just do a std install to a USB stick as a hard drive.
Start by doing the basic serial port troubleshooting, I'm pretty use the *BSDs have good forums/how-tos out there.
I wish I could be of more help but the last time I really used a *BSD seriously was NetBSD 1.0. In ~1994.
You might consider trying a Linux liveCD/DVD to troubleshoot.
Some can be set up on USB stick with persistent user space, allowing updates and new programs you could easily run TS on that.
You can also just do a std install to a USB stick as a hard drive.
Always doing things the hard way, MS2 sequential w/ v1.01 mainboard, LS2 coils. 80 mile/day commuter status.
-
- Super MS/Extra'er
- Posts: 12732
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Tunerstudio communication problem on unix
You shouldn't need worry about 32 bit vs 64 bit any more. TS has drivers for both on intel linux.
Also the only JRE that respects those flags to force it in 32 bit is OS X.
Also the only JRE that respects those flags to force it in 32 bit is OS X.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html