Jump to content

Linux EScribe Suite Beta Thread


Recommended Posts

 

3 hours ago, E5K1M0 said:

I would like to get Escribe working on an Rpi 4 but based on the information in this thread it seems like its going to be more of a project than I thought. Any recommendations on which distro to start with that will play reasonably well with both with the Pi & EScribe?

Debian and Ubuntu and their derivatives should work reasonably well, though I don't know about it running on a Raspi, it being ARM based. That might pose an issue.

Edited by Khorne
Link to comment
Share on other sites

Seems like I made it too hard on myself. On my second go at it I got it first crack, not exactly sure where I went wrong initially. I have it running with the latest raspbian 32bit build on Rpi4, simply double clicking on the file in the GUI after making it executable. 

 

One thing to note... the Rpi is not happy if you hook up a 100c unless you turn off USB charging. I tried several USB supplies including a 65W PD supply that runs a 15" laptop to power the Pi to no avail. I settled for disabling USB charging on the mod in the end.

 

The eventual project here is to make a portable "tablet" for Escribe. I currently have a 7" touch panel with a Rpi mounted to the back. Eventually to be battery powered and a enclosure 3D printed for the back of the panel to cover the Pi. Why? I dunno, why not. 

 

 

EDIT: may have spoken too soon, it appears to be crashing on loading any of my mods... investigating

Edited by E5K1M0
update
Link to comment
Share on other sites

@E5K1M0, do you have the newest 100C firmware applied?

The older one had a bug that let the USB voltage get too low, which could cause it to disconnect from USB data, especially on weak supplies. The newer one has fixed that. If not, there's also "Max USB Charge Rate" in Mod->Battery which you can use to limit it to 1.5A instead of 3A.

As far as crashing goes, can you try running it from a command line? The command will be:

~/.local/opt/evolv/escribe-suite/launch-escribe-suite

That should show you some debug information, and when it crashes, it'll probably say something there.  (I encountered something similar yesterday: on one of my Linux versions, it turns out I had used sudo when running Mono at some point, so the ~/.mono directory had root permissions (bad) and it would crash any time EScribe tried to write to the registry. They really should fix that, but realistically, I should really make a work-around.)

Link to comment
Share on other sites

  • 2 months later...

Firstly, thanks from another one of those 5 users you predicted in your OP... ;) I was curious, so I did some extensive digging!

