Wapata Posted April 8 Posted April 8 42 minutes ago, Bliss said: Please, try it again when you can and post the results. So, with Blockly 2026-04-08-1425 here is the result : Using CyberMaster: true DeviceLegoRcx.js:63 [CM null] Requesting serial port... DeviceLegoRcx.js:207 Signature: ff ef 10 DeviceLegoRcx.js:150 Sent: fe 00 00 ff 10 ef 10 ef DeviceLegoRcx.js:267 collected: 00 DeviceLegoRcx.js:305 [CM null] No reply for cmd 10 (attempt 1) (anonymous) @ DeviceLegoRcx.js:305 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:190 alive @ DeviceLegoRcx.js:393 connect @ DeviceLegoRcx.js:99 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:150 Sent: fe 00 00 ff 10 ef 10 ef DeviceLegoRcx.js:267 collected: undefined DeviceLegoRcx.js:305 [CM null] No reply for cmd 10 (attempt 2) (anonymous) @ DeviceLegoRcx.js:305 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:190 alive @ DeviceLegoRcx.js:393 connect @ DeviceLegoRcx.js:99 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:150 Sent: fe 00 00 ff 10 ef 10 ef DeviceLegoRcx.js:267 collected: undefined DeviceLegoRcx.js:305 [CM null] No reply for cmd 10 (attempt 3) (anonymous) @ DeviceLegoRcx.js:305 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:190 alive @ DeviceLegoRcx.js:393 connect @ DeviceLegoRcx.js:99 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:316 [CM null] Command failed after 3 attempts: 10 (anonymous) @ DeviceLegoRcx.js:316 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:190 alive @ DeviceLegoRcx.js:393 connect @ DeviceLegoRcx.js:99 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:207 Signature: ff 5a a5 DeviceLegoRcx.js:150 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:267 collected: undefined DeviceLegoRcx.js:305 [CM null] No reply for cmd a5 (attempt 1) (anonymous) @ DeviceLegoRcx.js:305 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:190 _handshakeCM @ DeviceLegoRcx.js:139 connect @ DeviceLegoRcx.js:100 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:150 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:267 collected: undefined DeviceLegoRcx.js:305 [CM null] No reply for cmd a5 (attempt 2) (anonymous) @ DeviceLegoRcx.js:305 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:190 _handshakeCM @ DeviceLegoRcx.js:139 connect @ DeviceLegoRcx.js:100 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:150 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:267 collected: undefined DeviceLegoRcx.js:305 [CM null] No reply for cmd a5 (attempt 3) (anonymous) @ DeviceLegoRcx.js:305 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:190 _handshakeCM @ DeviceLegoRcx.js:139 connect @ DeviceLegoRcx.js:100 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:316 [CM null] Command failed after 3 attempts: a5 (anonymous) @ DeviceLegoRcx.js:316 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:190 _handshakeCM @ DeviceLegoRcx.js:139 connect @ DeviceLegoRcx.js:100 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:63 [CM null] CM did not respond. Power it on. Both device blink, but not as it does with BCC. The mobile device may not have enough time to answer. You : Blink... Blink _ _ _ Blink... Blink _ _ _ Blink... Blink for the tower. Bcc : Blinl Blink Bliiiiiink... Blink Blink Blink for the tower Quote
Bliss Posted April 8 Author Posted April 8 @wapata, thank you From your post, I can see : "collected: undefined". Which tells me I do not READ anything from the tower... Maybe I have to start by sending something to the Tower to initialize it... It's difficult to find the detailed low level information about CyberMaster... I'll dig more... Let's keep hope... Quote
Wapata Posted April 8 Posted April 8 It's 5PM on your side, 9PM on mine. we work with a certain delay here Have you seen the last link of the previous page ? Quote
Bliss Posted April 8 Author Posted April 8 (edited) @Wapata, @AJB2K3 I think I found someting. In the NQC code I can see they put the DTR Pin HIGH and RTS pin LOW for the CM only. case kCyberMasterMode: fSerial->SetSpeed(2400, kPSerial_ParityOdd); fSerial->SetDTR(true); fSerial->SetRTS(false); return kRCX_OK; I think I read something about that already here. So I added the code to do that in the last version. Can you try again please? I removed the Alive command for now and just left the UNLOCK command. So now when you connect, I Set DTR High and RTS Low, I wait 100 ms, then I send the unlock command. Edited April 8 by Bliss Quote
Wapata Posted April 8 Posted April 8 (edited) It's not the same pattern, it blink slower but only three times now [CM null] Requesting serial port... DeviceLegoRcx.js:215 Signature: ff 5a a5 DeviceLegoRcx.js:158 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:275 collected: f8 df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17 DeviceLegoRcx.js:313 [CM null] No reply for cmd a5 (attempt 1) (anonymous) @ DeviceLegoRcx.js:313 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:158 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:275 collected: 5a a5 4a b5 75 8a 73 8c 74 8b 20 df 61 9e 20 df 62 9d 69 96 74 8b 20 df 6f 90 66 99 66 99 20 df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17 DeviceLegoRcx.js:313 [CM null] No reply for cmd a5 (attempt 2) (anonymous) @ DeviceLegoRcx.js:313 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:158 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:275 collected: df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17 DeviceLegoRcx.js:313 [CM null] No reply for cmd a5 (attempt 3) (anonymous) @ DeviceLegoRcx.js:313 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:324 [CM null] Command failed after 3 attempts: a5 (anonymous) @ DeviceLegoRcx.js:324 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:63 [CM null] CM did not respond. Power it on. Source Code Version: 2026-04-08-1522 Hey, there is data on "collected" Edited April 8 by Wapata Quote
Bliss Posted April 8 Author Posted April 8 (edited) @wapata, I can see you have something in the "collected" now... There is something going on... The series in one of the "Collected" stream is : 4a b5 75 8a 73 8c 74 8b 20 df 61 9e 20 df 62 9d 69 96 74 8b 20 df 6f 90 66 99 66 99 20 df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de Which represent the Reply phrase we look for: Just a bit off the block!. But the preamble is not complete (should be FF, 5A, A5. Not just 5A, A5), etc... Fist Collected contains: øthe block!è Second Collected contains: Just a bit off the block! Third Collected contains: øthe block!è Edited April 8 by Bliss Quote
AJB2K3 Posted April 8 Posted April 8 (edited) Using CyberMaster: true DeviceLegoRcx.js:63 [CM null] Requesting serial port... index.html:1 Chooser dialog is not displaying a port blocked by the Serial blocklist: bluetoothServiceClassId=00001200-0000-1000-8000-00805f9b34fb, name='88:4D:7C:E9:50:F4' index.html:1 Chooser dialog is not displaying a port blocked by the Serial blocklist: bluetoothServiceClassId=00001124-0000-1000-8000-00805f9b34fb, name='88:4D:7C:E9:50:F4' index.html:1 Chooser dialog is not displaying a port blocked by the Serial blocklist: bluetoothServiceClassId=00001124-0000-1000-8000-00805f9b34fb, name='C0:44:42:C7:F1:B9' index.html:1 Chooser dialog is not displaying a port blocked by the Serial blocklist: bluetoothServiceClassId=00001200-0000-1000-8000-00805f9b34fb, name='C0:44:42:C7:F1:B9' DeviceLegoRcx.js:215 Signature: ff 5a a5 DeviceLegoRcx.js:158 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:275 collected: 00 ff 5a a5 4a b5 75 8a 73 8c 74 8b 20 df 61 9e 20 df 62 9d 69 96 74 8b 20 df 6f 90 66 99 66 99 20 df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17 DeviceLegoRcx.js:313 [CM null] No reply for cmd a5 (attempt 1) (anonymous) @ DeviceLegoRcx.js:313 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:158 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:275 collected: ff 5a a5 4a b5 75 8a 73 8c 74 8b 20 df 61 9e 20 df 62 9d 69 96 74 8b 20 df 6f 90 66 99 66 99 20 df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17 DeviceLegoRcx.js:313 [CM null] No reply for cmd a5 (attempt 2) (anonymous) @ DeviceLegoRcx.js:313 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:158 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:275 collected: ff 5a a5 4a b5 75 8a 73 8c 74 8b 20 df 61 9e 20 df 62 9d 69 96 74 8b 20 df 6f 90 66 99 66 99 20 df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17 DeviceLegoRcx.js:313 [CM null] No reply for cmd a5 (attempt 3) (anonymous) @ DeviceLegoRcx.js:313 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:324 [CM null] Command failed after 3 attempts: a5 (anonymous) @ DeviceLegoRcx.js:324 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:63 [CM null] CM did not respond. Power it on. hmn first two bytes are missing but getting the 5 flashes like I did in the other topic. Edited April 8 by AJB2K3 Quote
Gunners TekZone Posted April 8 Posted April 8 (edited) N/A Edited 5 hours ago by Gunners TekZone Quote
Wapata Posted April 8 Posted April 8 17 minutes ago, Bliss said: Second Collected contains: Just a bit off the block! This one is the good one no ? Why it didn't go further? Quote
Bliss Posted April 8 Author Posted April 8 1 minute ago, Wapata said: This one is the good one no ? Why it didn't go further? Because it is missing the complete Signature: ff 5a a5 that is execpted to be in the reply... There is a timing issue maybe, it is like I don't read every bytes... I think there is some progress though... Quote
Gunners TekZone Posted April 8 Posted April 8 (edited) N/A Edited 5 hours ago by Gunners TekZone Quote
Bliss Posted April 8 Author Posted April 8 (edited) @AJB2K3, your log shows collected replies that seems to be complete but I do not see in the reply the ECHO of the command we sent... So I made some modifications to forget about the echo of the command. Let's try the newer version. 2026-04-08-1616 @Wapata, let me know too 31 minutes ago, Gunners TekZone said: There is no RESET as I think you think of it... At each COUNT command LL is just counting changes from 0 and comparing to what I have in my code. Once they match (or exceed I guess) it starts or completes a loop as coded. It will probably go up to 255 then loop to 0, being a program for 8- bit computers, but I have never checked as my wee robot arm simply doesn't move or rotate that much. Now I wonder if the number you put in LL for the COUNT instruction, represents a relative count. If internally, the count is 100, then 15 would mean wait for the count to reach 115... Which has the same result as to reset the count each time to 0 and wait until it reaches 15... Also, for the output commands, does the number represent the time in second? If there is no number for an output instruction, it goes immediately at the next line with no delay other than internal CPU speed? Edited April 8 by Bliss Quote
Wapata Posted April 8 Posted April 8 8 minutes ago, Bliss said: version. 2026-04-08-1616 Here it is ! Using CyberMaster: true DeviceLegoRcx.js:63 [CM null] Requesting serial port... DeviceLegoRcx.js:215 Signature: ff 5a a5 DeviceLegoRcx.js:158 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:275 collected: c0 5a a5 4a b5 75 8a 73 8c 74 8b 20 df 61 9e 20 df 62 9d 69 96 74 8b 20 df 6f 90 66 99 66 99 20 df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17 DeviceLegoRcx.js:313 [CM null] No reply for cmd a5 (attempt 1) (anonymous) @ DeviceLegoRcx.js:313 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:158 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:275 collected: df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17 DeviceLegoRcx.js:313 [CM null] No reply for cmd a5 (attempt 2) (anonymous) @ DeviceLegoRcx.js:313 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:158 Sent: fe 00 00 ff a5 5a 44 bb 6f 90 20 df 79 86 6f 90 75 8a 20 df 62 9d 79 86 74 8b 65 9a 2c d3 20 df 77 88 68 97 65 9a 6e 91 20 df 49 b6 20 df 6b 94 6e 91 6f 90 63 9c 6b 94 3f c0 85 7a DeviceLegoRcx.js:275 collected: df 74 8b 68 97 65 9a 20 df 62 9d 6c 93 6f 90 63 9c 6b 94 21 de e8 17 DeviceLegoRcx.js:313 [CM null] No reply for cmd a5 (attempt 3) (anonymous) @ DeviceLegoRcx.js:313 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:328 [CM null] Command failed after 3 attempts: a5 (anonymous) @ DeviceLegoRcx.js:328 Promise.then enqueue @ DeviceLegoRcx.js:69 rcxCmd @ DeviceLegoRcx.js:198 _handshakeCM @ DeviceLegoRcx.js:147 connect @ DeviceLegoRcx.js:108 await in connect connectRcx @ deviceManager.js:133 document.getElementById.onclick @ main.js:640Understand this warning DeviceLegoRcx.js:63 [CM null] CM did not respond. Power it on. But i need to go sleeping right now, see you tomorrow ! (fun fact : as i'm 5 hours in your futur, i can give you news before the TV ! ) Quote
Bliss Posted April 8 Author Posted April 8 @Wapata, thank you for your help. Your replies are not complete as compared to @AJB2K3. Probably not the same USB/RS232 adaptor and chipset... I will need to tweak some timing I guess... Quote
Gunners TekZone Posted April 8 Posted April 8 (edited) N/A Edited 5 hours ago by Gunners TekZone Quote
Bliss Posted April 8 Author Posted April 8 @Wapata, @AJB2K3, I tweaked a bit some delays in: Version: 2026-04-08-1644 Quote
Toastie Posted April 8 Posted April 8 OK folks, simply too much for me. I am zooming out. I can't focus on CM, RCX, IntA, IntB, at the same time. Whenever there is something that works (IntB + Blockly does, right? IntA is in the works, so is CM, and RCX ...) I'll get back. All the best Thorsten Quote
Gunners TekZone Posted April 8 Posted April 8 (edited) N/A Edited 5 hours ago by Gunners TekZone Quote
Bliss Posted April 8 Author Posted April 8 3 minutes ago, Gunners TekZone said: I hear that!! My "philosophy" here is stick around to do a few confirmation tests and/or suggestions for clarity... To help @Bliss with this incredible achievement. But alas, I am not ready to use Block coding for actual projects. @Bliss On this note... And while it might be a little too late? I am not sure what language and format base you are using for Blockly, or if it is of your own design. But I would like to recommend following as close as possible the block coloring and function that PyBricks uses for their Block code. That way one can better switch between both LEGO programming types (as they simply don't focus on older stuff like the "dumb" Interfaces). But also so one can better assist in development by comparing what works on PyBricks, like counting loops, etc. ----------------------------------------------- Ah, but of course... I now see that their Block programming is behind a paywall... So hmmm... Oh well, it was just an idea I do not know about pyBrick much to be honest. The block programming is not free, but I think Python library is free. I will probably check eventually. Since this is an application that runs in a browser, I use JavaScript. But I think I've read somewhere that Blockly is providing libraties in more languages like python for standalone applications... So to keep everything at best performance, I use the browsers native language which is JS... Quote
Gunners TekZone Posted April 8 Posted April 8 (edited) N/A Edited 5 hours ago by Gunners TekZone Quote
Gunners TekZone Posted April 8 Posted April 8 (edited) N/A Edited 5 hours ago by Gunners TekZone Quote
Bliss Posted April 8 Author Posted April 8 (edited) @Gunners TekZone, did you try to hold ctrl key while moving out a block inside a group of blocks with the mouse? When you have many inline blocks, choosing a middle block with a mouse and dragging, moves also all the block below it. But, ctrl-mouse and drag will actually move only the selected block out... I'm still discovering things with blockly when I use CTRL, SHIT, ALT key and also when I right click on blocks, in the code are, etc... I think you will eventually LOVE block programming when you find out all the possibilities ;-) I remember how reluctant I was about block programming. But the more I learn about it, the more I like it! And the idea is to make blocks that are intuitive and makes lots of things in the behing the scene... So it will improve as I plan to add other helpfull block in a near futur. I like the "connecting" feeling. I find Block Programming like Block building. It is as fun to me. Edited April 8 by Bliss Quote
Gunners TekZone Posted April 8 Posted April 8 (edited) N/A Edited 5 hours ago by Gunners TekZone Quote
Gunners TekZone Posted April 8 Posted April 8 (edited) N/A Edited 5 hours ago by Gunners TekZone Quote
Bliss Posted April 9 Author Posted April 9 (edited) 1 hour ago, Gunners TekZone said: Perhaps, since the Int-A inputs do not seem to offer much in "range", the Arduino should just use a GPIO and not an Analog pin? I agree, should be digital inputs on arduino, but did not want to change that part of LVL1 design... (Maybe they did this to allow for custon sensors using potentiometer I don't know) I just changed the threshold to be ON to 512. So reload you page to get the latest version... (It might update to latest version by itself...) Thank you for the good find. Edited April 9 by Bliss Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.