Builty
No display on Waveshare 3.5
Wanted to do another screen build, this time with the 3.5 ( new platform added for v2.0 ) When device arrived, checked power on and screen, showed touch test and rotating colours. Tried to flash v2.02 final, and noticed screen remained blank. Re-flashed, ( erase first - correct procedure ) Thought I might try a beta version, can't seem to find any, so re downloaded and tried a 3rd time, this time I thought I would see if I actually have a connection to T1 ( slightly problematic Satch version-another story ) Found that connection to web app seems fine, changed a few settings and re-booted, but screen on Waveshare 3.5 is not working. First thought was faulty hardware- but screen worked before re-flashing, so any ideas???
Hi Andy. I did have a comment on Youtube of the same, but I made some suggestions and they never got back to me. Is yours the 3.5B, and not the older 3.5 (no B)? Waveshare have both available, similar to the 4.3/4.3B. The code is for the B version only. They change the display driver chip between the 2 versions.
If you do have the B version, let me know and I'll fire up mine again and make sure nothing went wrong with the final build.
If you didn't get the B, also let me know. When I purchased mine, I didn't spot that they had 2, and wrote the code for the 3.5 (not B) and then when mine arrived, I struggled to make it work. I then figured out I had ordered the newer B version, and had to do the code again. I kept the old 3.5 code so I might be able to get it going (but nothing to test on.)
Hi again Greg, Thanks for the reply. I didn't realise there were 2 versions, and I have the 3.5 (no B ) I ordered it from Amazon, so I might have got the wrong version. cheers andy k
Hi again Greg, A follow up, I can confirm that the 3.5 ( not B ) is actually working fine as a midi bridge controller, vi the web app, and I am successfully using it ( without a display ) to use my Satch T1. Do you think there is any chance this model could be made to work, with a revised display driver?? I realise it could be a lot of work, but otherwise the basic 3.5 model is the same and the code works fine. I also ordered the correct model, and have it set up similar to a polar Max, with 2 footswitches, inside a Hammond enclosure, looks great. I have just wired in an internal 3.7 volt battery to use it with the big Tonex, as this has its own, separate , different supply. Early days, but I see no reason why it shouldn't work. I previously tested with the Big Tonex, but was getting a lot of noise ( probably too long cable, with adapters ) and I have now got a shorter cable with the correct connections, seems fine. Is there any more information on the big pedal, as I want to try to understand patch edits. I am trying to decide which of the Brown sound packs I prefer, but there are so many, and I would like to add some effects to some of them via the web app, am I correct in thinking these can not be saved directly on the pedal via the app?? At some point in the future, I think I will be getting a Tonex Plug, as it seems a nice evolution, and it appears to allow edits of ANY patches you have in your library vie the online portal, and it saves 30 on the unit, using its own phone app. This is quite a development, as it means you have access to your library of tone models / patches, without having to use a PC. Early days yet, and the app isn't available yet, but the unit is available for pre order, I quite like the look of it apart from having to use it as a dongle on the guitar-I would probably build a pedal to house it after a tuner, on a small board with a power amp. Thanks again cheers andy k
Hi Andy, Not sure about the 3.5 support. I don't think it would take much to finish it, but I'm keeping in mind that every platform increases the efforts needed to test changes. Maybe I could do a build and you test it?
With the big pedal, its much the same as the One, except that the big pedal doesn't auto saving like the One. So changes like enable/disable an effect get lost when patches are changed. In that way its more suitable for live use. If you want to save a change, you can still use the button on the Tonex itself. I haven't done support for saving from the controller side at the moment.
Yeah the Plug does look interesting. I wish the One had an app like that and buttons for preset up/down. Probably wouldn't have spent the last year doing custom coding then! It seems to be aimed at a different market though. Practise use and not really for live performances.