Desktop Linux use is currently something like 2.35% (https://gs.statcounter.com/os-market-share/desktop/worldwide) and Canalys estimating the number of installed PCs and laptops worldwide to reach 1.77 billion by the end of 2021 (https://www.reuters.com/article/us-tech-hardware-yearend-idUSKBN28Y12M) that means there's something like 41,595,000 people using desktop Linux... Just a few more than your estimate! 😛

I do personally have a single issue: not all of the screen thumbnails (in the scroller on the right of the Theme Designer screen) are being shown properly. Clicking on where the thumbnail should be still brings it up for editing on the left, but it's like the graphics are only being drawn for the screens visble in the window when it first opens. I'm running KDE Neon 5.22 - let me know if I can provide any more information to help you squash it! :D

Cheers!

Paul

Link to comment
Share on other sites

I've posted up SP 30.3

I spent a bunch of time getting rid of Mac and Linux specific bugs (visual, functional, and crash) in this version.

The Linux version should operate about as well as the Windows version at this point. Let me know if anything does/doesn't work on it.

  • Like 2
  • Thanks 2
Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...

Works well with X86_64bit linux Mint,really surprised i didn't notice any bugs versus early versions for windows back in when i bought DNA200 it took a year or two until it got to be bug free.  it seem like it almost runs better on linux especially considering that the amount of hours spent in developing for Linux and it's 5 users is not likely the same spent on Windows version.  I remember the days when software was immature every time you started escribe first would hang "program not responding" then after 15-45 seconds it would start working i almost emailed you guys suggesting you hire the developers at nfeteam.org windows version ever since first version very few bugs rock solid but not sure why no official Linux version and the very early beta/alpha version definitely doesn't have a slick installer like Escribe for Linux it must be the programming language the program is written in at least that's what my newbie mind that doesn't know how to write even basic program.  Hmmm by the 5 people using linux did you mean the 5 people who are also co-workers who love linux.

Link to comment
Share on other sites

  • 2 months later...

Hello All,

I'm running Linux Mint 20.1 Ulyssa kernel 5.4.0-109-generic and unfortunately I cannot get EScribe suite to connect to my 4 different DNA 250 units (2 Paranormal & 2 Thelma). Getting an error that just says "Can't figure out the device version" when trying to download and connect. 

EScribe version is 2.0 SP30.1

Anyone have any thoughts on where to start for troubleshooting other than downloading an older version and trying again?

Just a note - Linux Admin/Dev is my day job so if you need folks to test I'm more than willing to help!

Screenshot at 2022-04-23 16-30-15.png

Edited by AmadVaper
Link to comment
Share on other sites

Decided to run in a terminal to see what EScribe was outputting and I've added that below if someone can forward that on to the Devs.

Going to try different cable too

BTW - My machine hardware is:

Ryzen9 3900X
MSI X470
64GB Crucial Ballistix 3200mhz Ram
Zotac 1060 Video
2 Intel NVME 1tb
Razer Black Widow Keys
Logitech MX Anywhere 2 mouse

 

"/home/user/.local/opt/evolv/escribe-suite/launch-escribe-suite"
Killed
user@machine:/media/user/Data1$ Device list changed.
16:39:14.8630:   Benchmark: Tab Configuration: Welcome took 45.1831 ms.

16:39:14.8822:   Benchmark: File->New took 10.292 ms.

16:39:14.8834: Benchmark: Startup took 565.2474 ms.

16:39:14.9362: Benchmark: AutoConnect took 6.8696 ms.

Device list changed.
Device list changed.
16:39:23.0872: Benchmark: AutoConnect took 7.9496 ms.

Device list changed.

(EScribe:487097): Gtk-WARNING **: 16:39:23.223: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 0
A.JXD: Exception of type 'A.JXD' was thrown.
  at A.HJD.GU (System.IO.Stream , System.Byte[] , System.Func`2[T,TResult] , System.Func`2[T,TResult] , System.Action`2[T1,T2] ) [0x0013d] in <7f12dab92af142cabec75367973409b4>:0 
  at A.HJD.UU (System.IO.Stream , System.Byte[] , System.Func`2[T,TResult] , System.Action`2[T1,T2] ) [0x00000] in <7f12dab92af142cabec75367973409b4>:0 
  at A.HJD.BU (System.IO.Stream , System.Int32 ) [0x00095] in <7f12dab92af142cabec75367973409b4>:0 
  at A.AKF+NKF.GU (A.ZRB , System.Byte , System.Int32& , System.Boolean& , A.HXF ) [0x000bb] in <18d250f3d7964b88be530360e0b927da>:0 
I/O output report failed.
Closed.
16:39:54.9883: Benchmark: AutoConnect took 2.4082 ms.

 

Link to comment
Share on other sites

I also noticed this in the journalctl as well. Is there a plugin that I'm missing for the DNA250 chipset?

 

kernel: hid-generic 0003:268B:0419.0017: hiddev2,hidraw7: USB HID v1.10 Device [Dimension Engineering Evolv DNA 250 Color] on usb-0000:03:00.0-11.7/input0
Apr 23 16:39:23 machine kernel: cdc_acm 1-11.7:1.1: ttyACM0: USB ACM device
Apr 23 16:39:23 machine mtp-probe[487307]: checking bus 1, device 19: "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-11/1-11.7"
Apr 23 16:39:23 machine mtp-probe[487307]: bus: 1, device: 19 was not an MTP device
Apr 23 16:39:23 machine mtp-probe[487336]: checking bus 1, device 19: "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-11/1-11.7"
Apr 23 16:39:23 machine mtp-probe[487336]: bus: 1, device: 19 was not an MTP device
Apr 23 16:39:25 machine ModemManager[1375]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-11/1-11.7': not supported by any plugin

 

Link to comment
Share on other sites

I won't be able to follow up any time soon but did you start with the simple stuff like making sure you're using a good data cable?

Check the USB with another data device? 

It's been quite a while since I have had to designate USBs with any Linux distro, that's going back to the 9.x Ubuntu distros thinking about it. 

Link to comment
Share on other sites

7 minutes ago, Podunk Steam said:

I won't be able to follow up any time soon but did you start with the simple stuff like making sure you're using a good data cable?

Check the USB with another data device? 

It's been quite a while since I have had to designate USBs with any Linux distro, that's going back to the 9.x Ubuntu distros thinking about it. 

Thanks Podunk, I did try a different cable that is known working. Also checked dmesg so I know the system is seeing the DNA250

[24909.609070] usb 1-11.6: new full-speed USB device number 22 using xhci_hcd
[24909.952534] usb 1-11.6: New USB device found, idVendor=268b, idProduct=0419, bcdDevice= 3.00
[24909.952536] usb 1-11.6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[24909.952538] usb 1-11.6: Product: Evolv DNA 250 Color
[24909.952539] usb 1-11.6: Manufacturer: Dimension Engineering
[24909.952540] usb 1-11.6: SerialNumber: [censored]
[24909.999750] hid-generic 0003:268B:0419.001A: hiddev2,hidraw7: USB HID v1.10 Device [Dimension Engineering Evolv DNA 250 Color] on usb-0000:03:00.0-11.6/input0
[24909.999834] cdc_acm 1-11.6:1.1: ttyACM0: USB ACM device

I tried to push service packs to 3 of the units but this just failed saying it could not connect even though EScribe shows the unit connected.

Screenshot at 2022-04-23 17-27-40.png

Link to comment
Share on other sites

Pretty sure the group you need to be part of is plugdev. I'm on Mint 19.3 and have no issue, but I'm part of that group for a wide variety of things, so I wouldn't have been directly aware if this specifically required it. Just verified that I can connect fine on the latest build, just to be certain.

Link to comment
Share on other sites

8 hours ago, KickMeElmo said:

Pretty sure the group you need to be part of is plugdev. I'm on Mint 19.3 and have no issue, but I'm part of that group for a wide variety of things, so I wouldn't have been directly aware if this specifically required it. Just verified that I can connect fine on the latest build, just to be certain.

Here are the groups I am a member of :

groups
user adm uucp dialout cdrom sudo dip plugdev lpadmin bluetooth sambashare vboxusers wireshark power

 

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...